brandon.w

Just went through another round of testing, because I couldn’t sleep. I created a new notification that sends an e-mail when a page is updated. I, incidentally, updated my HTML sitemap page a couple times, and BNFW sent me the notification e-mails as expected.

So – it appears the issue (at least,, in my case) is solely with the “New Comment / Awaiting Moderation” notifications.

SO MUCH WIN for getting to this. Thank you!

That looks like a different issue. Do you have a cache (many plugins utilize a cache for you)? If so, you may try clearing it to see if that resolves your particular problem (you should get in the habit of doing this after every plugin update, anyway).

YAY – as of 3.1.2 – this issue has been corrected. No more console errors!

Here’s an idea: if Custom Permalinks is the problem in the majority of cases here, perhaps Yoast should consider adding a permalink editor of their own to the plugin’s list of capabilities. This way, users would no longer be dependent on out-of-date plugins that frequently have problems with Yoast. After all, managing permalinks IS (at least in part), a function of SEO. I’m surprised this isn’t something they’ve done already.

jcastillo1 – They have already closed that issue on GitHub. I’d also imagine that a vast majority of WordPress users do not have accounts on GitHub (which are required in order to post there), hence why no one is posting there. We are using a WordPress plugin, and as such, we expect to use the WordPress support threads… for… well… support.

This issue has been going on long enough that it may be time to start talking about alternative SEO plugins that can handle the same tasks Yoast does. Any suggestions?

And this is a problem with the Yoast code, then. ??

I use Firefox Developer Tools, though I’m not sure exactly how to tell if any files did not load.

If I click on the Network tab and refresh the page, all files are loaded with either a status of 200 (OK) or 304 (not Modified).

If only it were that simple. I tried that – because based on my last code example, that SHOULD have worked. So, I uploaded duplicates of the wp-seo-post-scraper-311.js and wp-seo-post-scraper-311.min.js files, but renamed the duplicates to 310, as you suggested.

That did not work for me. Here is the JS console now:

When clicking into the description meta editor:

TypeError: document.getElementById(...) is null		wp-seo-post-scraper-311.min.js:1:2975
	h.prototype.setDataFromSnippet()		wp-seo-post-scraper-311.min.js:1
	h.prototype.saveSnippetData()			wp-seo-post-scraper-311.min.js:1
	[28]</E.prototype.updateDataFromDOM()		yoast-seo-310.min.js:2
	[28]</E.prototype.changedInput<()		yoast-seo-310.min.js:2
	i()						yoast-seo-310.min.js:6
	j()						yoast-seo-310.min.js:6

This would be just a work around, much like using the bulk edit tool within Yoast (which I find easier, for now). Still hoping for a fix from the devs.

Surfbrain said:

Just add this line of code define( ‘CONCATENATE_SCRIPTS’, false ); in your wp-config.php and problem is fixed. ??

I haven’t tested this, but if this worked for you, then by it’s very nature, there is a problem with one or more of the JS files that are loading. The question is whether the problem lies in the Yoast JS files or the other plugin JS files. Basically, that line of code tells Wp to load all scripts, individually (rather than collectively), even if one or more of them fails to load properly.

Reference: https://stackoverflow.com/questions/32588692/how-does-concatenate-scripts-work-on-wp-config#answer-32589922

Thank you 5ivefold! I’d never used that tool before and it was a life saver to get all my recently created pages updated with their meta descriptions.

I accidentally realized that this *is* a plugin a compatibility issue. While working on another web with Yoast installed, I was able to add/edit the meta description of page and it saved after updating the page.

Went back to the problem site and found the culprit to be the Custom Permalinks plugin. Unfortunately, that plugin provides a necessary function for this web, but doesn’t appear to be kept up by it’s author.

Hoping that the next update to Yoast will resolve many of these compatibility issues. It appears that most people are finding one plugin or another is causing this issue.

PS – Still getting the same errors in the JS console as I had posted here 5 days ago.

Even after the last update (3.1.1) I am still unable to save meta descriptions. Is there a step I’m missing? I paste in the text I want, then click to update the page, but it just doesn’t work.

I don’t believe this is a plugin compatibility issue. I can see the description meta box, and I can add to it, but adding to it doesn’t automatically affect the “length indicator” just below the box. And updating the page/post after adding a meta description doesn’t save the new description. For the life of me, I can’t get it to stick. I’ve had to temporarily make a note that I cannot edit or add new meta descriptions until this is resolved. I can only hope (since there has been no official word) that the team is hard at work providing a fix.