wronski

Perfect. I was hoping that was the answer ?? Thank you!

1. Using Version 16.7
2. Using Version 5.7.2
3. Yes, still occurs
4. Yes, when tested with Firefox, still occurs
5. I have tested in Firefox with no browser plugins or extensions, and the issue persists

Please note, I use W3 Total Cache, and recently did a migration of my WordPress to a new instance. I am wondering if either a certain file that Yoast needs is either blocked or corrupted.

When I click on Start Optimisation, it takes me to: https://{my_ip_address}/wp-admin/admin.php?page=wpseo_tools&start-indexation=true rather than my domain.

Thank you for your help Marko. I managed to resolve the issue.

Given the site was degraded for a long period of time, we had to restore from a backup. We have shutdown W3 Total Cache services one at a time to ensure nothing dramatic happens, and this seems to be working.

Thank you, @sterndata. I was following instructions from the wordpress error message screen to contact wordpress support, but I did manage to solve my issue via phpmyadmin troubleshooting pages.

Solution was to restore wp_options table from a few days ago.

Perfect. That worked, Marko!

Sorry for the slow response. I had to set a time early morning to test all this.
Each of these things were set before, and still are, but I rechecked them, and the errors persist. I cleared the caches, and restarted my server. Cleared browser caches.

I have left the CDN on so you can observe the errors yourself. Go to https://www.questcoffee.com.au/ and check the console.

Thank you for your help in advance.

Hi @vmarko, thank you for the reply.

I turned off ‘W3 Total Cache’ CDN because it was causing this issue. I won’t be turning it on until I have a fix to try. The errors are the errors I have shared, and am wondering if you can provide me steps to complete https://aws.amazon.com/premiumsupport/knowledge-center/no-access-control-allow-origin-error/ to setup CORS for origin requests. Specficially: “Note: Be sure to also forward the header as part of your client request to CloudFront, which CloudFront forwards to the origin.”

I found the issue. There was a conflic with ‘W3 Total Cache’ Plugin. I deactivated W3 Total Cache, then was able to delete WP Optimise.

Hi James.

Please don’t write a passive aggressive response to a question I was asking you. You didn’t “ask” a question in your response to my request. You provided a recommendation. I wanted to make it clear that I am not looking to edit my review, and I also am of the belief software companies don’t have a right to stop their users from deleting content.

My question to you (which I now feel may have upset you) was honest because I was curious where your recommendation was coming from.

I don’t want to leave a review for this plugin. This is my content and I should have a right to remove what I don’t want public anymore.

Did you write “Instead of removing it, I recommend updating the rating and text to fit the current situation.” because you can’t remove it yourself, it’s too hard, or you don’t want to?