NextGen Gallery and Feed RSS

In my case it doesn’t help, WHEN you are logged in as the admin. Only the following was deleted:

<!-- ngg_resource_manager_marker -->

If you’re not logged in, it really helped.

For me is exactly the same as @sebastian Pertsch.

(In my case seems a conflict with the “scroll to top” button of my theme).

The fix that Ivan found resolved the issue I was having too.

Problem is still there and it is always with SEO Yoast, this is not the first time that these two plugins have problems together, the horrible thing is that they are blame each other. Yoast said it is Nextgen and Nextgen said it is Yoast.

I don’t care who it is, I want a solution for this.

Feed is not working

b[c] += ( window.postMessage && request ? ‘ ‘ : ‘ no-‘ ) + cs;
——————————————————^

@michael Ecklund you said twice the same and it doesn’t work at all

@ivan Novak for you the same .. it does not work !

Seems combined with the latest update and Ivan’s hack I now have a working feed again providing I’m not logged into WordPress. If logged in the feed is still a mess but at least that won’t affect my subscribers.

I don’t even have or use SEO Yoast and have the feed-problem as mentioned before.

i am having the same problem. NextGen, Yoast SEO and WP Canvas theme. Looking at the /feed page in browser gives:

This page contains the following errors:
error on line 3 at column 1: Extra content at the end of the document

Tried Ivan’s and Michael Ecklund’s fixes and neither made any difference.

In feed reader I get a message “The feed could not be loaded because the content is not in a known feed format.”

This is really a problem for my client because they have a MailChimp campaign that depends on the RSS feed and the emails have stopped working.

I just noticed this issue…broken RSS feed. Found this thread. Deactivated NextGen, feed fixed. Hope NextGen provides a fix soon. Luckily, I don’t use these galleries often.

I deactivated Yoast SEO and now the RSS feed is fine. I’ll look around for another SEO plugin. I would have gotten rid of NextGen but couldn’t do without it in this case because the client had been using it for years and accumulated many photo albums that were scattered throughout the site- too much work to un-do.

For me now it’s solved (I hope), Nextgen, Yoast and W3TC all in place and updated.
I think that the problem was because of some cache. After a while, the @ivan Novak fix has stopped working, also logged out.
I don’t know how but trying to fix another problem I solved that too, so at the end I think it was a cache problem, something that was jammed.
I had to disable W3TC and other plugins for some reasons, because the site was a mess.
Some W3TC files was missing, so I uninstalled it completely (even cleaning up .htaccess, wp-config and drop-in files), and I installed it again taking it from a back-up because with automatic install the necessary files were not self-recreated. When everything was back in place I also updated it. In all these steps I had to clean the cache and log-in/log-out several times.
At the end, just out of curiosity, I checked the feeds and, surprise, now they work, both logged-in and logged-out.
I don’t mean to say to uninstall completely and install again W3TC as I done because it’s a mess, but those who have this plugin can try to deactivate it.
First, better deactivate Nextgen, empty the cache via W3TC, then turn off also the latter and log out. Log-in and activate Nextgen, check, empty cache, then activate W3TC.
Hope that works for you too.

I followed tizz’s method, and after reactivating Nextgen, but before reactivating W3TC, it didn’t validate again. Then, I reactivated the cache, deactivated Yoast SEO, emptied cache, reactivated Yoast SEO, emptied cache again, now the feed is validating. Don’t know for how long, though, if it’s a cache issue.

Anyway, tizz’s method can probably be simplified. You could probably:

Deactivate Nextgen and Yoast SEO, empty the W3TC cache, then turn off W3TC and log out. Log-in and activate Nextgen and Yoast, check feed, then activate W3TC.

There may be some unnecessary steps in there still, but basically, that’s what I did, and it’s working ok for now.

Don’t know for how long, though, if it’s a cache issue

Indeed, it comes and goes, and now feeds aren’t working again. I don’t know if it’s a conflict with W3TC, but it seems a cache issue.

it is not w3tc and has nothing to do with it also not Yoast it is Nextgen the error comes from Nextgen

<sourcetext> b[c] += ( window.postMessage && request ? ‘ ‘ : ‘ no-‘ ) + cs; ——————————————————^</sourcetext>

It is not the first time that these 2 plugins has errors, 1 year ago the same problem with Yoast and Nextgen. But this issue must be fixed, I use All in One Seo pack now and I don’t have any issues with nextgen at all

Right, the cache fix didn’t help for long. Next, I tried Ivan Novak’s hack above. Seems to be working.