meta data for this page
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
plugin:autoresponder [2024/05/03 06:23] – [Managing autoresponders] duncanc | plugin:autoresponder [2024/06/22 20:07] (current) – [Upgrading from version 2 to version 3] duncanc | ||
---|---|---|---|
Line 2: | Line 2: | ||
---- plugin ---- | ---- plugin ---- | ||
+ | |||
description: | description: | ||
author | author | ||
Line 34: | Line 35: | ||
The necessary change is to clear the userselection field on the message table using an update query similar to this | The necessary change is to clear the userselection field on the message table using an update query similar to this | ||
- | '' | + | <code sql> |
- | set userselection = null'' | + | update phplist_message |
+ | set userselection = null | ||
+ | </ | ||
In version 3 the plugin no longer uses the attribute that was created for each autoresponder by version 2 of the plugin. It is safe to delete any such attribute through the Configure Attributes page in phpList. | In version 3 the plugin no longer uses the attribute that was created for each autoresponder by version 2 of the plugin. It is safe to delete any such attribute through the Configure Attributes page in phpList. | ||
Line 100: | Line 103: | ||
The phplist process queue command needs to be run periodically. This allows the plugin to check for subscribers who now need to be sent an autoresponder campaign and to submit that campaign. | The phplist process queue command needs to be run periodically. This allows the plugin to check for subscribers who now need to be sent an autoresponder campaign and to submit that campaign. | ||
- | The recommended way of running process queue is through a cron job so that it is automated. The frequency | + | The recommended way of running process queue is through a cron job so that it is automated. The frequency |
For example, if an autoresponder has a period of 1 day, then running the cron job every hour means that the campaign will be sent within 25 hours of subscribing (not 24 hours). For a new subscription, | For example, if an autoresponder has a period of 1 day, then running the cron job every hour means that the campaign will be sent within 25 hours of subscribing (not 24 hours). For a new subscription, |