David Bennett

It’s not a plugin – it’s on the server side.

On the site with the problem it is Litespeed Version 2.6.4.1

There’s only

Manage
Settings
Information

I don’t see a ‘Report’ section in the sidebar listing for Litespeed on that site.

I am using the same theme on another host where LiteSpeed is built in server side – and no problems with that site rendering genericons.

With the theme.

Hi Guido,
I am going to rely on the theme developer to make sure the themes I am using are ready for Gutenberg when it is ready to work with adding/editing products.

Until that happens I will disable Gutenberg with the Ramp plugin or the Classic Editor plugin (have to find out which is better to use) on my WooCommerce sites.

David

I got an answer from someone in a Facebook group who pointed me to the discussion group for WooCommerce developers on Github. In it, Mike Jolley said back in May that:

Since WooCommerce is not optimised for the Gutenberg editor we’ve decided to keep the old editor for now so sites do not break when WordPress 5.0 is released. Products are not content focussed so using Gutenberg with our meta box placed awkwardly at the bottom is not ideal.

And back in February, Cladiu Lodromanean said:

It’s just temporary until we develop nice Gutenberg-compatible screens for Products/Orders/etc. When Gutenberg is merged into WP core and released we will be ready with the Products block in WooCommerce 3.4 but editing products and orders in Gutenberg will come in a future WooCommerce release.

So now I know and I will be following the discussion on Github more closely.

That said, what this illustrates for me is that WooCommerce has a communication problem. They should be giving a roadmap to users and not just to developers who know to look in Github.

Can we get that?

Yes that’s what I mean. I say they are needed because otherwise newbies might simply not recognise that they can be toggled on/off

@designsimply

No, I mean there are no checkboxes, so no visual clue that checkmarks can be added.

See this mockup https://cloudup.com/cCjopFC-l8L

Thanks – I get that.

I tried that earlier. There’s nothing in the error log and debug didn’t make a log file at all.

However, I solved it. There was a folder named with the name of my site, sitting outside public.html – nothing in it. I renamed it to .comx. and that allowed me in.

I’ll try debug again to see what comes up.

Yes, tried different browser, VPN, and haven’t changed login URL

I have the same problem with my site. Got it this morning. Last night I had admin panel open and Transmit FTP connection open. Decided to clear browser cookies this morning and wondered whether that triggered it. Tried logging in from different IP addresses.

Many thanks, that did it.