Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.I installed the new dev version to help test it, and so far I've noticed two things:
#1 After installing and running update.php, the new fields were not built into my database. sched_stop, sched_stop_date, and sched_stop_edition had to be built manually.
#2 When I save newsletter issues, I'm often (about 50% of the time) getting an Illegal Choice Detected error. My dblog shows:
Message Illegal choice 1988 in Year element.
Not sure why that's happening, I set the year to 2009.
Sorry I can't be more help in debugging this.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | simplenews_scheduler.580494_01.patch | 2.8 KB | sgabe |
Comments
Comment #1
sgabe commentedWhich version are you using exactly? There is a note on the project page to use the listed 6.x-1.x-dev release instead 6.x-2.x-dev. Moreover, 6.x-1.x has been updated 2 days ago.
Comment #2
djudd commentedI'm using 6.x-1.x-dev and I updated shortly after the update was put up. Sorry, I must have selected the wrong version in the dropdown when I filed this.
Comment #3
sgabe commentedThe new features are definetly missing the update procedure. Thanks for drawing attention to this. I will check up on the illegal choice error too. How can 1988 get there, if you set the year to 2009...
Comment #4
sgabe commentedThe update procedure is fixed and I made some changes to prevent illegal values for schedule. Check out the attached patch.
Comment #5
sgabe commentedI think the missing update procedure is fixed, and committed to the dev release. If anyone has further information about the illegal choice detected error, please share.
Comment #6
sgabe commentedThe stop date got it's default value from the database as given in the install file, that caused an illegal choice detected error while editing a newsletter issue. This bug is fixed, and will be committed in the dev release soon.
I change the title, and set this issue to fixed.