Is NGG Selecting All Images on a Page?

  • It seems that NGG is selecting and acting on all images in our wp-admin area.

    We have a set of plugins we’re developing that in one area has a custom image upload and display area. To do that, there is a kind of template included as in a div that is not visible and is copied by our AJAX scripts and modified to build additional image related output that is dynamically added to another div. The img tags in that template have replaceable parameters until the AJAX scripts insert the new image names.

    The problem is that those are causing the following errors.

    [29-Dec-2015 20:45:07 UTC] Sorry, but recursing filters on “the_content” breaks NextGEN Gallery. Please see https://core.trac.www.ads-software.com/ticket/17817 and NGG_DISABLE_FILTER_THE_CONTENT

    These img tags in the temlate should have nothing to do with NGG, but clearly they are being selected and in some way acted upon that is causing the errors.

    So, is there a way to tell NGG to stay away from those img tags or the div containing our tempate?

    For the time being I’ve used temporary names for the tags instead of “img” and replacing that text also when using the template, but that’s awkward and I’m a bit concerned about NGG doing something with all images.

    Chuck

    https://www.ads-software.com/plugins/nextgen-gallery/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor photocrati

    (@photocrati)

    @n8dnx – You can try defining NGG_DISABLE_FILTER_THE_CONTENT to true in your wp-config.php file to see if that helps, otherwise I would suspect your code might possibly be over-reaching?

    – Cais.

    Thread Starter n8dnx

    (@n8dnx)

    Cais:

    Thanks for the response. My question then is what might we be disabling in NGG that we might need if we set NGG_DISABLE_FILTER_THE_CONTENT? Since I’m not the person here working with NGG, I don’t know what effect that might have.

    My other “real” question, is why NGG is looking at these img tags anyway. It’s doing this not as a result of my code, but simply because the img tags exist in my prototype for adding additional images (is included with the HTML sent to the browser). I have that prototype in my template because it can be different between image areas and pages.

    Plugin Contributor photocrati

    (@photocrati)

    @n8dnx – We use the <img> tag as a placeholder for displays inserted via the IGW (“green button”) in the TinyMCE editor’s visual tab … something within your code might be causing NextGEN Gallery to mistakenly try to work with your <img> tag usage … without the context of your code I cannot offer much more than that.

    As to using the constant, it is more a work-around than anything else … a stop-gap if you will until WordPress sorts out trac ticket #17817. It was introduced at a time when we had hoped/expected that ticket to be resolved and therefore essentially rendering the use of that constant as moot. What might break by using it … it depends, we strongly recommend a thorough review of your site’s active plugins and current theme to see if there are any effects.

    – Cais.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Is NGG Selecting All Images on a Page?’ is closed to new replies.