[Support request] Block element not working because of classic editor?

[robert]

Hi Folks!

I have a client with a WooCommerce webshop. This webshop was originally built with the Astra theme, and Elementor. The webshop wasn’t functioning properly because the web-guy used about 70 (!!!) plugins to make it all work. Bottom line is that at the end, it didn’t 🙂

So, I went back to the basics, and made a new shop in my beloved GP-theme, and instead of using Elementor (which to me is like shooting an ant with a bazooka) I’m using just Woocommerce category pages, and for the homepage (shop page with category layout) I made a header in the block elements. Works great on my testenvironment.

The new layout is now installed on the live shop, and we’re currently debugging stuff (because some of the used plugins might still be needed, i haven’t yet deleted all plugins). Of the 70 plugins, there are now 28 active plugins.

The issue I have, is that I imported some elements from my testsite to the live shop. All went fine accept the block element. I think this is because the ‘classic editor’ was still running at the time of the import.
When I go to elements, instead of “new element” is see “nieuw bericht” (which means new post). So it looks like the post type; block element wasn’t injected properly.

The block element was imported, but I couldn’t see the actual blocks. Nor can I select the block element in the element dropdown. Nothing changes when I try to import the block element again after deleting it. It seems i’m stuck with this block element.

Is there a way to completely eliminate the traces of the classic editor without wiping the entire shop? It has 600 products in it 🙂

I uploaded images to my own site, so you can see my issues.(placed them in the credential field for safety)

Hope you can help, thanks in advance!

[robert]

p.s. no caching is active at the moment, as i always switch this off when i’m working on a site.

[David]

Hi there,

so just to be clear on some things:

1, Are you using the latest version of GP Premium?
2. Are you using the Classic Editor Plugin ? And if so in the plugin settings is the Option to allow users to Switch Editors enabled ?

As a note – if you do disable the Classic Editor plugin then any classic pages that can be edited via the block editor will simply output its content inside a Classic Editor Block…. i would suggest doing this on a staging site just to be extra safe

[robert]

Hi David,
Sorry for my late reply, I forgot to check the box for notifications 🙂
Thanks for the quick response!

In response to your questions:
1: yes, I am using the lastest versions of GP and gp premium. Everything is up to date.
2: no, I am not using the classic editor anymore on this site (to avoid more issues). Before deleting it, I tried to fiddle around with these settings to solve the problem, but that didnt work.

The content that used to be in a classic editor has now been converted into ‘normal blocks’. The thing is, I have no issues with the block editor at all, accept for the block element that’s not correctly imported or submitted as a post type. (is that the way it works? Will it be added as a custom post type? Because in my screenshot it says; ‘add new post’ instead of add new element. Which to me seems the source of the problem.)

Cheers!

[robert]

In addition, I also tried to switch back to the old theme (which is still in there), and I also deleted the GP premium plugin and reinstalled it.

(now when I think of it, I typically use an older one because it’s in my standard plugin folder, and then after installation, I update it to the newest version.)
I’ll try to download the newest version directly to see if that solves the problem.

Client is already really happy about the improvement in performance, so this nitpicking is completely from my side. I cannot stand it when things don’t work as they should 🙂

[robert]

YEEEEEEEEEHAAAAAAAAAW!!!!! it worked.
For some reason the version was 1.9.something.
Deleted the plugin, upped the latest version, and voila!

The button now states: add new element.

Hope this helps anyone with the same issue.

[David]

Glad to hear you found the issue and the solution 🙂

[robert]

Thanks for the help!

[Author]

Posts