Closed geerlingguy closed 4 years ago
Heh, now I remember. There's a whole bunch of semi-related issues here:
There's even a module to help with this problem (Recreate Block Content), but that's yet-another-module-to-fix-one-tiny-thing that I don't want to have to rely on.
I might add some sort of hook that connects the migrated block to that instance with the different UUID in code, maybe? Or make this another 'manual step after completing the migration' :/
I'm going to just stick with #55 — manually recreating the blocks on reinstall. If this were a much greater effort over a longer period of time I'd figure out a way to get it to work out of the box, but since I want to get this thing launched... I'll just go ahead and do it manually.
When I migrate the site now, I get:
For the front page
block-whatido
block. I'm guessing that the configuration has a UUID that is installed when the site is installed, but the migration creates a different block UUID when I run the migration, and the configuration is referencing a block that doesn't exist.I seem to remember running into this same issue in the past before :(