benvaassen

The patch for Yoast SEO free 19.5.1 has been released and the download problem with it should be resolved by now. Once again we’re sorry for the problems caused and thanks again for reaching out so quickly and letting us know!

Yoast SEO Premium 19.1 has just been released. It should show up when you navigate to Dashboard -> Updates in your backend but you can also find the updated version in MyYoast.

We’re still working on the patch for free. I’ll inform everyone here when we release the patch.

• This reply was modified 2 years, 3 months ago by benvaassen. Reason: Added version number

We’re sorry that you’re experiencing a fatal error. Thanks for reporting. We’re investigating and it seems to be a problem with the latest update of Yoast SEO while the newest Premium wasn’t released yet. This shouldn’t have happened.

We’re looking at getting this resolved as soon as we can by releasing a patch for free and also by releasing Yoast SEO Premium asap. Either should fix the fatal error.

Hi @fjelltid. I’m sorry that our plugin is taking down your site. Can you first try to delete and reinstall Yoast SEO? And if you have any Yoast add-ons installed but inactive, can you delete them?

Hi @giuseppectmobi,

I just noticed that the line item mentioned in the stack trace is 2031. In 17.1 that’s changed to 2043 so my guess would be that clearing your OPcache would fix the issue (or reinstalling the plugin). Can you try that before diving into a conflict check?

Hi @bloggamefoxit,

We’re sorry to see you’re having this problem with the latest version. We reproduced the problem and can confirm that this no longer works out of the box with the latest version of the All in One SEO plugin. All in One SEO seems to have changed the internal way to store information, which breaks the compatibility. That’s probably why it can still duplicate the old titles or keywords but doesn’t duplicate the new ones.

We suggest contacting the All in One SEO support team to bring back full compatibility with our plugin!

The best place to know if it’s going to be a ‘yea’ or a ‘nay’ would be the GitHub issue itself. The issue currently doesn’t have a high priority because this change does not influence SEO directly. I’d like to invite you to contribute to the discussion on GitHub.

Because of the above, we cannot answer your question here and I’ll set this topic to “resolved”.

Hi Ben,

Thanks for sharing! That looks like we’re trying to create a table that already exists. Can you try recreating the tables with our Test Helper plugin? After installation / activation, go to Tools -> Test Helper and click the Reset indexables tables & migrations button.

If that still doesn’t work, can you share the debug information once more?

Hi Ben, I’m sorry to hear that our speed up process isn’t working for you. Can you share what the “Show debug information” button shows? That should give us some more information about why it’s not working for you.

Hi @volkansevim, so sorry about this, this shouldn’t happen. Thanks for letting us know. I can confirm this a problem on our side and it’s reported to our developers on GitHub, so we’ll get this fixed. Please be patient until then!

Hi @teszilla, so sorry about this, this shouldn’t happen. Thanks for letting us know. I can confirm this a problem on our side and it’s reported to our developers on GitHub, so we’ll get this fixed. Please be patient until then!

We’re glad to hear you both figured out what was wrong! I’ll mark this as resolved then.

Hi @vesco27 thanks for letting us know about Jetpack. It seems your site also has the Jetpack sitemap enabled here. The GET requests from your first post, are requesting the Jetpack sitemap and not Yoast’s sitemap (which is located at sitemap_index.xml when enabled).

I think there’s definitely some conflict going on here. I’m curious to know what happens if you disabled Jetpack’s sitemap and enabled ours but I’d only recommend that on a staging environment, not your live site. We’ll check into this.

You only need 1 sitemap, so you should either pick Yoast SEO’s sitemap and disable Jetpack’s or the other way around.

Thanks for letting us know Emily! If it’s not working after a few weeks, please let us know and open up a new topic. For now, I’m gonna mark this as resolved.

For everyone who is running WPML, we’re including a fix for the infinite indexation. We’d recommend downgrading to 13.5 and wait on our 14.1 release. It should be released in a couple of days, so please hang in there for a little while!

Hi @abidzai I’m sorry to hear about this. It sounds as if your site got hacked, as @endymion00 said (thanks for helping out!). Reaching out to a third-party for help, like Sucuri, is what we’d recommend. This post might also be helpful.

Good luck!