Gutenberg: Front-end markup doesn't update when Gutenberg updates

Created on 18 Jul 2018 · 6Comments · Source: WordPress/gutenberg

Describe the bug
I had a test page that I had created months ago. On the page it had a Multi-Column block (among lots of others). Up until only recently, the Multi-Column block was using CSS Grid. Recently, this has now changed to use Flexbox and more importantly, the content for each column is contained within its own container/div.

Even though my Gutenberg plugin was up to date, when I viewed this page on the front-end, it was still using the old markup (i.e. The blocks for each column weren't in their own container/div). The markup only changed to the new format once the page was re-saved.

Hypothetically, what happens in say 5 years time, when some new css grid spec is all the rage and WP is updated to use this all-new fancy grid? Is my page that I created 5 year earlier, still going to use the old markup? Based on the what I just saw with my old page, it would. I shouldn't have to go back and re-save all my old pages so that the front-end markup updates.

Obviously the most logical answer is no, I wouldn't have to re-save my old pages. In that case though, why did I just have to resave my old page now before seeing the new markup? How is this going to be avoided once Gutenberg is in core?

_Gutenberg 3.2.0_

Backwards Compatibility [Feature] Extensibility [Type] Documentation [Type] Question

Source

maddisondesigns

👍2

Most helpful comment

Further to that discussion @maddisondesigns What happens when you have that block on 1,000 of pages. How will you update the block. Are you going to sit there and press "update" on every 1,000 pages?
@danielbachhuber is the intention to add this functionality to the extend api? I've personally hit a roadblock with not being able to update existing blocks with more functionality inside our save, return function.