NextGen Gallery and Feed RSS

NGG is adding that snippet via anonymous function, which is super annoying by the way.

Thankfully there is a temporary solution by @toscho on WordPress Stack Exchange.

Copy his function and paste it into your currently active WordPress theme’s functions.php file.

Then copy/paste this into your currently active WordPress theme’s functions.php file as well.

function kill_anonymous_example(){
    remove_anonymous_object_filter(
        'wp_footer',
        'C_Photocrati_Resource_Manager',
        'print_marker'
    );
}
add_action('wp_footer', 'kill_anonymous_example', -2);

That removed it and my feed works again.

@jump88 – Are you still seeing this issue with version 2.0.59?

@michael Ecklund – Thanks for offering this work-around.

– Cais.

I am experiencing the same issue and using the code snipet did not resolve my issue. I am using 2.0.59. When I deactivate the plugin, the RSS feed works correctly.

-Erik

@edunger – Given that many RSS issues are intermittent if/when NextGEN Gallery is active I would suggest you start your own topic, especially since the suggested work-around did not sort things out for you.

– Cais.

For me the error has brought by the latest version of WordPress SEO by Yoast. Go back to the previous version (1.5.2.4) worked for me.
With NextGEN 2.0.59 / WordPress SEO 1.5.2.4 the result is this
With NextGEN 2.0.59 / WordPress SEO 1.5.2.5 the result is this:

Sorry
This feed does not validate.
    line 2, column 1: Undefined root element: script [help]
        	<script type="text/javascript">
     ^
    line 21, column 0: XML parsing error: <unknown>:21:0: junk after document element [help]
        <?xml version="1.0" encoding="UTF-8"?>
In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation.
    "text/xml" media type is not specific enough [help]

Here the same:

<!-- ngg_resource_manager_marker -->	<script type="text/javascript">
		(function() {
			var request, b = document.body, c = 'className', cs = 'customize-support', rcs = new RegExp('(^|\\s+)(no-)?'+cs+'(\\s+|$)');

			request = true;

			b[c] = b[c].replace( rcs, ' ' );
			b[c] += ( window.postMessage && request ? ' ' : ' no-' ) + cs;
		}());
	</script>
			<div id="wpadminbar" class="nojq nojs" role="navigation">

…and then the whole adminarbar-code ’til

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"

begins.

Same problem for me :
https://www.street-photographers.com/feed

Any idea ?

Thanx

Really really bad!

Getting this problem as well for a clients site and unfortunately Michael’s fix just kills the RSS feed completely.

Any update on a fix?

All – It would seem this is related to the recent WordPress SEO update as @tizz noted, or it may be something entirely different but in any case it would be much more productive to create your own topic for your specific site so it can be addressed.

If necessary, you are also welcome to submit a Bug Report (https://www.nextgen-gallery.com/report-bug/) for this issue but if you are using the latest WordPress SEO you may also want to report this to Yoast as well.

Thanks!

– Cais.

Except it’s not, photocrati. I had this exact problem and when I saw this thread and thought “Oh, well, then” and disabled WordPress SEO. The feed was still broken. So I disabled NextGEN and VIOLA! feed is working fine. Re-activated WordPress SEO and the feed is still fine. Now I can’t re-activate NextGEN without getting a white screen of death.

Great..

Sorry, I spoke too soon. In the beginning the validator gave me the above error (…junk after document element…) and typing my address/feed/ the same error of @supajug.
The other day, in the situation described above, after clearing the cache several times the error seemed to disappear at all, and I’ve seen my feed page as asual. In fact, the issue disappeared for half.
Then, as now, even with some recommendations the validator still says the feed is valid – maybe it’s because I’ve disabled UTF-8 blog charset support in W3TC, I don’t know – but the same issue of @supajug is still present in my feed page. Disabling Nextgen feed page is visible and the validation is 100%.

Hi tizz, how did u go to your previous version of SEO, please help

@toolsqa You can find previous versions here, but I don’t think you’ll solve the issue in that way. As said, after the first moment in which I’ve seen my feeds right, the issue then came back, even if my feeds does validate they aren’t working at all.

I was plagued with this problem as well and found a working solution here: https://www.kriesi.at/support/topic/rss-feed-not-working-anymore/

The important bit:

Tried this in wp-content/plugins/nextgen-gallery/non_pope/class.photocrati_resource_manager.php

function print_marker()
    {
if(is_feed()) return;
        print $this->marker;
    }

Seems to work.