plaidpiper

I’m also interested in a solution for this. Seems like the missing piece of the puzzle.

Never mind, looks like this is an error related to another plugin.

An update has been issued for the pro version which fixes layout bugs in the new editor UI.

Loads of Kioken stuff doesn’t work properly in the new Gutenberg UI now as well. Nightmare.

@sj_o So simple! I hadn’t considered the default option as something that would affect the blog, I had my mind stuck on it being a ‘page’

Thanks for the video, really cleared it up.

Keep up the great work –

From a happy user of Kioken Blocks and GutenBooster

@jokanane @traed @raymondoamw – I’ve had exactly this issue too.

We setup a new site for a client in 3.6.5.

We meticulously put everything together in gutenberg then read the changelog for 3.7 and saw nothing that would have meant more work. So we updated – then this!

@shellbeezy – This sort of thing has to be be in change logs! Depending on how many sites this block is used in, this could result in hours of unplanned work.

Also, a bit surprised you were unaware of the blocks being in core since 3.6 (see line 126 here https://github.com/woocommerce/woocommerce/blob/master/CHANGELOG.txt)

Surely, the way it worked prior to 3.7, with classes that matched the product loop was much more compatible with themes out of the box?

Hoping this can be reverted in the next release.

• This reply was modified 5 years, 2 months ago by plaidpiper.