The latest dev release is 8.x-1.x-dev
Issues which must be resolved before the next release
Other issues which are not blockers for the next release
#2333359: Why should unpublishing date be later than publishing one?
#2416135: Provide separate tab for node scheduling
#2651348: Port Rules integration for Scheduler to Drupal 8 Assigned to: jonathan1055
#2651354: Port Feeds integration to Drupal 8
#2705499: Replace drupal_set_message() with an injectible service
#2707411: Conflict between 'required publishing' and not having scheduler permission Assigned to: jonathan1055
#2708957: SchedulerManager throws exception on receiving EntityManagerWrapper from web profiler
#2712465: 8.x test coverage Assigned to: jonathan1055
#2731587: Refresh schema and config settings after upgrading to new version
#2824015: Inconsistency in "changed" timestamp when publishing in the past
#2868553: Fix the code to adhere to Drupal Best Practice
#2871164: Ensure Scheduler dates and status field have consistent translatable settings
Fixed issues which will be included in the next release
#2924353: Tag rules_integration tests with @group legacy
For earlier fixed issues see:
8.x-1.0 released 14th November 2017
8.x-1.0-rc2 released 7th August 2017
8.x-1.0-rc1 released 19th April 2017
8.x-1.0-alpha2 released 15th September 2016
8.x-1.0-alpha1 released 17th May 2016
Comments
Comment #2
joekersI'm not sure of the progress on #2594615: Automated testing in 8.x [meta] but I feel that it should go in to the "Issues which must be resolved before 8.x-1.0-alpha1" group?
Comment #3
jonathan1055 CreditAttribution: jonathan1055 commentedOK, yes you are probably right. I have now added that. Progress is very good - take a look at the summary of #2594615: Automated testing in 8.x [meta]. With the exception of the API test file all of the other failing classes have patches which fix the code.
When #2655666: API Testing module - conversion to 8.x is done we can fix the final tests.
Comment #4
jonathan1055 CreditAttribution: jonathan1055 commented#2615592: Convert hook_help to use routes is now fixed
Comment #5
jonathan1055 CreditAttribution: jonathan1055 commentedFixed #2626480: scheduler/cron needs a route controller and hence also #2426627: [meta] Convert all page callbacks to routes
Moved #2655666: API Testing module - conversion to 8.x into the 'must resolve' list as it is a pre-requisite for fixing #2594615: Automated testing in 8.x [meta]
Comment #6
chr.fritschWhat about thinking bigger and using scheduler for all entities, not only nodes. Would be awesome to schedule media entities or paragraphs for example
Comment #7
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThanks chr.fritsch. This issue is not the place to discuss the details, as here we track progress of the most important issues to get our first alpha release.
However we have got an issue for that idea already #2096585: Support for non-node entities, e.g. Media, Commerce Products, Custom 3rd-party entities and your ideas would be very welcome.
Comment #8
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #2666832: Publish in the past sets date to 1970-01-01
@joekers Thinking about it again, I'm not sure #2594615: Automated testing in 8.x [meta] is technically a blocker. Each of the faults have their own issues (which are in the blockers list), and that meta issue may be used to track new tests which are not complete by the time we want to release alpha1. I've moved it back to the nice-to-have list.
Comment #9
pfrenssenAs soon as we have a release we have to provide upgrade paths between releases. I think the most important issue that is blocking an alpha release is #2651338: Create a service for the Scheduler API. This is an API change for which an upgrade path is impossible.
I wouldn't be comfortable releasing Scheduler with the current "API". The current implementation is really bad,
hook_scheduler_api()
is a relic that dates from Drupal 4.7 and has never been updated. We should replace this with proper event listeners.Comment #10
pfrenssenComment #11
pfrenssenI took a look at the alpha blockers with this mindset: "As a developer of a cutting edge Drupal 8 site, consciously using alpha releases of modules while being aware of the risks it involves, would I find it acceptable that this issue is present in an alpha release?"
#2625572: Admin setting 'Enable content type for scheduler' is ignored - This seems to break the really basic usage of Scheduler. Definitely an alpha target.
#2644690: Include default time processing in datetime widget for 8.x - OK to remove this from alpha target for me, I don't think the default time is part of the "80% case".
#2651338: Create a service for the Scheduler API - Hard blocker for alpha since it is an API change.
#2651448: Publish and Unpublish fields are shown for users who do not have the permission - Security issue, hard blocker for alpha.
#2655666: API Testing module - conversion to 8.x - Testing issue, not a hard blocker, is fine to do later, but needs to get in before beta.
#2666832: Publish in the past sets date to 1970-01-01 - A regular bug fix, I would be OK removing this from the alpha target.
Other issues which are not blockers for alpha1
#2592293: Test access to scheduled node views - OK. Testing issue, not a blocker.
#2594615: Automated testing in 8.x [meta] - OK. Testing issue, not a blocker.
#2629820: [meta] node edit validation - Meta issue, not a blocker.
#2633870: Revisit defaults for third party settings - This requires an upgrade path, I would prefer to promote this to a blocker, I think it's also very near completion.
#2644208: Convert tokens to Drupal 8 - OK, not an "80% case", not a blocker.
#2651344: Change unavailable_after meta tag to HTTP Header X-Robots-Tag - OK, not very important, more a "nice to have", not a blocker.
#2651348: Port Rules integration for Scheduler to Drupal 8 - OK, not an "80% case", not a blocker.
#2651354: Port Feeds integration to Drupal 8 - OK, not an "80% case", not a blocker.
#2659824: Exclude node types that do not have scheduling enabled - OK, not very important, more a "nice to have", not a blocker.
Comment #12
pfrenssen@chr.fritsch, I would love to support all entities in Scheduler, but it's not realistic to still do this now, we are trying to get an alpha release out of the door, and this would require a complete rewrite. I think this is something for a 8.x-2.x release of Scheduler. Let's discuss in #2096585: Support for non-node entities, e.g. Media, Commerce Products, Custom 3rd-party entities.
Comment #13
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThanks for the detailed analysis. Its good to say the scenario you put yourself in, when viewing each of the issues. Very helpful.
So, in summary, your changes are:
Move into the alpha-blockers list
#2651338: Create a service for the Scheduler API
#2633870: Revisit defaults for third party settings
I'm happy with both of these suggestions. Thanks for explaining the importance of getting the new service in at the alpha stage, particularly as there is no upgrade path.
Move out of the alpha-blockers list
#2644690: Include default time processing in datetime widget for 8.x
#2655666: API Testing module - conversion to 8.x
Whilst these issues in themselves may not be blockers, they do have well tested patches which each fix current failing classes in the automated tests. Getting the current tests to all pass will help the development of every future issue we work on, as not only will we immediately see if the work breaks exitsing code, but the issue will not always be set back to 'needs work', which gives the impression that it is not ready for review. I'd be ready to commit both of these patches now, and get two more classes passing, but have refrained because it is good to get a second opinion. We do have patches for every failing class at the moment, so we can get a fully green set of tests right away, then we can concentrate on the more difficult issues.
#2666832: Publish in the past sets date to 1970-01-01 This has just been RTBC by you and committed by me.
Comment #14
pfrenssenIt looks like we're very close on many of these issues. I'll try getting some review time in this week. I've been very much strapped for time lately as I have moved to a different country and am in the process of starting up a new company. It will take a few more weeks for things to completely settle down on my end.
Comment #15
legovaerComment #16
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented@legovaer Why did you delete #2659824: Exclude node types that do not have scheduling enabled ? It was not in the blocker list, but that second set of issues are all the ones we would generally want to do before beta release. It's good to keep this list in view in one single place, isn't it?
Comment #17
legovaerSorry, must have happened by accident!
Comment #18
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedNo worries.
I have now moved #2633870: Revisit defaults for third party settings into the blockers list, as per Pieter's request.
Also added a new non-blocker #2667692: Re-instate field_extra_fields for 8.x
Comment #19
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedMoved #2651448: Publish and Unpublish fields are shown for users who do not have the permission to the fixed list.
Added #2652036: Field widget set incorrectly after Scheduler module re-install to the non-blockers list.
Added @ after issue number inside the [ ] to automatically display the user assigned to the issue.
Comment #20
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented#2644690: Include default time processing in datetime widget for 8.x is fixed
Comment #21
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented#2644208: Convert tokens to Drupal 8 is fixed. Thanks @joekers.
Comment #22
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented#2625572: Admin setting 'Enable content type for scheduler' is ignored is fixed
#2651344: Change unavailable_after meta tag to HTTP Header X-Robots-Tag is fixed
Added #2669164: Introduce event subscriber for the Scheduler hooks
Comment #23
pfrenssen#2667692: Re-instate field_extra_fields for 8.x is fixed.
Comment #24
pfrenssenMoving #2669164: Introduce event subscriber for the Scheduler hooks to the list of blockers, since this will replace the existing hooks with event subscribers this is a major API change that is impossible to handle in an update hook.
Comment #25
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #1979462: Provide API documentation
Fixed #2633870: Revisit defaults for third party settings
Comment #26
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented#2655666: API Testing module - conversion to 8.x is fixed.
#2311273: Tidy up _scheduler_publish() and _scheduler_unpublish() is fixed.
Comment #27
legovaerComment #28
legovaerComment #29
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #2707411: Conflict between 'required publishing' and not having scheduler permission Assigned to: jonathan1055
This is not a blocker for alpha1 but should be high up in the importance list for fixing before alpha2.
Comment #30
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #2365707: Missing validation allows Unpublish date to be blank to the fixed list.
Comment #31
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded
#2682579: Move constants out of global space into settings and schema
#2712465: 8.x test coverage Assigned to: jonathan1055
#2714135: Remove unused constants which are now in config
Fixed
#2594615: Automated testing in 8.x [meta]
Comment #32
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedNow that #2669164: Introduce event subscriber for the Scheduler hooks is complete, I have released 8.x-1.0-alpha1! Thank you Pieter, Levi, Joe and everyone else who has contributed to get us this far.
OK, so which issues shall we tackle next, for alpha2? I think #2652036: Field widget set incorrectly after Scheduler module re-install is the most important, because currently Scheduler is broken after a re-install and needs admin changes to the date widget settings. This should be fixable in code.
Comment #33
pfrenssenGreat news!! Congratulations!
Comment #34
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded a link to the alpha1 page, which has all the issues which contributed to that release, and deleted them form this issue summary.
Moved into blockers:
#2592293: Test access to scheduled node views
#2652036: Field widget set incorrectly after Scheduler module re-install
#2682579: Move constants out of global space into settings and schema
Added:
#2416135: Provide separate tab for node scheduling
#2490570: Validate that the 'publish on' value matches the expected format
#2490578: Validate that the 'unpublish on' value matches the expected format
#2700209: Disable node access checks during cron publish/unpublish
Deleted:
#2714135: Remove unused constants which are now in config
On a separate subject, for a great alternative visual listing of the Scheduler queue take a look at https://contribkanban.com/board/scheduler
Comment #35
joekersGreat work on releasing the alpha guys! :)
Comment #36
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded:
#2731587: Refresh schema and config settings after upgrading to new version
#2732223: Update readme.txt for 8.x
Fixed:
#2682579: Move constants out of global space into settings and schema
#2741263: Add composer.json file for Scheduler
Comment #37
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #2751495: Uninstalling Scheduler 8.x-1.0-alpha1 deletes all fields on content types which is a major blocker
Added #2708957: SchedulerManager throws exception on receiving EntityManagerWrapper from web profiler
Fixed #2311273: Tidy up _scheduler_publish() and _scheduler_unpublish()
Comment #38
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded
#2754919: Add configuration link for Scheduler on modules page.
#2755665: Restore original access requirement for scheduled content overview.
#2756147: Remove @file tag docblock from .php files where the class matches the filename
#2757625: Previously passing tests now fail in Drupal 8.2 - Change assertRaw to assertText
Removed
#2652036: Field widget set incorrectly after Scheduler module re-install
#2751495: Uninstalling Scheduler 8.x-1.0-alpha1 deletes all fields on content types
Comment #39
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #2771375: Use dependency injection for routeMatch() in ScheduledListAccess
Moved to Fixed
#2592293: Test access to scheduled node views
#2732223: Update readme.txt for 8.x
#2755665: Restore original access requirement for scheduled content overview.
#2767635: Scheduled content view has wrong id
Comment #40
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedFixed
#2771613: Improvements to Scheduled Content view
#2771375: Use dependency injection for routeMatch() in ScheduledListAccess
#2659824: Exclude node types that do not have scheduling enabled
There is one problem which should be corrected before alpha2 - reported in #28 of #2651348-28: Port Rules integration for Scheduler to Drupal 8 where we get an error if the Rules module is not enabled.
Comment #41
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded #2790459: Move Rules integration code into a sub-module for accurate dependencies and I think this should be resolved before alpha2.
Comment #42
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAfter committing #2790459: Move Rules integration code into a sub-module for accurate dependencies and #2790471: When editing a block: Fatal error: Class 'Core\RulesConditionBase' not found I have now released 8.x-1.0-alpha2
Comment #43
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded
#2333359: Why should unpublishing date be later than publishing one?
#2776665: Support for multi-lingual translations and differing scheduled dates
#2781433: Replace deprecated usage of Drupal::url in .install status report
#2789515: Drush task for lightweight cron
#2799095: Fix schema error in scheduled content view. Status value should be string not boolean
#2799869: Date field placeholder text doesn't reflect date format defined in admin settings - hardcode the format
Now we need to decide on the priorities for the next release. Maybe we should tackle the date entry methods (widget and text) and date validation rules.
Comment #44
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThese are now fixed:
#2700209: Disable node access checks during cron publish/unpublish
#2790459: Move Rules integration code into a sub-module for accurate dependencies
#2790471: When editing a block: Fatal error: Class 'Core\RulesConditionBase' not found
#2803049: Scheduler Module is conflicting with View_unpublished module
Comment #45
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commented#2790459: Move Rules integration code into a sub-module for accurate dependencies
#2790471: When editing a block: Fatal error: Class 'Core\RulesConditionBase' not found
Removed these as they are already in the alpha2 release.
Comment #46
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded:
#2807081: Better label for TimestampDatetimeNoDefault widget
#2809627: Fix DefaultTime test for daylight-saving
#2824366: Move tests from /src/tests to tests/src/functional and extend BrowserTestBase instead of WebTestBase
#2831429: Date format placeholders not replaced in error message
Fixed:
#2781433: Replace deprecated usage of Drupal::url in .install status report
#2799095: Fix schema error in scheduled content view. Status value should be string not boolean
Comment #47
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedBlockers now fixed:
#2824366: Move tests from /src/tests to tests/src/functional and extend BrowserTestBase instead of WebTestBase
and #2831429: Date format placeholders not replaced in error message
Also fixed:
#2789515: Drush task for lightweight cron
#2848213: Give warning when wrong datetime field widget is set
#2861902: Fix coding standards violations in 8.x codebase
#2861909: Exit early to avoid unnecessary processing in hook_form_NODE_FORM_alter
#2867269: Replace db_select() and db_update() which are deprecated
One new non-blocker not done yet
#2868553: Fix the code to adhere to Drupal Best Practice
I think it is time for a new release. Jumping straight to rc1.
Comment #48
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedFixed #2776665: Support for multi-lingual translations and differing scheduled dates
Added #2871164: Ensure Scheduler dates and status field have consistent translatable settings as a follow-up.
Comment #49
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedI have created 8.x-1.0-rc1
Comment #50
pfrenssenYay!! Congratulations!
Comment #51
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded:
#2851618: Rules automated tests fail at D8.3 and 8.4
#2871164: Ensure Scheduler dates and status field have consistent translatable settings
Fixed:
#2873108: Amend Scheduler tests in preparation for core 8.4 change to 'save' button
#2874410: Tests with assertFieldById fail to find field at 8.3 and 8.4, ok at 8.2
Comment #52
pfrenssenI had a look through the issue queue and the module seems to be in pretty great shape. The release blockers for 8.x-1.0-RC2 are done, there are no major or critical issues in the queue (and none have been reported in the past 6 months!). We have almost reached a very healthy 5000 active users on Drupal 8.
I have the feeling that the module is almost ready for a full 1.0 release. What do you think about cutting the RC2 soon, and providing a grace period of 2 months? If no major or critical issues are reported in this period then we can go for the full 8.x-1.0 release. We could announce this on the project page, and ask our users to do some final testing for major problems or security issues.
Thanks Jonathan for your tireless efforts!
Comment #53
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedHi Pieter,
Thanks for your reply, good to hear from you! Yes I think we are generally in quite good shape for a RC2 release soon. I've been trying to work out which of the issues will be harder to resolve for our users after a 1.0 full release. The only major problem I see can is how we deal with the Scheduler text format, which is admin-defined but not actually used apart from in messages. It is causing more problems than it solves and I am tempted to remove it from the admin config page and use a standard format. The issue is #2799869: Date field placeholder text doesn't reflect date format defined in admin settings - hardcode the format and this this would also allow the validation issues to be closed. I think if we are doing this, it should be before RC2.
Jonathan
Comment #54
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded
#2824015: Inconsistency in "changed" timestamp when publishing in the past
#2884680: Remove field_ui dependency
#2843425: Add PRE_PUBLISH_IMMEDIATELY event to allow other modules to react before the node is published
#2890778: Populate the scheduler date fields for content created by Devel Generate
#2849490: Scheduler + Calendar module throws notice for "Undefined index: id"
Comment #55
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedFixed
#2799869: Date field placeholder text doesn't reflect date format defined in admin settings - hardcode the format
#2629820: [meta] node edit validation
Removed
#2490570: Validate that the 'publish on' value matches the expected format
#2490578: Validate that the 'unpublish on' value matches the expected format
I have created a new release https://www.drupal.org/project/scheduler/releases/8.x-1.0-rc2 and if no new major bugs are reported in the next two months I will release 8.x-1.0
Comment #56
balra06 CreditAttribution: balra06 commentedHi,
Is the Scheduler integration with workbench moderation targetted in release 8.x-1.0 ??
When can we expect the new release ??
Thanks,
Radha.
Comment #57
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedHi Radha,
No, the integration with workbench moderation will not be part of Scheduler 8.x-1.0. See #2820026: Drupal 8 version of Scheduler Workbench Integration
Jonathan
Comment #58
balra06 CreditAttribution: balra06 commentedHi Jonathan,
Thanks for the reply.Is there any workaround available ?
We would want the features available with the scheduler like sending email notification , throwing an error if we try to schedule an article prior to the current time n date.
Scheduled Update module does not do an automatic update and it does not have the above features mentioned and moreover its not covered b the security policy
We are using workbench moderation and we would need the scheduler functionality to be implement with above features.
Do we have to end up writing a new module ? or can we do some workaround and use the scheduler module
Thanks,
Radha.
Comment #59
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedHello again balra06/Radha,
You have lots of requirements and ask for many things, some of which are covered in Scheduler and others can be catered for with Scheduler + Rules. Others may be provided if and when Workbench Integration gets started. This issue is specifically for tracking the progress towards our 8.x-1.0 release so please discuss those requests on other issue threads.
I know that you are new on drupal.org so I will cut you some slack, but you do not need to ask the same question on multiple issues and e-mail the project maintainers directly, when we are following the issues and are responding in good time. I am giving all my drupal work for free, spending my own spare time on it, and when you say "We need" and "We want" and "When can we expect" this type of language does not encourage me to assist you any faster ;-)
Jonathan
Comment #60
balra06 CreditAttribution: balra06 commentedHi Jonathan,
This is really a great module... i am totally new to this and just wanted a confirmation before we take a decision on the requirements we have.
Thanks for all your responses so far ..I am pretty much clear now ..
I was under an impression that some work is already happening out there so just was checking out on if we can expect anything out in the new release .. was not enforcing on any requirements :)
Thanks,
Radha.
Comment #61
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedAdded new issue #2902512: Call to a member function getThirdPartySetting() on null which is a blocker for 8.x-1.0
But we do have a bonus new feature #2916738: Enable TRAVIS build and create custom phpcs.xml
Comment #62
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedFixed:
#2902512: Call to a member function getThirdPartySetting() on null
#2921593: Remove unrequired dependency on Action module
I think it is time for release 8.x-1.0
Comment #63
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedWe now have a full release for Drupal 8 - whoop!
https://www.drupal.org/project/scheduler/releases/8.x-1.0
Comment #64
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedFixed #2924353: Tag rules_integration tests with @group legacy
Tests now pass again at 8.5. We cannot remove the
@group legacy
until #2922757: Replace deprecated RouteEnhancerInterface, then remove @group legacy which may be quite some time if the new classes are not backported to 8.4 and 8.3Comment #65
frankx CreditAttribution: frankx commentedFew days before i started a web project with Drupal 863. and tried to use the module scheduler to publich and unpublich content. by setting of unpublished time, the content is still to see on the website, when the setted time is already over. Is that normal?
Comment #66
Chris Matthews CreditAttribution: Chris Matthews commentedThis issue is titled "Progress towards 8.x release of Scheduler", which of course has already been accomplished. With that said, can this issue be marked as fixed and a new issue be opened titled: "Plan for Scheduler 8.x-1.1 release" (I think it gets confusing trying to manage plans for multiple releases on the same issue node. In other words, it's probably best to have a unique plan issue node for each new release)
Comment #67
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedThanks Chris, yes you are right. I have created #3030243: Plan for Scheduler 8.x-1.1 release
Comment #69
jonathan1055 CreditAttribution: jonathan1055 as a volunteer commentedUnassigning myself from this closed issues.