Update to 14.7 causes problems with NextGen

Hi,

We are unable to reproduce the issue. We installed NextGen v3.3.6 and using Yoast SEO v14.7 on WordPress 5.4.2 we were able to:

1. Create NextGen Gallery. See image: https://pasteboard.co/JlKFp3B.png
2. Insert it into a post. See image: https://pasteboard.co/JlKFwiF.png
3. And see the images on the front-end. See image: https://pasteboard.co/JlKFFqt.png

We are also able to edit the NextGen Gallery as a block and add images and they still appeared as expected on the front-end.

Can you confirm all your non-Yoast plugins and themes are updated?

Hi,
yes all my plugins are up-to-date.
Possibly it is related to NextGen Plus – I use version 1.6.29.

Hi,

Thanks for the information. It sounds like a plugin or theme conflict. Can you try and gather as much information for us as possible? Please perform the following:

1. If the issue only happens when Yoast is enabled, please Check for conflicts. Install the Healthcheck plugin and enable troubleshooting. Then switch to a standard theme like 2020. Does the issue resolve? NOTE: This will not affect how users see your site.

2. Check for JavaScript errors with your console.

If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue?for our developers. Please report the issue to a third party developer as well.

If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium?and receive our Premium email support and we can help you further.

I am having the same problem. It is absolutely related to Yoast SEO. I have about 80 websites here. Most use NextGen Gallery and Yoast SEO. When I updated the Yoast SEO plug in, it broke all of the NextGen Galleries.

We were able to trace the problem backward and are completely sure of this.

If I disable Yoast SEO and then recode the Galleries, they work.

I am hoping Yoast SEO can fix the problem or get with the NextGen Gallery developer to sort this out. It is on a number of forums now.

Thanks for any help you can offer.

Hi @innlight,

Thank you for chiming in. Are you also using the Plus version of Nextgen or using the free version? We ask since we don’t have access to their Plus version to troubleshoot and see if we can reproduce the error.

Looking at the last couple of forum topics over at the NextGen forums, their support reps are looking into fixing an issue with TinyMCE and their Classic Editor integration.

Can you @innlight, and @faithdanceart confirm if you are using the Gutenberg or the Classic Editor?

@faithdanceart, we see that the Plus version got a new version today, can you please update to their latest version and let us know if that helps?

I am using the free version of NextGen and also Yoast SEO.

And classic editor in wordpress. The theme I use is Avada.

There is a guy from Yoast who is working on the solution. You can see his post here:
https://github.com/Yoast/wordpress-seo/issues/15806

In short he says:

Djennez commented 22 minutes ago

I found the line of code that changed in 14.7 that causes this behavior, though I am still unsure as to why the behavior is happening. The problem is here:

wordpress-seo/admin/class-admin-asset-manager.php

Line 304 in 440cd20

‘wp-blocks’,

Our post-edit script seems to not get loaded on classic editor due to this wp-blocks dependency. That script probably has some magic that prevents expanded shortcodes from ending up in the text editor. This commit seems to have added this line. Will ask our developers to look into this.

• This reply was modified 4 years, 3 months ago by innlight.

Thank you @innlight to link that here.

I personally wasn’t aware of that GitHub issue and thank you for linking it here. My colleague Jannes is forwarding this to our development team. This means you’ll be able to follow the ticket there for further investigation. Thanks!

Thank you. Which plug in are you supporting? Yoast or NextGen? Really appreciate anything you can do. This affects dozens of my client’s websites.

Hi @innlight,

I was speaking as Yoast’s support team. There is, unfortunately, nothing else we can help with at this very moment. It’s now up to our development team to investigate. Please keep an eye on the Github issue, thank you!

You rock! Thanks so very much, Jeroen!!

I will keep an eye on Github.

Much appreciation to you for getting this over to the Yoast development team :o)

@innlight You’re welcome. We are going ahead and marking this issue as resolved but please let us know if you require any further assistance.

Hi Carl!

The problem is not solved. Unless the Yoast SEO plug in is disabled, NextGen galleries are not working. It somehow changes the code from a simple shortcode the a mass of confusion. See example of what the gallery code looks like after it has been affected by the Yoast SEO plug in.

<div class=”mceItem mceNonEditable nggPlaceholder”
id=”1597125761599″
data-shortcode=”ngg_images source="galleries" container_ids="5" display_type="photocrati-nextgen_basic_thumbnails" override_thumbnail_settings="0" thumbnail_width="240" thumbnail_height="160" thumbnail_crop="1" images_per_page="60" number_of_columns="0" ajax_pagination="0" show_all_in_lightbox="0" use_imagebrowser_effect="0" show_slideshow_link="0" slideshow_link_text="[Show slideshow]" order_by="sortorder" order_direction="ASC" returns="included" maximum_entity_count="500"”
data-mce-resize=”false”
data-mce-placeholder=”1″
contenteditable=”false”>
<h3>NextGEN Gallery</h3>
<div class=”nggPlaceholderButton nggIgwEdit”>
Edit
</div>
<div class=”nggPlaceholderButton nggIgwRemove”>
Delete
</div>

Reading the discussion on the other site shows me that this issue won’t be resolved until version 14.8 is out. Please let me know when this is the case.