Closed (fixed)
Project:
Simplenews Scheduler
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2009 at 07:10 UTC
Updated:
2 Dec 2009 at 10:10 UTC
Hi
Newsletter editions are created even when After a maximum number of editions option is specified zero for the Scheduler settings.
Thanks
Comments
Comment #1
sgabe commentedThat was a bug in the database query which should have return with the maximum number of editions in the simplenews_scheduler_new_edition() function. Fixed and committed, please check and report back!
Comment #2
whan commentedHi
I have downloaded the new code and tried to send news letters at the specified date and time, this time the newsletter edition not being created again, but the newsletters are not being sent to the subscribed mail addresses. When I select
the send only option without scheduling option the Newsletters are sent to the subscribed addresses.
Thanks
Comment #3
sgabe commentedWhat settings did you try exactly? Is there anything in the watchdog regarding the failed sending or anything else?
Comment #4
whan commentedHi Sgabe,
I have selected the Send newsletter according to schedule and set the date and time and the After a maximum number of editions option which is zero. I have run the cron manually after the specified date and time mentioned in the Newletter scheduler settings. The watchdog message reads "Newsletter not send: node does not exist (nid = ; vid = ).".
Thanks
Comment #5
sgabe commentedIf you set the maximum to 0, there will be none newsletter sent. If you want to send a newsletter just once, you have to set the maximum to 1. The original node will be never sent just it's new editions. I think the deleted nodes and left behind newsletters cause the error message. You should try with a clean slate (empty the node and newsletter related tables in the database) and the correct settings.
Comment #6
whan commentedHi
The module works with the maximum no. of editions set to 1. I don't get the error message after emptying the table.
Thanks