- πΊπΈUnited States SocialNicheGuru
And it needs to be updated to Drupal 10
- πΊπΈUnited States SocialNicheGuru
if you disable the module you need to do a cache clear or you might get:
Class "Drupal\scheduler\Plugin\Field\FieldType\SchedulerRepeaterItem" does not exist in ReflectionClass->__construct() (line 26 of drupal10.2.6/html/modules/contrib/date_recur/src/DateRecurCachedHooks.php)
- ππ°Hong Kong richard cheung
Does this patch support content moderation?
- πΊπΈUnited States danflanagan8 St. Louis, US
This would be a great feature, to be sure. I mostly like the implementation in the patch in #28. I'd probably rather have less in the module file and more in a service, but that's no big deal.
The patch didn't work for me though. I had to add a
$node->save();
near the end ofDrupal\scheduler_repeat\EventSubscriber::unpublish()
. I'm using scheduler 2.x. Scheduler itself saves the unpublished entity before dispatching the unpublish event, so we have to save it ourselves if we want our changes to persist.As for #29:
Does this patch support content moderation?
Short answer is no. Long answer is that scheduler always needs the Scheduler content moderation integration β module to work with workflows. Even with that module enabled, the repeater doesn't quite work. The reason is that the
publish_state
andunpublish_state
get reset on publish and unpublish respectively by thescheduler_content_moderation_integration
module which means they cease to be available for thescheduler_repeater
module.So that's a pain. Getting this to play nice with
scheduler_content_moderation_integration
might require a patch over there.