Additions:
You can enable the repetition feature in your [[PhpListConfiguration config.php]] file:
# Repetition. This adds the option to repeat the same message in the future.
# After the message has been sent, this option will cause the system to automatically
# create a new message with the same content. Be careful with it, because you may
# send the same message to your users
# the embargo of the message will be increased with the repetition interval you choose
# also read the README.repetition for more info
define("USE_REPETITION",1);
# Repetition. This adds the option to repeat the same message in the future.
# After the message has been sent, this option will cause the system to automatically
# create a new message with the same content. Be careful with it, because you may
# send the same message to your users
# the embargo of the message will be increased with the repetition interval you choose
# also read the README.repetition for more info
define("USE_REPETITION",1);
Revision [1022]
Edited on 2006-12-21 05:51:25 by AlStillero [added breadcrumb trail + some edits + formatting]Additions:
==[[PhplistDocumentation Phplist Documentation]] » [[MessageFunctionsInfo Message functions]] » ==
=== Explanation of repetition feature ===
PHPlist can automatically re-schedule your messages after sending it. It will create an exact copy of your message. This can be used to work in conjunction with file system attachments. If you want PHPlist to send you some file from the server at a regular interval, the filesystem attachment will be refreshed at the moment of sending the (first) message.
As of version 2.10.x the repetition feature can also work in conjunction with the [URL] feature, which allows the inclusion of dynamically created web pages --for instance, a web page that changes every day or every hour can be sent as a daily or hourly message.
**Note**: see below for a bug fix, usually necessary to make this feature work.
Even if you set PHPlist to send every certain interval, you can still tell it to NOT send (ie re-schedule) the message at certain moments, by using the repeat_exclude setting in config.php, and adding the following to your config file:
You can add as many entries as you like and the format is as follows:
where the bits between [ and ] can be chosen as you like it, but they have to fit the following:
- ##[format]## needs to be a [[http://www.mysql.com/doc/en/Date_and_time_functions.html MySQL data format string]]
- ##[list of values]## needs to be a list of values that this format can return, which then, if matched with the new "embargo" for a message will not create a message for that date, but instead increases the "repetition value" to find the next one in a row.
So for example, for excluding the weekend you would use:
and for excluding specific dates you can use:
A typical use of the repetition feature is with sending a web page with dynamic content. In PHPList 2.10.2 and earlier, there is a bug that seems to affect many or most PHPList installations. PHPList caches the dynamic web page, and the bug keeps PHPList from checking/updating the dynamic web page as needed.
So, if you use the repetition feature with a dynamic web page as message content, but find that the content of the email never updates, look at this bug report and the suggested fix: http://mantis.phplist.com/view.php?id=7684
==Related pages==
- [[MessageFunctionsInfo Message functions]]
=== Explanation of repetition feature ===
PHPlist can automatically re-schedule your messages after sending it. It will create an exact copy of your message. This can be used to work in conjunction with file system attachments. If you want PHPlist to send you some file from the server at a regular interval, the filesystem attachment will be refreshed at the moment of sending the (first) message.
As of version 2.10.x the repetition feature can also work in conjunction with the [URL] feature, which allows the inclusion of dynamically created web pages --for instance, a web page that changes every day or every hour can be sent as a daily or hourly message.
**Note**: see below for a bug fix, usually necessary to make this feature work.
Even if you set PHPlist to send every certain interval, you can still tell it to NOT send (ie re-schedule) the message at certain moments, by using the repeat_exclude setting in config.php, and adding the following to your config file:
You can add as many entries as you like and the format is as follows:
where the bits between [ and ] can be chosen as you like it, but they have to fit the following:
- ##[format]## needs to be a [[http://www.mysql.com/doc/en/Date_and_time_functions.html MySQL data format string]]
- ##[list of values]## needs to be a list of values that this format can return, which then, if matched with the new "embargo" for a message will not create a message for that date, but instead increases the "repetition value" to find the next one in a row.
So for example, for excluding the weekend you would use:
and for excluding specific dates you can use:
A typical use of the repetition feature is with sending a web page with dynamic content. In PHPList 2.10.2 and earlier, there is a bug that seems to affect many or most PHPList installations. PHPList caches the dynamic web page, and the bug keeps PHPList from checking/updating the dynamic web page as needed.
So, if you use the repetition feature with a dynamic web page as message content, but find that the content of the email never updates, look at this bug report and the suggested fix: http://mantis.phplist.com/view.php?id=7684
==Related pages==
- [[MessageFunctionsInfo Message functions]]
Deletions:
=== explanation of repetition feature ===
PHPlist can now automatically re-schedule your messages after sending it. It will create an exact copy of your message, which is generally not what you want, so it's probably not that useful yet.
It will become useful once we have added the functionality to the system to allow for dynamic content of messages (ie automated retrieval of some webpage)
For now (version 2.7.x), it's only use will be to work in conjunction with file system attachments. If you want PHPlist to send you some file from the server at a regular interval, the filesystem attachment will be refreshed at the moment of sending the (first) message.
As of version 2.10.x it also will use the [URL] feature to allow inclusion of dynamically created web pages--for instance, a web page that changes every day or every hour can be sent as a daily or hourly message. (However see below for a bug fix usually necessary to make this feature work.)
Even if you set PHPlist to send every certain interval, you can still tell it to
NOT send (ie re-schedule) the message at certain moments. You do this as follows:
You add the following to your config file
Now that needs a bit of explanation. You can add as many entries as you like and
the format is as follows:
one entry is formatted
where the bits between [ and ] can be chosen as you like it, but they have to fit
the following:
##[format]## needs to be a Mysql data format string which you can find at
http://www.mysql.com/doc/en/Date_and_time_functions.html under "Date Format"
##[list of values]## needs to be a list of values that this format can return, which then, if matched with the new "embargo" for a message will not create a message for that date, but instead increases the "repetition value" to find the next one in a row.
So for example for excluding the weekend you use
and for excluding specific dates you can use
Typically in using the repetition feature you will include a web page with dynamic content.
In PHPList 2.10.2 and earlier, there is a bug that seems to affect many or most PHPList installations. PHPList caches the dynamic web page, and the bug keeps PHPList from checking/updating the dynamic web page as needed.
So if you use repetition with a dynamic web page as message content, but find that the content of the email never updates, look at this bug and the mod suggested to fix that problem:
Bug 0007684: cache problems with included web page in message: http://mantis.phplist.com/view.php?id=7684
Additions:
=== explanation of repetition feature ===
PHPlist can now automatically re-schedule your messages after sending it. It will create an exact copy of your message, which is generally not what you want, so it's probably not that useful yet.
It will become useful once we have added the functionality to the system to allow for dynamic content of messages (ie automated retrieval of some webpage)
For now (version 2.7.x), it's only use will be to work in conjunction with file system attachments. If you want PHPlist to send you some file from the server at a regular interval, the filesystem attachment will be refreshed at the moment of sending the (first) message.
===Exclusion of times and dates===
%%(php)
# exclude dates for repetition
%%
%%(php)
array("format" => [format], "values" => array([list of values])),%%
##[format]## needs to be a Mysql data format string which you can find at
##[list of values]## needs to be a list of values that this format can return, which then, if matched with the new "embargo" for a message will not create a message for that date, but instead increases the "repetition value" to find the next one in a row.
%%(php) array("format" => "%a", "values" => array("Sun","Sat")),%%
%%(php) array("format" => "%d-%m-%Y","values" => array("31-01-2004","28-08-2004")),%%
===A bug===
PHPlist can now automatically re-schedule your messages after sending it. It will create an exact copy of your message, which is generally not what you want, so it's probably not that useful yet.
It will become useful once we have added the functionality to the system to allow for dynamic content of messages (ie automated retrieval of some webpage)
For now (version 2.7.x), it's only use will be to work in conjunction with file system attachments. If you want PHPlist to send you some file from the server at a regular interval, the filesystem attachment will be refreshed at the moment of sending the (first) message.
===Exclusion of times and dates===
%%(php)
# exclude dates for repetition
%%
%%(php)
array("format" => [format], "values" => array([list of values])),%%
##[format]## needs to be a Mysql data format string which you can find at
##[list of values]## needs to be a list of values that this format can return, which then, if matched with the new "embargo" for a message will not create a message for that date, but instead increases the "repetition value" to find the next one in a row.
%%(php) array("format" => "%a", "values" => array("Sun","Sat")),%%
%%(php) array("format" => "%d-%m-%Y","values" => array("31-01-2004","28-08-2004")),%%
===A bug===
Deletions:
PHPlist can now automatically re-schedule your messages after sending it. It will
create an exact copy of your message, which is generally not what you want, so it's
probably not that useful yet.
It will become useful once we have added the functionality to the system to allow
for dynamic content of messages (ie automated retrieval of some webpage)
For now (version 2.7.x), it's only use will be to work in conjunction with file system
attachments. If you want PHPlist to send you some file from the server at a regular interval,
the filesystem attachment will be refreshed at the moment of sending the (first) message.
*Exclusion of times and dates*
#// exclude dates for repetition
#// end
array("format" => [format], "values" => array([list of values])),
[format] needs to be a Mysql data format string which you can find at
[list of values] needs to be a list of values that this format can return,
which then, if matched with the new "embargo" for a message will not create a
message for that date, but instead increases the "repetition value" to find the
next one in a row.
array("format" => "%d-%m-%Y","values" => array("31-01-2004","28-08-2004")),
==A bug==
