Comments

jonathan1055 created an issue. See original summary.

joekers’s picture

I'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?

jonathan1055’s picture

Issue summary: View changes

OK, 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.

jonathan1055’s picture

jonathan1055’s picture

chr.fritsch’s picture

What about thinking bigger and using scheduler for all entities, not only nodes. Would be awesome to schedule media entities or paragraphs for example

jonathan1055’s picture

Thanks 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.

jonathan1055’s picture

Issue summary: View changes

Added #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.

pfrenssen’s picture

As 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.

pfrenssen’s picture

Issue summary: View changes
pfrenssen’s picture

I 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.

pfrenssen’s picture

@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.

jonathan1055’s picture

Thanks 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.

pfrenssen’s picture

It 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.

legovaer’s picture

Issue summary: View changes
jonathan1055’s picture

@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?

legovaer’s picture

Issue summary: View changes

Sorry, must have happened by accident!

jonathan1055’s picture

Issue summary: View changes

No 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

jonathan1055’s picture

Issue summary: View changes

Moved #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.

jonathan1055’s picture

jonathan1055’s picture

Issue summary: View changes

#2644208: Convert tokens to Drupal 8 is fixed. Thanks @joekers.

pfrenssen’s picture

pfrenssen’s picture

Issue summary: View changes

Moving #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.

jonathan1055’s picture

jonathan1055’s picture

legovaer’s picture

Issue summary: View changes
legovaer’s picture

Issue summary: View changes
jonathan1055’s picture

Issue summary: View changes

Added #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.

jonathan1055’s picture

jonathan1055’s picture

jonathan1055’s picture

Issue summary: View changes

Now 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.

pfrenssen’s picture

Great news!! Congratulations!

jonathan1055’s picture

joekers’s picture

Great work on releasing the alpha guys! :)

jonathan1055’s picture

jonathan1055’s picture

Issue summary: View changes

Added #2790459: Move Rules integration code into a sub-module for accurate dependencies and I think this should be resolved before alpha2.

jonathan1055’s picture

jonathan1055’s picture

jonathan1055’s picture

jonathan1055’s picture

Issue summary: View changes

I have created 8.x-1.0-rc1

pfrenssen’s picture

Yay!! Congratulations!

pfrenssen’s picture

I 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!

jonathan1055’s picture

Issue summary: View changes

Hi 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

balra06’s picture

Hi,

Is the Scheduler integration with workbench moderation targetted in release 8.x-1.0 ??
When can we expect the new release ??

Thanks,
Radha.

jonathan1055’s picture

Hi 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

balra06’s picture

Hi 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.

jonathan1055’s picture

Hello 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

balra06’s picture

Hi 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.

jonathan1055’s picture

Issue summary: View changes

Added 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

jonathan1055’s picture

jonathan1055’s picture

Issue summary: View changes

We now have a full release for Drupal 8 - whoop!

https://www.drupal.org/project/scheduler/releases/8.x-1.0

jonathan1055’s picture

Issue summary: View changes

Fixed #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.3

frankx’s picture

Few 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?

Chris Matthews’s picture

This 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)

jonathan1055’s picture

Status: Active » Fixed
Related issues: +#3030243: Plan for Scheduler 8.x-1.1 release

Thanks Chris, yes you are right. I have created #3030243: Plan for Scheduler 8.x-1.1 release

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

jonathan1055’s picture

Assigned: jonathan1055 » Unassigned

Unassigning myself from this closed issues.