Plugin Contributor
iSaumya
(@isaumya)
Hi @jujiz,
This plugin automatically BYPASS cache for wp admin pages and for any user who is logged in. You can check chrome developer console > network tab to check the headers and you will see cache is bypassed.
Are you using some sort of page builder? If so then which one? Also if possible do a screen record to show the issue in detail and share that with us. If you are inside wp-admin there is no way things are cached. Your cf-cache-status is BYPASS.
Thread Starter
jujiz
(@jujiz)
heres a screen record https://drive.google.com/file/d/1M9nlClGl9v1qL-CgxqUbPw2vv3CN84_A/view?usp=sharing
i think i can get more details from the console in some screens. Please check if its enougt to debug. thanks
Plugin Contributor
iSaumya
(@isaumya)
Hi @jujiz,
First of all as you have showed in your video, the fallback cache is turned off and you have also modified the Cloudflare page rules to bypass everything so basically Cloudflare is also not caching anything and neither does the plugin.
The 403 forbidden error is a server-side thing means the server is not allowing the script to access the path it s trying to access. I really don’t think it is coming from our plugin as you have disabled both fallback caches and modified the Cloudflare page rules to bypass everything.
Let’s wait for @salvatorefresta to come online in case he have some idea about what’s causing this. Though personally I do not use any page builders whatsoever but looking at your video and the configurations you have dowed me, I really don’t see how this plugin can cause this issue as it is essentially not doing anything.
Thread Starter
jujiz
(@jujiz)
just a footnote. That area where that window appears is a section with the preview of the actual website.
I am not developer so i dont know exactly what to do here.
Thread Starter
jujiz
(@jujiz)
@salvatorefresta any solution?
Thank you
Hi @jujiz ,
the page rule I seen in your video is not the one created from the plugin, so please click on “reset all”, delete the page rule and re-install the plugin again.
As @isaumya already said, the cache is 100% bypassed while logged in. If this not happens (rare cases) is due to conflicts but it is not possible for us be sure of this. You shoud give us access to a staging area in order to check if all is working properly.
Can you?
Thread Starter
jujiz
(@jujiz)
Hello @salvatorefresta what do you mean by “access to a staging area” where how?
Should I folow you said – “please click on “reset all”, delete the page rule and re-install the plugin again” Or should I jus give you access to the “staging area” ?
thanks
Plugin Contributor
iSaumya
(@isaumya)
Hi @jujiz,
As @salvatorefresta said, you can first try the Resent All and resetting up the plugin and if that doesn’t solve the issue, send the stagging area details to the email id mentioned in the plugin settings page (right side sidebar).
Hi @jujiz ,
access to staging area = access to a “test environment” of your current WordPress installation.
I cannot ask you access to live site due to ww.wp.xz.cn support guidelines.
Thread Starter
jujiz
(@jujiz)
Hello @salvatorefresta
I realise that its not a plugin issue (i guess) i have deactivate all plugins and there is (still) a 403 error.
I am contacting my host now
Thread Starter
jujiz
(@jujiz)
AHHH ok……. I was writing you a email with 10 or 20 lines of text 😅 and the host just replied!
The module Mod_Security was deactivated from the host and that solve the error message.
Thank you!
Plugin Contributor
iSaumya
(@isaumya)
Hi @jujiz,
Glad to know that the issue is resolved. Making this thread as resolved now.
