Our team is also running into this issue. It seems to be completely random whether our scripts fire off or not. Found that it's only when GTM scripts are attached, even if those do nothing at all. 2.0.5 works fine.
Main problem is I don't get any sort of error in the logs or console related to whatever is breaking.
Tested the changes made in the newest 1.x-dev branch.
In the D10.2.6 version the shim seems to be working correctly. No problems thrown in the console.
In the D10.3 beta the picker loads quickly instead of being stuck in a forever load.
Howdy all,
Hopefully this is the place for this.
We're using 10.2.5 currently with the patch from #141 (Also tested the following with #157 as well).
There is a issue we're running into with making inline blocks into reusable blocks.
If an inline block is made reusable and placed on multiple pages, but the original page is deleted then the block becomes broken.
This is happening after the layout_builder_cron() is run. It seems to disregard whether the block has the 'reusable' column set to '1' and removes the block from the database.
Steps to recreate:
1. Create a page
2. Create an inline block (any type)
3. Save the layout
4. Set the inline block to reusable
5. Create a new page
6. Add the reusable block to the new page
7. Delete the original page
8. Run Cron
9. The reusable block should be broken with text similar to "This block is broken or missing. You may be missing content or you might need to enable the original module."
10. In recent log messages you should see the block is broken after the layout_builder_cron() has completed its execution.
This only happens with inline-to-reusable, so if a block is created as reusable from the start there is no issue.
It also only occurs once the original page that the block was created on is deleted. If you delete the block from the original page, but don't delete the page the error will not happen. But as soon as you delete that page, whether it has the block or not, the block will break.
We haven't been able to solve this yet and we're hoping others might test and see if it's happening in their environments as well.