-
I have multiple sites that migrate from v1 to v2 GenerateBlocks.
If I toggle to v2 I can use the new blocks. Legacy blocks still work.BUT duplicating or coping a generateblocks/container block won’t change its uniqueId anymore.
If I toggle back to v1 the uniqueIds are handled fine, but I can’t access the new blocks.Is there code to patch the regeneration of uniqueIds for container blocks in v2-mode?
Or is there a way to migrate all container blocks to element blocks? -
Hello,
BUT duplicating or coping a generateblocks/container block won’t change its uniqueId anymore.
Are you referring to v1 blocks in this case?
-
Yes, as far as I saw it the “Container Block” results in a generateblocks/container tag in V1 and in a generateblocks/element in V2.
My assumption is that switching the toggle to V2 leads to copying the uniqueId without regenerating it as a hook for the V1 gp/container tag is missing or something like that.
-
Hello,
I am not able to recreate it locally. What I am doing:
1. v1 blocks active. I create a v1 container block and save the page.
2. I enable v2 blocks, then refresh the page I was editing and try duplicating the v1 container block. I can see from the code editor that a new ID has been regenerated.If you don’t see that, is it possible to give us access to your installation so I can test? You can also install the Temporary Login Without Password plugin and send us a login link without using a password. Please, use the private area of your reply to send those details.
- You must be logged in to reply to this topic.