There are only updates for a user with frequency: WEEKLY.
But also a user with frequency DAILY will receice a mail with the content of the WEEKLY update.
This happens when the user with DAILY frequency has an ID (subscriber_id) larger than the ID (subscriber_id) of the user with the WEEKLY frequency.
The larger IDs (subscriber_id) are processed after the lower IDs (subscriber_id).
Analysis:
In jms_latestnews_js.php:
if (!$rows) --> the return gives an empty $list,
but in emails.php after $results = Factory::getApplication()->triggerEvent(...) the content of $list is the same as the former WEEKLY update
I tried to debug, but did not find a solution and I have no futher idea.
Work-a-around:
Process first all IDs (subscriber_id) with frequency DAILY and after that the IDs (subscriber_id) with frequency WEEKLY in emails.php:
Modification:
Replace:
with:
Regards,
Peter
But also a user with frequency DAILY will receice a mail with the content of the WEEKLY update.
This happens when the user with DAILY frequency has an ID (subscriber_id) larger than the ID (subscriber_id) of the user with the WEEKLY frequency.
The larger IDs (subscriber_id) are processed after the lower IDs (subscriber_id).
Analysis:
In jms_latestnews_js.php:
if (!$rows) --> the return gives an empty $list,
but in emails.php after $results = Factory::getApplication()->triggerEvent(...) the content of $list is the same as the former WEEKLY update
I tried to debug, but did not find a solution and I have no futher idea.
Work-a-around:
Process first all IDs (subscriber_id) with frequency DAILY and after that the IDs (subscriber_id) with frequency WEEKLY in emails.php:
Modification:
Replace:
" . $whr
with:
" . $whr . " ORDER BY e.frequency";
Regards,
Peter