Automatically send email reminders

89,0099,00

Plus 19% VAT
Delivery Time: keine Lieferzeit (z.B. Download)

Script for automatically sending Limesurvey email reminders using a cronjob. Helps you solving spam issues and working around email sending limits.

SKU: N/A Category:

If you are maintaining several surveys at your Limesurvey system, sending email reminders manually can be quite a pain. Using this Limesurvey cronjob script you can fully automate the process of sending email reminders.

The tool sends reminder emails for active surveys only to those participants who have:

  1. already received an invitation email.
    -> See this Limesurvey cronjob script to automatically send email invitations
  2. not finished the survey yet.
  3. a valid token and email address assigned.
  4. not received an invitation or reminder within the last Y days or hours (plugin setting).
  5. not received more than X reminders (plugin setting).

Furthermore, this Limesurvey cronjob script takes into account the survey’s start date (if set). It also checks the “valid from” and “valid until” dates for every participant.
Since version 2.12 the tool also supports setting custom reminder send dates. You can even set multiple dates for the different reminders to be sent.

Using this Limesurvey cronjob script will reduce the risk of your Limesurvey invitation emails being treated as spam. You can not only define how often the script is called. But you can also define how many emails should will be sent at every call by adjusting the batch size setting at survey level.
This also allows working around certain email sending limits. Providers often set such thresholds to limit the maximum amount of emails which you can send within a minute/hour/day.

Available settings of this Limesurvey plugin

For every survey you can define the following details:

  1. Active = Activate automatic reminder sending for this survey
  2. Minimum date: Define a reminder sending start date. For the different follow up reminders you can set multiple, comma separated dates
  3. Interval = Number of days or hours which have to pass between the next reminder email and a previous reminder or invitation
  4. Interval unit = Set interval to X hours or days
  5. Maximum reminder count = Maximum number of reminders a participant should receive (so you do not spam your participants)
  6. Max batch size = Maximum number of emails the script will include at every script call

Installation of the Limesurvey cronjob script for sending email reminders

  • Firstly, download the plugin as ZIP file after payment. 
  • Limesurvey 3.x: Unzip all files. Then copy the “Reminder” folder to the Limesurvey “plugins” directory.
  • Limesurvey 5.x: Just upload the ZIP file at the plugin manager to install the plugin.
  • Activate the plugin at the Limesurvey plugin manager.
  • At any survey you can now activate the feature at the survey’s plugin settings.
  • Finally, set up the cronjob to automatically call the script every X minutes, hours or days. The script processes all surveys for which you activated the plugin.
    Depending on the way your provider is running cronjobs, try one of these commands:

    • php application/commands/console.php plugin –target=Reminder
    • php application/commands/console.php plugin index –target=Reminder
    • /usr/bin/php application/commands/console.php plugin –target=Reminder
  • The cronjob should be executed at least once a day. Cron tab setting for running it every night at 1 am: 0 1 * * * 

More information

 

Product Features

Limesurvey version

v3.x to 6.x, v3.x, v4.x, v5.x, v2.50 to v2.73.1, v2.05/2.06/2.6 LTS, v2.00

Recent updates:

2024-06-03 (Tested Limesurvey version 6.5.9):

  • 2.22.1 (2024-06-03) Fix: Error strtotime(null)
  • 2.22.0 (2024-05-17) Fix: PHP8 issues
  • 2.21.0 (2024-02-06) New Feature: Added pluginEvent reminderOnCustomHeaders to manipulate customHeaders array
  • 2.20.0 (2024-01-11) New feature: Added onDecorateEmail event to change body before sending email (eg. header and footer)

2023-12-05 (Tested Limesurvey version 5.6.48):

  • 2.19.1 (2023-12-05) Fix: Wrong path settings for URLs

2023-11-30 (Tested Limesurvey version 5.6.46):

  • 2.19.0 (2023-11-16) New feature: Max emails per script call
  • 2.18.1 (2023-11-08) Fix: Adjust baseUrl when showScriptName is false
  • 2.18.0 (2023-10-05) Extended logging feature, added global counter for logging
  • 2.17.0 (2023-09-08) Fix: Take global time adjust settings into account
  • 2.16.0 (2023-08-15) Fix: Optimized support for multiple email addresses
  • 2.15.0 (2023-07-26) New feature: Added @@OPTINURL@@ and @@OPTOUTURL@@ for replacements

