OneHundred

@citphoto , yes, just overwrite the wordpres-seo folder and you’re good to go.

@citphoto I had a local backup of the plugin, so just replaced it.

Otherwise, you could look at the git for the plugin, and grab it from there: https://github.com/Yoast/wordpress-seo

Same. Our site goes to a 502 as soon as we upgrade today.

Renaming/disabling the plugin (from FTP) fixes the issue.

I’ve now rolled back to previous version with no problems. Will await new release.

I’m on IIS. Latest PHP.

• This reply was modified 6 years, 4 months ago by OneHundred.

Thank you. I’ve had a reply via email too, and you/they are going to look at my website.

I’m still getting this issue. I’m having to manually delete the files through FTP each time I update a page.

Thank you Tim, all working well again.

I have also posted this in another thread:

I’m experiencing the exact same error code today (since the update). But it’s not every domain for me.

I have 30+ domains across 5 different hosting packages (international hosting). Only the domains on my Windows based hosting are experiencing this issue. My other 4 hosting accounts (Linux) are fine.

All installations are on WordPress 4.2.2, and Wordfence 6.0.2. Some of the sites have the exact same themes/plugins too. Renaming the Wordfence plugin folder removes the error and allows access to the site/admin area.

I’m experiencing the exact same error code today (since the update). But it’s not every domain for me.

I have 30+ domains across 5 different hosting packages (international hosting). Only the domains on my Windows based hosting are experiencing this issue. My other 4 hosting accounts (Linux) are fine.

All installations are on WordPress 4.2.2, and Wordfence 6.0.2. Some of the sites have the exact same themes/plugins too. Renaming the Wordfence plugin folder removes the error and allows access to the site/admin area.