Lynqoid

For anyone else looking at this, I fixed this by setting up the shortcode correctly, make sure you add the target_page = permalink attribute to the pbd_search shortcode.

It’s worth noting that ACF currently says:

Testing ACF with Gutenberg is going great. I’m happy to see how well Custom Meta Boxes are being supported in this new JS powered edit screen – everything seems to be working out of the box! The only issues are due to changed actions and filters, which will require some minor compatibility patches. As the Gutenberg project continues to develop, we will continue to test and roll out updates.

So it’s not quite there yet with Gutenberg and Gutenberg isn’t quite there yet too. I personally am going to keep an eye on ACF updates and Gutenberg updates to see when I can start testing some of my own ACF built templates, exciting times ahead!

https://www.advancedcustomfields.com/blog/exciting-developments-coming-acf-2018/

However, since I use that for one or two important pages, I’m not going to remove it for the sake of a beta plugin.

I think that’s the important part, I wouldn’t remove any of my plugins that I use on an active site either just for a beta, regardless of how far along the beta was. I would wait until it’s no longer a beta. Although it exists for testing and messing around with, which is cool.

You will be able to use https://www.ads-software.com/plugins/classic-editor/ to disable Gutenberg if you wish. I believe WooCommerce are updating the plugin to be more compatible with Gutenberg (this might have already started) so it’s worth keeping an eye on that.

This plugin: https://www.ads-software.com/plugins/classic-editor/ has been shared around which will provide the ability to disable Gutenberg if required.

I would like to think of these errors will be fixed along the way, fingers crossed! ??

When you added the plugin, did you see a Gutenberg item added to the admin menu, down the bottom left?

It’s just an example plugin at the moment that shows you what it can do.

Thanks, I’ll take a look later.

So just check if $term is set? I wonder if that is what is_woocommerce() uses too, to see if it’s a woocommerce template? I’ll investigate! ??