Conflicting with Yoast SEO

Hi @omusman,
did you cloned the site with this plugin present? If so, you did this wrong. Anytime you are cloning the site make sure that either you first remove it from the main site and then clone it or you delete this plugin after cloning it. Then when you bring the site back from the stage environemnt to live, resetup the plugin.

This is because your staging might be on a different domain or subdomain where Cloudflare won’t work. If you have setup the plugin for https://example.com then it needs to be used there. You cannot use it in dev.exmple.com or something like that. If you wish to use it there then you have to delete the plugin and do a fresh install with the CF account details of the staging domain. So, the plugin will create the necessary rules needed for that domain.

Hi @isaumya

Thank you for the reply, i did as you suggested and just to mention, the cloning was a test, i also tested this on live site, and i am facing the issue on live environment too.

Huh! I have not faced this issue on any sites. Just to test in the stage environment can you please keep this and yoast plugin enable and disable the rest of the plugin and then check?

Sure, i disabled all the plugin, just Super Cache and Yoast is enable, still error exists.

Can you check the browser console, from where the error is coming from? Also inside the plugin settings under the cache tab, make sure that the WP JSON endpoints responses are not cached.

Hey there,

I checked the WP JSON Endpoint option but it still is giving error upon saving the changes. The dev console has given this error:

Error while saving: WordPress options save did not get to the end.

Hi @omusman,
I understand your concern but it is kind of impossible to debug without having access to your website and checking what’s going on.

BTW, can you check:

1. This option is checked inside the plugin settings (https://i.imgur.com/RHX88jF.jpeg)
2. If you have enable Web Application Firewall (WAF) inside the Cloudflare dashboard, try disabling that
3. Try using the cache rule based option (Implementation Guide: https://gist.github.com/isaumya/af10e4855ac83156cc210b7148135fa2)

Please try using these options and let me know if they work. Implement/try these option serially as mentioned above.

Hey Saumya,

Thanks for the reply,, i have checked the settings you showed in the image, also checked for WAF firewalls on Cloudflare, but none are used, and also follow the Cached Rules you shared in the Github link and disabled the Cache Buster Query Parameter. One thing i would like to share which i notice is when i saved the settings on yoast, the url which is been hit is this:

wp-admin/admin.php?page=wpseo_page_settings_saved&settings-updated=true&nocache=1

I have disabled the Query parameter still the nocache=1(i changed it with ?swcfpc=1) is appearing in the URL.

Thanks.

Hi @omusman,
That is not supposed to happen. Can you please check in an incognito window? And also remove the custom code you added to change the cache buster query param as it is no longer needed considering you are not using cache busters anymore. Thanks

No, i tried in incognito and removed the line which changes the query from wp-config.php, now url is changed to:

/wp-admin/admin.php?page=wpseo_page_settings_saved&settings-updated=true&swcfpc=1

• This reply was modified 1 year, 8 months ago by omusman.

But are you still facing the same problem? I don’t know why the query string is there (it is not supposed to be if you have cleared all the cache).

But even if it is there, it is not doing anything as you have turned off that feature.

Yes, issue still exists, the reason why i am pointing this out, because as i disable the cache, hence it removed the query string from the url and when i try saving the changes then, it works so it might be something this is causing issue.

Hi @omusman,
Have you enabled the option inside the plugin settings > other tab > remove cache buster query string? Have you enabled this settings?

Can you please share the page source code of the admin where this is happening via pastebin?

Yes, i have enabled the Remove cache buster query string option.

Pastebin seems to be not storing full source code, here is the wetransfer link of the page https://example.com/wp-admin/admin.php?page=wpseo_page_settings#/crawl-optimization

https://we.tl/t-LmSkrdlZ9r

Thanks.

Hi @omusman,
Thanks for sharing the page source. I honestly have no idea why it is being added. As generally that query param is added by JS which injects that query params to URLs. But as you have enabled the “Remove cache buster query param” option the JS is not being loaded as it should. But still, I don’t know why yoast URLs have that query param. I have also looked at the plugin code and saw no place that might be causing this.