Omar Reiss

@rubyslipper. That’s not possible anymore. But a better way to do that is to simply put those pages to noindex in the advanced tab of the Yoast metabox. That way it will automatically get excluded from the sitemap as well.

Read more about how to do that in this article: https://kb.yoast.com/kb/how-do-i-noindex-urls/#single

@amedic, the last update simplifies the settings, so there is no need anymore for an advanced toggle. All the settings are now available by default.

@lauratraveler We’ve moved the breadcrumbs settings to a new settings screen called “Search appearance”. Because of an issue in the 7.0 release, your breadcrumbs might have accidentally deactivated. You can turn them on again under Search appearance > breadcrumbs.

For more context, please read our release post. https://yoast.com/yoast-seo-7-0/

Hope this helps resolve any issue you might have!

So… This doesn’t really seem like an exploitable vulnerability. Please send us an email on [email protected] showing the vulnerability and how it can be exploited and of course then we will fix it.

May I point out to you that disclosing an XSS issue on a public forum is bluntly rude and puts your fellow users at risk. Like most big plugin builders, Yoast has a security@ mail address for responsible disclosure. And even security emails to our support mail make it through 99% of the time.

We’ve just released a patch (2.3.2) that fixes the profile update issue.

We’ve just released a patch (2.3.2) that fixes this issue.

@all we’ve released a patch (2.3.2) today which fixes this issue.

@msteel please create a separate issue for this (preferrably a bug report on GitHub), since it’s definitely not related to this topic.

The patch (2.3.1) for the wp_query fatal has been released. We’ve received positive feedback on it from multiple users. Marking this topic as resolved.

Thanks @all for your input and cooporation.

We have received positive feedback from a couple of users. The patch (2.3.1) has been released. Marking this topic as resolved

@msteel Sounds like a whole different issue. Do you use the WordPress installer for installing and updating plugins or do you use another method?

Bottomline was us using WP_Query too early and other plugins depending on certain hooks in WP_Query which were not available yet.

Ok then, we are going to release the patch. Thanks @all for your input and cooporation.

@gaswirth Thank you for testing!

@everyone we’d appreciate more feedback!

@everyone we’ve done a change that will hopefully solve your problem.

Would you be so kind to test the beta we’ve created for you?

You can download it here: https://uploads.yoast.nl/wordpress-seo-2.3.1-beta.zip

@everyone we’ve done a change that will hopefully solve your problem.

Would you be so kind to test the beta we’ve created for you?

You can download it here: https://uploads.yoast.nl/wordpress-seo-2.3.1-beta.zip

Thanks @keanpoh, we’ve been getting similar reports. Apparently in many cases, the issue is resolved after deactivating and reactivating the plugin. I’ve gotta say that doesn’t make it easier for us to find what’s causing this. But it might help users get to the 2.3 version of Yoast SEO already, which includes lots of nice improvements and cool new features.