Category Archives: CalendarScripts

Namaste! LMS Bridge for GamiPress

We have just released an integration between Namaste! LMS and GamiPress.

The integration adds new activity events that let you award GamiPress points of any type when any of the following events happen in Namaste! LMS:

For Courses

  • When a student finish a course
  • When a student finish a specific course

For Modules (When Modules are Enabled)

  • When a student user finish a module
  • When a student finish a specific module
  • When a student finish a module of a specific course

For Lessons

  • When a student complete a lesson
  • When a student complete a specific lesson
  • When a student complete a lesson of a specific course

The new events are visible in the “When” drop-down selector in Add/Edit point type page:

Feel free to send us any suggestions for other events in this integration.

Performance on Multiple Quizzes and Conditional Content in WatuPRO

Here is a new super power of the WordPress quiz plugin WatuPRO, available from version 6.4.8.5: a shortcode to calculate the performance of a logged in user on multiple quizzes. It can display:

  • The total points collected
  • The average percent correct answers on all quizzes.
  • The average percent achieved points from maximum points in every quiz.
  • The total number of correct answers.
  • The total number of wrong answers.
  • The total number of unanswered questions.
  • The total maximum points that could be collected.

The stats are based on all attempts of the logged in user of the quizzes whose IDs are passed in a shortcode attribute.

The new feature also allows you conditionally display any content based on the total points collected, average percent correct answers, or average percent from maximum points.

Let’s see how this all works.

The Shortcode and The Variables

Note: from version 6.6.7.3 you can pass the parameter use_only_latest_attempts=1 to base the calculations only on the latest attempt of the user instead of all attempts.

It is a content-enclosing shortcode and will not produce any output by its own. You need to enclose the content that you want to use along with variables that you want calculated. The shortcode has a required parameter quiz_ids which should contain the ID of the quizzes that will be used, separated by comma. Example:

[watupro-multiquiz quiz_ids="2,3,25"]

On the 3 quizzes you collected a total of %%MULTI_POINTS%% points and you gave average of %%MULTI_PERCENTAGE%%% correct answers.

[/watupro-multiquiz]

Here are all the available variables for this shortcode:

  • %%MULTI_POINTS%% – the total points collected
  • %%MULTI_PERCENTAGE%% – the average percent correct answers
  • %%MULTI_PERCENTAGEOFMAX%% – the average percent points collected from maximum points possible (the stat is calculated for each quiz attempt and then dividied. It’s NOT an average of all collected points vs all possible points).
  • %%MULTI_CORRECT%% – the total number of correct answers given
  • %%MULTI_WRONG%% – the total number of wrong answers given
  • %%MULTI_EMPTY%% – the total number of unanswered questions
  • %%MULTI_MAX-POINTS%% – the total maximum points possible from all quizzes and all attempts

If the user is not logged in or if the quiz_ids attribute is not passed, the shortcode will not display anything.

The Conditional Parameters

This shortcode can be used also to conditionally display some content based on how the user has performed on the selected tests. You can use conditions for point range, percentage range and range for percent from maximum points. All conditions can be used at the same time.

The content enclosed between such shortcode will be shown only if all the conditions are met. This is a very useful way to display something only when the conditions are met. It’s almost like the standard quiz grading except that the grade will not be stored anywhere and cannot trigger certificates or other actions.

Here’s how to use it:

[watupro-multiquiz quiz_ids="2,3,25" condition_points="10-25" condition_percent_correct="50-100" condition_percent_max="50-100"]

Congratulations you did extremely well and earned a discount code: BIGDISCOUNT

On the 3 quizzes you collected a total of %%MULTI_POINTS%% points and you gave average of %%MULTI_PERCENTAGE%%% correct answers.

[/watupro-multiquiz]

You can skip any of the condition attributes to use only one or two of them.

Event Triggers in Intelligence Module for Arigato PRO

Event triggers are powerful way to do automated actions in your WordPress auto-responder when certain events happen. This page explains the event triggers in the Intelligence module for Arigato RPO:

Subscribes to is a pretty obvious trigger. It fires immediately when a subscriber subscribes to a selected mailing list.

Unsubscribes from, similar to the above fires immediately. It lets you subscribe the user to another list (not recommended without their agreement!), automatically unsubscribe them from other lists, etc.

Clicks on is a trigger that fires immediately when the subscriber clicks in a trackable link inside the email message. Trackable links are another feature enabled by the Intelligence module. It lets you track clicks and CTR on links that you insert in your messages.

Does not click on is a pseudo-trigger that is executed once daily. There is no event “not click” on a link but with these pseudo triggers you can select that something will happen if the user does not perform an action within X days of their registration. In this case the trigger means: do something if the user does not click on a selected link within, for example 30, days of their registration. It does not matter in what email message the trackable link is sent, how many times it is sent, or even if it is not sent at all. If there is no click from that user after X days, the trigger fires.

Reads autoresponder email is an immediate trigger. It fires when the subscriber opens the selected email. Note that these triggers are not reliable as many email programs ignore the hidden image that we use to track email openings. There will be false-negatives, so don’t use the trigger for anything too important.

Does not read autoresponder email is another pseudo-trigger. There is no real “event” here but you can create this daily trigger that will check once per day if the subscriber has opened the selected autoresponder message. If after X days of their registration they still have not read the email, the trigger fires. As with “reads autoresponder email” trigger above, these two triggers are not reliable. There will be false-positives.

Stays subscribed in is a daily trigger too. Once daily the program checks if the subscriber is still with us. You can select that if she stays subscribed for 180 (for example) days, she may get tagged as long-term subscriber, moved to another mailing list, or something else.

Receives autoresponder email is an immediate trigger. It fires at the moment a specific message is successfully sent to the subscriber from your server. There is no guarantee that the email has been read.