brodydorland

Hey Martijn – Not sure what changed or who we have to thank, but the error magically disappeared a few days ago. We’re back to a working Yoast module!

Quick update… After some internal troubleshooting with my development team, we’ve narrowed it down to a Mac/Chrome issue. More specifically, newer versions of Chrome. You might have an issue with your javascript code. When digging into the console error, this code snippet seems to be the culprit.

at __unstableMarkListeningStores (data.min.js:2:22094)

__unstableMarkListeningStores: function(e, t) { o = new Set; try { return e.call(this) } finally { t.current = Array.from(o), o = null } }

Newer browsers are expecting it to look like?new Set();

Here’s a quick video showing the issue and console error. Hope that helps!

https://us06web.zoom.us/clips/share/lhLn_0Ukl_xEMTMcWeXe8zQdZMQb40UNRRfleO48d6AO6nm32v6CMekCa7tyoHOF13spjk6Hfeju6zo0pwF9b8QY.LRBOUX9t_Q8nlvbl

FWIW – We’ve used the Yoast plugin for many years on this site and we’ve never had an issue. And we have not had any noteworthy updates on the site recently outside of regular WP, theme, and plugin updates.

Thanks Maybellyne. I executed those steps. When I got to step #4, the initial rescan failed due to a JSON error. I didn’t get to copy the exact error message, unfortunately. I then tried the scan again and it completed successfully. But, the original error is still present on all pages/posts.

I’ve already tried all that. Per my previous post, I’ve switched themes (in troubleshooting mode) and upon activation of the Yoast plugin, “a site failure occured”. And I’ve cleared all caches multiple times, including Cloudflare. And note that this error is happening within the Yoast module on all pages and posts, not just a particular page or post.

Hi! I went through your prescribed “Health Check & Troubleshooting” process. In troubleshooting mode with the Twenty Twenty-Two theme, I activated the Yoast plugin and got the following notice:

“When enabling the plugin, wordpress-seo, a site failure occurred. Because of this the change was automatically reverted.”

What now?

Same issue on my site, although mine says “o is not a function”. My WP and Yoast are all updated with the latest versions.

Same issue. I just recently got the plugin set up, created a Twitter app, set up an external cron job (via easycron) and everything appeared to be working, but no posts on Twitter. I saw this support post, reverted back to the previous version (8.2.1) and boom, tweets are posting.

Checking back in on this issue. I’m still running into the issue when embedding a playlist/tracks into a post. I’m surprised others haven’t mentioned it. Am I the only one with an invalid/broken feed? Does no one else care?

@steaders – Does your suggestion above still apply? Can you update the instructions so I can test?

More detail here: https://www.ads-software.com/support/topic/rss-feed-validation-issue-1?replies=1

+1 overall – Just had to go with the old-fashioned method for now (GA’s UA code in my header file).

Note to anyone that needs cross domain tracking (same GA profile for multiple domains/subdomains), you’ll need to adjust your code snippet a bit implementing this manually.

P.S. – Hello Mr. Frangos.

Brody @ DivvyHQ.com

+1 – Need some guidance on how to set this up. Working from this article:

https://support.google.com/analytics/answer/1034342?hl=en

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.

FYI for anyone else who runs into this issue.

Here’s a temporary workaround to get your RSS feed functioning properly: Install WP Hide Post – https://www.ads-software.com/plugins/wp-hide-post/

This plugin provides you with a simple “visibility” widget/form on your WP post editor that includes the ability to hide an individual post from your RSS feed. Therefore, by hiding/removing the post that has the HTML5 player issue, your feed is back up and running.

Hope that helps.

I’m not finding an “index.php in the plugin directory”.

Note that I read that to mean look for an index file in here: /wp-content/plugins/html5-jquery-audio-player-pro/

I do have a file here /wp-content/plugins/index.php, but that file only has three lines of code.

I see that there is an index.php with a bunch of code here: /wp-content/plugins/html5-jquery-audio-player (the standard version)

But I deactivated that plugin when I bought the pro version.

Little help?

Thanks Maeve – That helped. My original playlist title did have spaces, which resulted in spaces before the underscores in the shortcode. Note that I only got it working when I completely removed all spaces in the playlist title.

Not a big deal though. Glad to get it working!