Open stephen-cox opened 3 months ago
I think this needs fixing in localgov_core. Once the default block installer service has figured out what ID it should be using for a block, it should check if that ID is in use before trying to save it.
I've realised this is probably yet another case where we need to add and check the $is_syncing param, but I think what I already proposed to add the check for existing IDs is worth doing too, as it'll make the block installer slightly more robust.
Ive just followed the steps to recreate with
"localgovdrupal/localgov_core": "dev-fix/2.x/245-installing-site-from-existing-config-fails as 2.13.7"
And the site installs from config successfully now, with publications enabled.
Error is: 'block' entity with ID 'localgov_base_publication_navigation' already exists.
Steps to reproduce
Delete the install_localgov hook from the profile or patch core from https://www.drupal.org/project/drupal/issues/2982052
Exception trace