Hello @dccorp,
I’m sorry you’re experiencing issues with the new version. To help troubleshoot this cache clearing error, could you please provide a few more details:
Does this error show up on the frontend, the dashboard, or both? Could you share which script throws this error?
If this is coming from backend.min.js from Super Page Cache when logged in and purging cache from the admin toolbar, it might be because a cached version of the script might be loaded when logged in.
If you have multiple caching plugins, can you please make sure that you purge the cache for all of them, and also ensure that you clear the browser cache (or try purging cache in an incognito window)? This should help determine if it’s a cache conflict issue.
Let me know if any of the above helps. Thank you!
Thread Starter
dccorp
(@dccorp)
Hi, thank you for the answer.
Only in dashboard, only when try to empty cache from toolbar, as it shows in this screenshot:
https://pasteboard.co/OcxsjUzu2gCr.png
I think I’ve purged Linkspeed with “purge all” command in the toolbar also, and I don’t have another cache plugin (or at least I don’t think so).
Thank you,
Hey @dccorp,
Thank you for the response!
Unfortunately, I couldn’t replicate the issue on my end.
Looking through the code, we are not using any call that directly calls innerText straight onto a document.getElementById call, so this leads me to believe that the error might not be coming from Super Page Cache.
This leads me to believe that there might be another event listener from a different plugin that gets attached to the admin bar button. If the cache purging doesn’t work, and the listener is indeed from another plugin, it might be preventing the functionality Super Page Cache attempts to run.
- Does the cache purge properly when the error is thrown?
- Does the error only display in the browser console, or it’s also visible on the frontend?
- Does purging the cache from the plugin dashboard works ok?
Thank you!
Thread Starter
dccorp
(@dccorp)
Hi Andrei, thanks for your answer (multumesc 🙂
Answers:
- It seems that the cache is working
- The error is thrown only when the clear cache command is sent from the toolbar (as in the screenshot sent in the previous post). Toolbar is present as long as I’m logged in as administrator, so yes, the error is displayed also on the frontend, if the command is sent from toolbar
- It seems that the purge is ok, but I need more tests.
I’ll check tonight each plugin for possible conflict and I’ll be back with the results.
For the moment I’ve locked the plugin to the 5.0.12 version, as it is working as expected.
Thread Starter
dccorp
(@dccorp)
Hi, I’ve found something!
- With firefox and noscript addon (my daily browser config), I receive that error mentioned above. Noscript was blocking a call to app.formbricks.com, which is new in super page cache. I was not able to access super page cache plugin’s settings also.
- After allowing the call in noscript, I was able to access settings but that error is still there.
- In chrome, without strict measures against scripts, the error is not thrown anymore and everything is working.
Thank you, maybe you’ll be able to debug further with this info.
Hello @dccorp,
Hey, thanks a lot for the detailed follow-up! It was really helpful to pinpoint the issue. From what you shared, it looks like your setup (Firefox with NoScript and tight script restrictions) is quite specific. While we totally get the need for that kind of configuration, it’s unfortunately a bit outside what we can realistically support across the board.
That said, I’m glad things are working in Chrome and that you found a workaround.
Let us know if anything else comes up within the usual use cases.
Have a great day!
