Mark Spencer

I installed the WP Downgrade plugin to return to 5.5.3. However, my WP dashboard says I’m running 5.6.1 (I disabled auto update after the 5.6 fiasco).

What’s funny is I have two WP installations on essentially two websites (the issue is on a subdomain and the database is separate from the primary domain). On the primary domain, everything works just fine. On the subdomain – the featured image portion just will not load in the block editor.

I use the subdomain to serve several clients and right now is our busy time of year so taking the site down to upgrade to 5.6.1 to see if the issue is resolved and whatnot is not exactly something I can do at the moment.

I installed the jQuery Migrate tool as well and wouldn’t you know – no issues! So after about a month of running it, I got tired of the messages and uninstalled it.

My feeling (and I’m very, very far from being an expert) is that there is an issue in the jQuery database since WP was using such an outdated version. Seems like the project was rushed to meet a deadline or for some other reason. Either way, WP’s complete disregard for the issue and instead just blaming the end user (it’s so easy to do) is rather disappointing. I get they’re volunteers but seriously – this is a native to Gutenberg and the default editor. I don’t run a plugin that affects how the editor functions just the native block editor that comes with every install of WP. And yet, alas, I’m getting the blame.

While I primarily use Firefox, others who have accounts on my website also had the same issue using a different browser (most use Chrome).

How would I set the height and width of a span? Not sure where I would go to set this for a featured image.

Glad it is not just me. Really feel the issue is with the core WP script itself (being that in the default WP editor, “featured image” is WP native and no a feature of a plugin or theme).

I reverted back to WP 5.5 and installed the jquery migrate helper plugin, which tells me everything is just fine – no errors.

I am confident others are having the issue and that WP will correct it in a future release. There’s a lot of chatter among the WP sympathizers of how “wonderfully awesome WP 5.6” and how “nothing is wrong” and if anything is that it’s the fault of a theme or plugin.

Don’t get me wrong, I like WordPress. It’s extremely powerful and versatile. Just don’t sit there and tell me a native feature to WP is the fault of a theme or plugin when that’s an outright lie.

They don’t seem to understand how a massive jquery library change can affect even small things I guess……

That requires me to upgrade to version 5.6, which isn’t going to happen right now. I use the website having issues as a client portal and right now it’s not a good time to introduce that risk, which I already know is with the core WordPress code and not a plugin or a theme.

Olga is ignoring the featured image issue… which is NOT A DARN PLUGIN!

Care to actually respond why a native WordPress feature in Word Press’ native editor will not work in version 5.6 or just throw more BS out there instead?

I have my site set to most everything updates automatically and I constantly check for updates to ensure I got the latest theme/plugin updates. The site uses X theme (Themeco) and is up to date. I ensured all plugins were up to date prior to posting here.

I did experience an issue with a plugin I use, but I will take that up their their support team.

The issue I posted here about dealt with adding a featured image to a post. We use the standard Gutenberg editor that WordPress is built around and the featured image is a part of that. What happens in version 5.6 when you click the button to add a featured image is the pop up box to add an image displays but is blank. Waiting several minutes, no changes. That’s not a theme or plugin issue, that’s a WordPress issue.

It is odd though that another site I have updated to version 5.6 (and uses the same theme) did not have this issue.

In the meantime, I reverted back to WP version 5.5 to temporarily solve the issue. I think WordPress jumped the gun with their jQuery library update and essentially shoved it down everyone’s throats without much time to react. That’s a major jump in library versions they are making.