2023-06-12 (Tested Limesurvey version 5.6.23):

  • 2.14.2 (2023-06-08) Adjustments for maxBatchSize
  • 2.14.1 (2023-06-07) New feature LS 6.x support
  • 2.14.0 (2023-06-01) Improvement: Extended reminderMinDate to optional comma separated list of dates
  • 2.13.0 (2023-05-23) New featrue: Plugin event reminderOnFieldsArray for replacements
  • 2.12.1 (2023-05-22) Fix: Missing classes by LimeSurveys ClassFactory after Limesurvey update
  • 2.12.0 (2023-05-08) New feature: Setting reminderMinDate for reminder sending start date
  • 2.11.1 (2023-05-08) Fix: Path to html2text
  • 2.11.0 (2023-04-28) New setActive() and setInactive() methods
  • 2.10.1 (2023-04-17) Fix for adding attachments
  • 2.10.0 (2023-03-27) New feature: Plugin event reminderBeforeRemind, supports onSurvey action
  • 2.9.2 (2023-02-28) New feature: Added {SID} to the replacements array
  • 2.9.0 (2022-12-05) New feature: Define interval in days or hours

2022-11-08 (Tested Limesurvey version 5.4.9):

  • 2.8.0: Added support for email attachments.

2022-10-26 (Tested Limesurvey version 5.4.8):

  • 2.7.1: Optimization for LS 5.x settings inheritance for HTML email setting

2022-09-30 (Tested Limesurvey version 5.3.4):

  • 2.7.0: New plugin events “reminderBeforeSendEmail” and “reminderEmailTexts” for easily extending plugin features
  • 2.6.0: Added advanced logging

2022-06-07 (Tested Limesurvey version 5.3.16):

  • 2.5.1 Added support for multiple email addresses
  • 2.5.0 Fixed token based placeholders

2021-12-20 (Tested Limesurvey version 5.2.x):

  • 2.4.0 Max batch size fix, show direct output on console

2021-12-10(Tested Limesurvey version 5.2.x):

  • 2.3.2 Added additional information for plugin settings

2021-11-30 (Tested Limesurvey version 3.27):

  • 2.3.0 Send plain text email when `htmlemail` is off
  • 2.2.0 Added inviterAdjustDateTime function to take global setting into account
  • 2.1.0 Added codeception tests + plugin settings footer

2021-09-30 Release of script version 2.0 (Tested Limesurvey version 3.27):

  • New setting at survey level to define the maximum batch size or set the script to send all emails in one run.

2021-06-19 (Tested Limesurvey version 3.27):

  • Added Limesurvey 4.x and 5.x compatibility
  • New feature to add baseUrl automatically when  activating the plugin
  • Added default settings to plugin settings
  • Fix: Support @@SURVEYURL@@ placeholder within email texts
  • Fix: Check start and expiry date properly before sending emails
  • Fix: Do not send emails to participants without a token

2020-09-22 (Tested Limesurvey version 3.23 and 4.3):

  • New setting ignoreBatchMaxSize added to allow unlimited emails during a single script run
  • Fixed for Limesurvey v4

2020-09-14 (Tested Limesurvey version 3.22.27):

  • Fully renewed version, turned into a Limesurvey plugin
  • Easier to adjust by using different plugin settings for every survey

2018-12-14 (Tested Limesurvey version 3.15.5+181115):

  • First release for Limesurvey 3.x

2017-10-17:

  • Fix for properly checking survey start and expiry date
  • Fix for correctly updating details at Central Participant Database (CPDB)

2016-06-20:

  • Include adjusted server setting for “reminder sent” timestamp

2016-05-02:

  • Added support for Limesurvey v2.50
  • Fixed optin/optout links within email texts

2016-02-05:

  • Added additional check to make sure each user has a valid token assigned

2016-01-28:

  • Improved batch size check to only send emails of a following survey if batch size was not reached