Plugin Support
kamenk
(@kamenk)
Hello James,
Thank you for your kind words and for taking the time to provide detailed feedback regarding our plugin! We’re glad to hear that you enjoy using it alongside your SiteGround hosting.
Regarding your concerns:
- Caching in wp-admin: Our plugin is designed not to cache any content under the wp-admin/ path, as backend pages are dynamic and continuously updated. More information about how our dynamic caching works and exclusions can be found here:
https://eu.siteground.com/kb/siteground-dynamic-caching-configuration
2. Combine JS files setting: The “Combine JS files” feature can sometimes interfere with certain plugin functionalities. In such cases, you can exclude specific JavaScript files from being combined to prevent conflicts. You can find detailed instructions here:
https://eu.siteground.com/tutorials/wordpress/speed-optimizer/frontend-optimization/#combine-css-and-js-files
To ensure we provide the most accurate guidance, we kindly ask that you open a new support ticket via your Client Area. This will allow our team to review your current setup in detail and determine whether the issue originates from our plugin or another source.
Best Regards,
SiteGround Support Team
Hey! You sure? The always exclude list on the page you sent is:
wp-login, preview=true, cart, my-account, checkout, addons, add-to-cart, wp-cron.php, xmlrpc.php, contact, task=registration, register, view=registration|administrator|remind|login, admin/content/backup_migrate/export, status.php, update.php, install.php, user, info, flag, ajax, aha
none of those are everything under wp-admin….? also unsure how site-editor is included if wp-admin isn’t. which would explain the issue with blocks not appearing in site editor.
Don’t have time to open more tickets — just letting everyone know here to try this if they are having issues. Changing this one thing fixed my problems. I am constantly purging the cache on this site and this one change fixed this issue immediately
Plugin Support
kamenk
(@kamenk)
James,
To clarify, our plugin does not cache content in wp-admin/ for logged-in users. This is achieved by monitoring specific cookies, as mentioned in the article I shared earlier. For example:
wordpress_logged_in_
wpSGCacheBypass=1
Whenever you are logged into the WordPress Dashboard, the wordpress_logged_in_ cookie is set. This cookie signals to our plugin to bypass caching for wp-admin/, ensuring dynamic backend content like WooCommerce blocks and the Site Editor works correctly.
We understand that in some cases, additional exclusions (like the relative path you applied) may be needed depending on specific plugin setups or custom workflows. We’re glad to hear that this resolved the issue for you.
If at any point you require further assistance in reviewing or debugging caching behavior, our team is always available via the Help Desk to provide a more in-depth review of your setup.
Best regards,
SiteGround Support Team
Thanks for the useful clue! If that’s the case then I have a feeling the logged-in method is the issue. Since obviously I was logged into the site when I worked in the Site Editor and encountered this problem before adding the relative path to the exclude list manually.
Some browsers (like Brave, a Chromium privacy focused browser) and extensions will block cookies, but I checked and I was allowing cookies for this site since it’s one I’ve built and trust (haha). It could perhaps be an issue of Brave thinking that you/Siteground are a third party and not a cookie added by the site itself (which would be trusted. Since Siteground must send a cookie separately this would explain it! https://brave.com/shields
Something to consider in the future when evaluating the best way to handle exclusions. Cookies may not be the best way since more and more people are not allowing them these days, use blockers, or live in places that are getting stricter about cookies…
I will keep it in mind on the next site build and test both ways and get back to you! 🙂
-
This reply was modified 1 month, 3 weeks ago by
James Monroe.
-
This reply was modified 1 month, 3 weeks ago by James Monroe.
Plugin Support
kamenk
(@kamenk)
Thank you for the detailed explanation and for taking the time to share your findings.
We’ve passed your feedback and observations to our plugin development team for further review. They will evaluate whether excluding the wp-admin area through an alternative mechanism would be more appropriate in scenarios where cookies are blocked or restricted.
Should you need any further assistance or have additional insights to share, please don’t hesitate to reach out.
Best regards,
SiteGround Support Team
Plugin Support
kamenk
(@kamenk)
Hi James,
We weren’t able to reproduce the behavior on our end, so to continue the investigation, could you please help us with the following:
- Provide temporary access to an environment where the issue can be observed.
To do so, please open a new support ticket through your Client Area so we can investigate this further.
- Confirm whether the “Logged-in users cache” option is enabled under File-Based Caching in SiteGround Speed Optimizer at the time the issue occurs.
You can check this setting here:
WordPress Dashboard → Speed Optimizer → Caching → File-Based Caching → Configure → Logged-in users cache
If you would like the case to be reviewed further by our developers, please submit a support ticket through our Help Desk, or ensure that the Logged-in users cache option is disabled.
Best regards,
SiteGround Support Team
