@cutrano We’re sorry to hear you are experiencing this issue on your site.
Can you please confirm you are using the most recent version of Yoast SEO, version 16.02? You can learn more about updating here: https://yoast.com/help/how-can-i-update-my-free-plugin/
Also, can you confirm you are using WordPress 5.7.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: https://yoast.com/why-we-dont-support-old-wordpress-versions/
Yes, everything is up-to -date. This is basic troubleshooting. Using version 16.2 with WordPress 5.7.1
There’s a problem with the plugin and it appears to be widespread. Hoping your team can patch it and we can all move along
Hi @cutrano
We are sorry to hear that the issue persists even after performing the conflict check. We received similar reports from other users and noticed that the only thing in common is that all websites are running the Imperva CDN.
Are you using this plugin? If so, does clearing the Imperva CDN cache resolve the issue?
If you continue to have problems, can you please provide a screenshot of the Javascript error you are getting on your console? This guide explains more.
Unfortunately I’m not one of those users. I did however clear my caching plugin and still not having any luck fixing this problem.
Classic editor is up to date.
Sorry to hear that issue persists @cutrano . Let’s dig further.
There were several reported issues that got fixed after their host whitelisted a rule in their mod_security setup that was causing problems. Is this something you can check with your web host?
What was the rule that was whitelisted? I can check it
@cutrano To check whether there is a mod_sec rule violation causing this you would need to review your site’s error log, and then search for any ModSecurity errors from your IP address. A mod_sec violation typically starts with something similar to:
[client IP.AD.DRE.SS] ModSecurity: Access denied with code 403
If there is a rule violation, the ID of the rule that is violated will be displayed within the error shown as an ID number, such as [id “123456”]
Then using the rule ID you can then whitelist the rule ID on the server. If you don’t have direct access to whitelisted mod_sec rules, you can request this to be done by your hosting provider.
Updated my PHP version from 7.2 to 7.4 and it fixed it
However not working in Firefox or Safari…only Chrome
-
This reply was modified 5 years ago by
cutrano.
Hi,
We understand that you’ve updated your PHP from 7.2 to 7.4 and that fixed it. We would expect that the Yoast SEO plugin would work with the latest version of PHP, in fact we recommend PHP 7.3 or greater — https://yoast.com/help/plugin-requirements/#php
We understand it’s working in Google Chrome, but not in Firefox or Safari. Were you able to check regarding the mod_security setup with your web host?
We might need to take a further look at your website, but we are unable to do so over these public forums. Our Yoast SEO Premium plugin comes with one year of (technical) support, so you might want to consider that.
There’s nothing wrong with Mod Security. Can we please move to the next step? Please advise. This has been broken for a while now. Im lucky the PHP upgrade at least got me to work in Chrome.
I have the free Yoast plugin. What types of support are available. I need to get this resolved
-
This reply was modified 5 years ago by cutrano.
I have the free Yoast plugin…not pro. What type of support is available for this
