With the release of v2.0.0, we moved the inset, details and accordion blocks from a static to a dynamic implementation. Whilst, for now, those implementations should be backwards-compatible, this could present an issue if in future we want to change the markup output by those dynamic blocks. At that point, we could change the markup for any dynamic instances of the block just by updating the markup in the relevant render.php file. However, this would not change the output markup for any static instances of the block previously created by v1 of the plugin (as the entirety of the markup would have been saved in wp_posts at the point the post was last edited). The only way to convert those old static instances to dynamic would be either:
a) Go through the content manually, re-saving the posts via the editor (as at that point, it invisibly replaces the static instance with an equivalent dynamic one); or
b) Run a script to go through the database, identifying & replacing static instances with dynamic ones
With the release of v2.0.0, we moved the inset, details and accordion blocks from a static to a dynamic implementation. Whilst, for now, those implementations should be backwards-compatible, this could present an issue if in future we want to change the markup output by those dynamic blocks. At that point, we could change the markup for any dynamic instances of the block just by updating the markup in the relevant
render.phpfile. However, this would not change the output markup for any static instances of the block previously created by v1 of the plugin (as the entirety of the markup would have been saved in wp_posts at the point the post was last edited). The only way to convert those old static instances to dynamic would be either:a) Go through the content manually, re-saving the posts via the editor (as at that point, it invisibly replaces the static instance with an equivalent dynamic one); or
b) Run a script to go through the database, identifying & replacing static instances with dynamic ones