Scheduler 7.x-1.3 was released on 12th November 2014. Here are the issues relating to the changes and additions since 1.2.
New features
- New function to allow other modules to know when a process is being done during scheduler cron.
#2168861: Use drupal_static() to indicate when scheduler_cron is running - Invoke hook_scheduler_api() during 'publish immediately' process.
#2260017: Let other modules interact during "publish immediately" - Additional date elements when entering the schedule date.
#2278557: Allow month name and three-letter month abbreviation in the date format - Flexibility for non-admin users to view the full scheduled list.
#2355401: New permission 'view scheduled content'
Bug fixes
- Compatibility with PostgreSQL database.
#1708488: PostgreSQL - Countdown field error - unix_timestamp() does not exist - Fix _scheduler_allow() to initialise the result to TRUE and use correct logic.
#2164147: Correction for _scheduler_allow - Avoid using strptime() and fix tests to check the conversion.
#2184517: Fatal error: Call to undefined function strptime() - Fix array warning.
#2205809: Warning: trim() expects parameter 1 to be string, array given in _scheduler_strtotime() - Use drupal_exit() so that all hook_exit() functions are invoked at end of lightweight cron.
#2250309: Call drupal_exit() instead of exit() in _scheduler_run_cron (and notes on avoiding drush error) - Correct the syntax for D7 Feeds module.
#2257301: Update for D7 Feeds.module API - Allow scheduled unpublishing to run as planned regardless of status.
#2355129: Remove test for $status=1 before unpublishing - Avoid calling _scheduler_allow(publish) when not setting an publish-on date.
#2358157: Do not call _scheduler_allow(publish) when scheduling an unpublish date - Add validation to check unpublish-on when editing an unpublished node.
#2365707: Missing validation allows Unpublish date to be blank
Usability improvements
- Better use of 'default time' functionality.
#2143061: The 'date only' option must be turned on for a format with no time element - Validate and improve consistency in date and time letters.
#2187361: Validate the date format letters and reorganise _scheduler_strptime() - Better information on the Timecheck tab.
#2188945: Improve the timecheck page - Repeat the 'Scheduled Content' tab on administration page.
#2256411: Add 'Scheduled content' tab to the admin pages - Multiple improvements to the controlling cron publish/unpublish functions.
#2311273: Tidy up _scheduler_publish() and _scheduler_unpublish()
Standards and code improvements
- Fix two badly-formed translation strings.
#2360295: Two translation string warnings
Comments
Comment #1
jonathan1055 commentedComment #2
jonathan1055 commentedComment #3
jonathan1055 commentedComment #4
jonathan1055 commentedAdded #2260017: Let other modules interact during "publish immediately"
Comment #5
jonathan1055 commentedAdded #1708488: PostgreSQL - Countdown field error - unix_timestamp() does not exist
Comment #6
jonathan1055 commentedAdded #2164147: Correction for _scheduler_allow
Comment #7
jonathan1055 commentedComment #8
jonathan1055 commentedAdded #2311273: Tidy up _scheduler_publish() and _scheduler_unpublish()
Comment #9
jonathan1055 commentedAdded #2278557: Allow month name and three-letter month abbreviation in the date format
Comment #10
jonathan1055 commentedAdded #2143061: The 'date only' option must be turned on for a format with no time element
Comment #11
jonathan1055 commentedAdded #2355129: Remove test for $status=1 before unpublishing
Comment #12
jonathan1055 commentedAdded #2355401: New permission 'view scheduled content'
Comment #13
jonathan1055 commentedAdded #2360295: Two translation string warnings and
#2365707: Missing validation allows Unpublish date to be blank
Comment #14
pfrenssenComment #15
jonathan1055 commentedAdded #2358157: Do not call _scheduler_allow(publish) when scheduling an unpublish date
Comment #16
jonathan1055 commentedRemoved
#2170353: Reduce memory footprint
Comment #17
jonathan1055 commentedUpdated intro text after release of 1.3
Comment #18
pfrenssenClosing since this is done now. Thanks for all the hard work on this!
Comment #19
jonathan1055 commented... and thank you too! It's been a good effort.
It will be interesting to watch the usages statistics to see how quickly users install 1.3 and whether that correlates with any increase in issues/bugs discovered which we have not found.
Comment #20
pfrenssenI expect adoption to be rather swift since it is a security release. I will be monitoring the queue closely in the following days to see if bugs are reported. Up to now everything is quiet, that's positive :)