Arigato PRO 3.0

Our premium WordPress auto-responder Arigato PRO is now upgraded to version 3.0.
Here are the new features, improvements and fixes from version 2.9 to 3.0:

  • Added option to copy/clone a newsletter.
  • Added option to change the mailing list owner. This is useful if you have defined user roles that can manage only their own mailing lists.
  • A duplicate list feature lets you copy/clone a mailing list with its custom fields and associated autoresponders. This will not copy the subscribers however.
  • You can send autoresponder email also to those who will not receive it because it’s added later to the sequence. This generates a newsletter to only those subscribers.
  • Applied your WP timezone settings across the system. This will make sure that any date intervals are accordingly to your timezone and users have proper signup date on registration. Note that the optional setting for sending emails after X o’clock remains configurable for backward compatibility.
  • New option lets you not send a newsletter to email address if that address also exists in other selected mailing lists.
  • For better site performance new setting lets you include Arigato scripts and CSS only on the pages that contain signup form shortcode.
  • When using the “Subscribe by email” option and a name has broken encoding the subscriber will be inserted without name.
  • Improved integration with Contact Form 7: you can now include the list signup shortcode in the CF7 message to get yes/no confirmation whether the user has subscribed for each of the mailing lists.
  • Improved handling of new lines around list tags in outgoing messages.
  • Improved handling of POP3 connection errors when checking for bounces or email subscribes. They will no longer stop sending of the cron job emails.
  • Added option to use the standard WP auto paragraphs functions on messages that to not properly display new lines. Use it only when needed.
  • Arigato no longer stores or shows the IP address of the subscribers to comply with data protection laws. You can still use the {{{ip}}} variable in admin notification emails at your own responsibility.
  • Added option to redirect the subscriber to a selected URL if they are already registered and activated in the mailing list.
  • Name will automatically have first letter capitalized when you use the {{name}} and {{firstname}} variables inside messages.
  • Default unsubscribe action is now “delete” instead of “deactivate”. You can change this at Arigato PRO Settings page.
  • For consistency changed “label_style” shortcode parameter to “labels” in all locations. Legacy shortcodes will still work.
  • Added parameter size to Google reCaptcha, when version 2 is used.
  • Fixed bug: The option “For better performance load Arigato scripts and CSS only on pages that contain signup form shortcodes.” was causing PHP error in some occasion.
  • Fixed bug: list notification email field did not properly accept more than one email separated with comma.
  • Fixed bug: when Blacklist management contained empty lines it was blacklisting everything.
  • Fixed bug: when a list has redirect URL it should redirect there even duplicate users.
  • Fixed bug: when newsletters were created from presets a tracker for opened mails were not added.

Tech Support for WordPress Plugins

Sometimes when you have a problem with any of our plugin we will request you access. This happens only in cases when your problem cannot be reproduced on our installations. Why is this required is explained later in this post.

How To Provide Access

It’s easiest to just send administrator’s login (preferably not yours, but a designated account which after resolving the problem will be deleted). Understandable some customers do not want to share full access to their sites so we have a very easy solution for this: create user with role Editor or even Author. Then enable admin rights only for the plugin you need help with:

For WatuPRO

The setting is on WatuPRO Settings page, section Roles -> Roles that can manage exams (or test, quizzes etc). Select the user role and save.

For Arigato Pro

The setting is in Arigato Autoresponder Options page, section Roles -> Roles that can manage the autoresponder. Select the role and save.

For Namaste! LMS

The setting is in Namaste! LMS Settings page, section WordPress Roles that can administrate the LMS. Enable the role and save.

This is it, we’ll need the login details of the account you have created.

In rare events this may not be enough and we may need an FTP account with access to the plugin folder.

You must deactivate, delete or change the account password after the problem is resolved.

Why Provide Access

You don’t expect your doctor to diagnose you only based on symptoms neither you expect your car mechanic to fix your car by watching pictures of the engine. Please don’t expect that software developers can resolve all issues by watching screenshots or reading explanations.

There are many reasons why we may need access:

  • There might be a specific edge-case bug that cannot be reproduced on our installations
  • There might be a conflict with other plugin or theme on your installation
  • There might be a specific server configuration that causes the problem only on your installation
  • The specific volume and type of data you have might be producing a problem that cannot be reproduced elsewhere
  • You may just be doing something wrong
  • Anything else

If we are requesting you for access this means there is no other way to resolve your problem. If you don’t want to do it, this is perfectly fine but technical support can be provided only if do.

In case you don’t trust us you are free to resolve the problem yourself or with the help of trusted by you developer – all plugins come with open sourced code.

What Are We Going to Do With It

We will reproduce the steps that cause your problem along with outputting debug information on various places in the code. This is the reason we may also need FTP access.

We will use the access to diagnose the problem and resolve it, and for nothing else.

Disclaimer:

We are not going to intentionally delete any of your data or send any emails to your users without explicit permission. We will not steal your data or share it with anyone for any reason. Our best interest is to resolve the technical issues you have as soon as possible. However we still recommend creating backups of any sensitive data you have.

WE TAKE NO RESPONSIBILITY OF AND NO LIABILITY FOR ANY DAMAGES CAUSED BY ATTEMPTING TO RESOLVE YOUR TECHNICAL ISSUES. IN NO EVENT AND UNDER NO CIRCUMSTANCES SHALL KIBOKO LABS BE LIABLE  FOR ANY DAMAGES CAUSED BY  DATA LOSS, DATA LEAKS, SITE DOWNTIME AND SO ON. KEEPING YOUR DATA SAFE IS YOUR OWN RESPONSIBILITY.

