Closed over-engineer closed 7 months ago
Could not reproduce in a vanilla WordPress installation with the following plugins installed:
1.2.2
(this plugin)5.7.0.1
Purging all caches does not seem to be causing any issues with the Pressidium Cookie Consent plugin.
@formaciongrafica I tried to replicate the issue on my end, but, unfortunately, I couldnāt reproduce it š
Hereās a few things you could check:
Update plugins to their latest versions to address any known issues
If possible, temporarily deactivate all WordPress plugins except Pressidium Cookie Consent and LiteSpeed Cache to see if the issue persists. Re-enable them one by one to identify any conflicting plugins
Inspect the console, are there any errors? (on Google Chrome, CTRL
+ Shift
+ J
on Windows, or CMD
+ Option
+ J
on macOS)
Check the error logs on your server
Hello Konstantinos In reality I have been able to replicate the error in 3 different installations, and in all of them the same error is generated. I have disabled both plugins and the problem persists. The only factors in common are:
I hope I have provided some more clues. Thanks again! Placido.
@formaciongrafica Could you please also check your server logs for any errors?
Hello Konstantinos Sorry I couldn't answer you before.
I attach the screenshot of my Chrome error console, as well as the November and December logs of my hosting service with all the logs related to Pressidium and LiteSpeed. Regarding the .php.error.log there was no record related to either plugin.
I tried to reproduce the error with the new version of Pressidium installed and I couldn't replicate it again, so I assume it was some conflict with a previous plugin that I updated, or some change in the new version of Pressidium :)
Regarding the configuration of the Pressidium, I reconfigure it and send you the record, at the latest, during this afternoon or evening.
Thank you very much, again, for your constant assistance. Placido.
Hey, @formaciongrafica!
I tried to reproduce the error with the new version of Pressidium installed and I couldn't replicate it again, so I assume it was some conflict with a previous plugin that I updated, or some change in the new version of Pressidium :)
Thatās great! Iām glad it was resolved.
Iām closing this issue. If you have any more questions, feel free to ask š
Initially reported by @formaciongrafica in #43.
There might be some sort of conflict with the LightSpeed Cache plugin.