Does it work correctly with WordPress 3.7 ?

Stay calm *Joost de Valk* is on actions.

I am also having this same issue. I believe Russell Jamieson has found the problem, just need Yoast to make the change.

This is an issue for me too…

…Having the same issue…

same error here as well on all updates after upgrading WordPress ??

me too.

I get the same error (noticed it when updating an unrelated plugin, as others have mentioned here).

Also, @powerblogservice, you said it doesn’t do anything, but why has my XML Sitemap (with Yoast) tanked with a 404 error after upgrading to 3.7?

From what I understand by reading https://www.ads-software.com/support/topic/read-this-before-you-post/ — this plug-in author wants you to register on another website to report problems, rather than discussing them here. So, unless we all follow the instructions in the above link and navigate through a difficult to use developer website, we may never hear from the author concerning this.

I have reported this as a “bug” (or an “issue) on their Github. For those of you that want to share your sentiments, in hopes that this issue is fixed, please feel free to do so at: https://github.com/Yoast/wordpress-seo/issues/337

I just ran through the hoops and told SEO about it on its forum
So join me at:
https://github.com/Yoast/wordpress-seo/issues/338

@chris M. That’s probably unrelated, it still works on my site (https://rushtips.com/sitemap_index.xml).

The 404 error has happened to me a few times. You can try to re-install it.

Will be fixed in the next version. See issue at github.

It doesn’t affect the performance of the plugin. The function is only called when you update plugins/themes/core and it checks whether you updated the current theme and if so, re-checks whether the theme has a <meta description> tag. Nothing major. (via jnfnl)

Everyone, FYI:

a) This is not a serious issue. It doesn’t affect the performance of the plugin nor of WordPress itself. It will not stop any updates from happening either.
As @laserjobs also said: The relevant function is only called when you update plugins/themes/core and it checks whether you updated the current theme and if so, re-checks whether the theme has a <meta description> tag.
So nothing really major.

b) As @russell Jamieson also said: The issue is caused by a change in WP core in 3.7. They introduced an action hook in 3.6 which WP SEO was using and have changed the way the action is called in 3.7.

c) The issue was first reported by @vickyindo as a bug straight after the 3.7 release. Within hours, I made a patch available.
The pull request is waiting for Yoast to review it, but I very much expect it to be included in the next version.
If you don’t want to wait until then, just apply the changes outlined in this commit.

Oh.. and please do not open any more duplicate bug reports on this issue on GitHub. Duplicates are lazy, not useful and will only be closed.
Anyway, the issue is solved, a patch is available. You can either apply it yourself or wait for the next version of WP SEO to be released.

And @chris M.: that is completely unrelated to this issue – this error has nothing to do with the sitemaps. Please open a separate thread for this and/or if you have more detailed information, file a bug report on GitHub.

*grin* I see @crashnet has stolen my thunder while I was still composing my reply ??