Segment Performance Shortcode in WatuPRO

From version 5.9.2 WatuPRO supports a new shortcode which allows to show how a segment of the respondents performed on the test – as average percent correct answers or as average number of points.

The segment is based on the answer of a chosen question.

What does it mean and how does it work?

Let’s use an example to make things easier. We will create a single-choice question to ask the user for their age. (You can also use open-ended question for example if you want users to type their answer).

We’ll make this question a “survey” type by selecting “This is a survey question” because we don’t want it to affect the test calculations. Your situation might be different.

Then, in the final screen of the quiz we’ll add the following shortcode:

The average results of respondents aged {{{answerto-2083}}} is [watupro-segment-stats question_id=2083 criteria="percent_correct"]% correct answers on this test.

Which displayed the following output:

The average results of respondents aged 37-50 is 23% correct answers on this test.

Breaking Down The Shortcode

Let’s break down the shortcode and all its parameters so you know how to use it. If you find the explanation of the parameters complicated go straight to the examples to get a better idea how to use the shortcode.

The shortcode is watupro-segment-stats and accepts the following parameters:

question_id

This is a required parameter. The shortcode will not display anything without the question ID. You can see the question ID at the quiz Manage Questions page. It’s the first column in the table.

criteria

This is an optional parameter which defaults to “percent_correct”. You can use the following values:

  • percent_correct to display the average percent correct answers of the group answered the same way to the question in the first parameter.
  • points to display the average points collected of the group answered the same way to the question in the first parameter.
  • grade to display the percentage of users from the group who received the same grade. If you also pass the parameter grade_id you can specify the grade you are referring to – otherwise the calculation will be based on the currently achieved grade from the user.
  • category_grade to display the percentage of users in the group achieved the same category grade for the given category. When criteria=”category_grade” passing one of the parameters catgrade_id or category_id becomes required. You can for example use the shortcode once for each category grade to show the % of users achieved each specific grade on the category. If you pass category_id instead the stats will be shown based on which grade was last received by the current user on that category (see the examples for more clarity). There is a trick that makes things easy if you use the %%CATGRADES%% variable to loop through all the categories. Pass the parameter category_id like this: category_id=”this” in the “common category grade output box” on the Manage Grades page (you have to select a question category to have the box shown) and the program will automatically figure out which is the category and what grade was achieved on it for each of the categories.

compare

This attribute can be used only when criteria is “grade” or “category grade”. It lets you calculate either users who got the same grade (or category grade) as the quiz taker (this is the default behavior) or what % of users got worse or better grade.

Possible values for the attribute: “same” (default), “better” or “worse”.

segment

This is optional parameter which lets you show the results of a chosen by you segment. This is very important: by default, when the parameter is missing, the shortcode will display the results of the same segment as of the current user. So if the user responded “37-50” like in our example above, the shortcode will display the stats for all users who took the same quiz AND selected “37-50” on the question.
However the shortcode allows you to display stats for other groups by passing the segment parameter. So you can show full stats like this:
The average results of respondents aged up to 18 is [watupro-segment-stats question_id=2083 criteria="percent_correct" segment="under 18"]% correct answers on this test while the average results of respondents aged over 50 was [watupro-segment-stats question_id=2083 criteria="percent_correct" segment="over 50"]%

This shortcode is intended to be used only in the “FInal Page / Quiz Output” box. It will work just fine outside it but in this case the parameter segment becomes required and the shortcode will calculate stats based on all tests which use the question passed in “question_id” parameter.

Examples

This is a very powerful shortcode and with all these parameters it can be confusing. Some examples will make things much easier to understand:

Show average points from the group on the whole test (in the final screen):

The average points achieved from the other respondents your age is [watupro-segment-stats question_id=2083 criteria="points"].

This will display something like:

The average points achieved from the other respondents your age is 33.

***

Show average % correct answers from all groups on the whole test (in the final screen):

The average results of respondents aged up to 18 is [watupro-segment-stats question_id=2083 criteria="percent_correct" segment="under 18"]% correct answers on this test while the average results of respondents aged over 50 was [watupro-segment-stats question_id=2083 criteria="percent_correct" segment="over 50"]%

***

Show the % of users from the group who achieved the same grade (use only on the final screen):

Your grade is %%GTITLE%%.

On average [watupro-segment-stats question_id=2083 criteria="grade"]% of the respondents aged {{{answerto-2083}}} got the same grade.

This will display something like:

Your grade is B+.

On average 36% of the respondents aged18-36 got the same grade.

***

Show the % of users from the group who performed worse (got lower grade)

Your grade is %%GTITLE%%.

On average [watupro-segment-stats question_id=2083 criteria="grade" compare="worse"]% of the respondents aged {{{answerto-2083}}} performed worse than you.

This will display something like:

Your grade is B+.

On average 41% of the respondents aged18-36 performed worse than you.

***

Show the % of users from the group who achieved the same category grade in each question category:

(You need to use this shortcode inside the “Common category grade output” box and make sure %%CATGRADES%% variable is included in the “final output” of the quiz.)

For category %%CATEGORY%% you got %%POINTS%% points and %%PERCENTAGE%%% correct answers.

Grade: %%GTITLE%%

On average [watupro-segment-stats question_id=2083 criteria="category_grade" category_id="this"]% of the respondents from your age group got the same grade.

This will display something like:

For category Business Analytics you got 8 points and 65% correct answers.

Grade: Success

On average 74% of the respondents from your age group got the same grade.