I'm running into an error after upgrading recurring_events from RC2 to RC 5. It occurs on two sites, one with a few events (its a new feature) and one with hundreds.
Its reproduced selecting an existing event, changing the dates to a further future time span, then confirming to allow deleting/ recreating instances for the series. Following confirmation the error shows NOTICE: PHP message: Uncaught PHP Exception Drupal\Core\Entity\EntityStorageException: "The "" plugin does not exist. Valid plugin IDs for Drupal\recurring_events\EventInstanceCreatorPluginManager are: recurring_events_eventinstance_recreator" at /app/web/core/lib/Drupal/Core/Entity/Sql/SqlContentEntityStorage.php line 811
Issue fork recurring_events-3316080
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
ll66382 commentedComment #3
owenbush commentedThe plugin should be getting set in a hook update, did database updates run?
https://git.drupalcode.org/project/recurring_events/-/blob/2.0.x/recurri...
Comment #4
ll66382 commentedMoving from rc2 => rc5 I see these with an drush deploy and the updb step--
Comment #5
ll66382 commentedComment #6
owenbush commentedI can see two problems here
Firstly, recurring_events_registration_8009 looks to be failing. That's likely a problem I need to address in the module.
Secondly, the update to set the plugin recurring_events_eventinstance_recreator seems to be running successfully, but then your config import afterwards is likely undoing it. So you need to export the new plugin setting to your recurring_events.eventseries.config file and commit that to version control. Because if you do not do that, every time you run an import it will be wiping out the new plugin setting resulting in the problem you raised this issue for.
Comment #7
muriqui commentedJust ran into this bug, too, but on a clean install and without the registration submodule enabled. Steps to reproduce:
Result:
Edit: This test was with the current 2.0.x, not 2.0-rc5.
Comment #9
muriqui commentedOK, found one problem: Commit c3f500eb90fbec47a1492bc51954411c915dbe60 made a config change in recurring_events_update_8014(), but that change wasn't added to config/install/recurring_events.eventseries.config.yml, so new installs of the module don't receive it. I've added the missing config in MR 53.
This fixed the issue for me, but probably doesn't resolve the OP's issue transitioning from RC2 to RC5.
Comment #12
owenbush commentedGreat find, thank you. I've committed that MR.
I'll take a look at 8009 failing separately to that config change.
Comment #13
aaronbaumanI ran into the same issue on #3319567: WSOD when updating event series definition
There's another issue which is that the config form doesn't save the value.
Comment #14
aaronbaumanNevermind, this MR appears to have been merged even though the issue is open.
Following up on #3319567: WSOD when updating event series definition
Comment #15
audiomason commentedI encountered this issue today. I was able to resolve it using the configuration sync UI by exporting the recurring_events.eventseries.config, adding the creator_plugin parameter from #11, and importing the modified config.