ispreview

Yes I noticed this too. Will await the fix.

Yes, although I’m quite shocked that NGG’s developers haven’t been on here yet to acknowledge the many problems being caused by their latest update.

Agreed here too. Gutenberg doesn’t work for me, I’m a professional writer and work in code, the Classic Editor suits all my needs.

The shortcode method doesn’t really work very well. You can’t see the image in the editor, so you don’t know what you’re looking at, and it seems to generate a div, a link and an imagine inside all of that, which is not the same thing.

Is there any plan to add this feature to Gutenberg in NGG before the Classic Editor is retired in a year’s time?

Ok done, thanks.

Yes it persists. I even deleted Yoast SEO in the beta install, then re-installed, but the issue remains.

Weirdly when I did this test again and disabled that plugin the “Featured Image” link still did not return, so I figured it must be some sort of combination with another plugin playing a role.

I tested again and found that this popular plugin is also causing the same problem when enabled:

“Yoast SEO”

Ok I found the conflicting plugin, it’s called:

“Advanced Editor Tools (previously TinyMCE Advanced)”

When enabled that one stops NGG from showing the Featured Image option in Gutenberg.

Hi @gabyimagely,

No it’s installed on my own dedicated server. I’m fairly certain it was working just after 5.5’s release, but then something changed with one of the NGG updates after that and it broke in Gutenberg again.

On the classic editor issue with the same problem, that one was given a temporary fix in the WP 5.5.1 release, which returned some of the old jQuery stuff and thus allowed the NGG featured image option to work (they plan to remove the temporary fix next March 2021, so I’m sure NGG will resolve that one before then).

• This reply was modified 4 years, 5 months ago by ispreview.

I should add that this shows up in PHP7.4 too, but under that version it’s merely deprecated so the error display itself is suppressed. I think you should ideally fix this before PHP8 as it does tend to fill up the error log files.

Worth saying that the release of WP 5.5.1 has provided a “temporary” fix for this by reintroducing some of the old jquery, but this is expected to be removed again early next year. At least that gives NextGen a bit longer to fix it.

I’ve got the same problem in Gutenberg, although I don’t have the “Stackable – Gutenberg Blocks” plugin like the above poster. As per my other bug report, the workaround of using “Classic Editor” is pointless right now as the link used to select an image is broken (doesn’t save your choice) since WP5.5 too.

Weirdly I think this did work under an earlier release of NextGen, so it was probably broken by one of the two post-5.5 NGG updates to the plugin. So for the time being we have to keep WordPress downgraded to 5.4.X as the loss of featured image support is too much of a problem.

Is there any idea which update this will appear in?

Yes I am referencing the settings not being saved problem.

Still getting the same error.