Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Clearing caches on MSM site
| Status | Resolved |
| Add-on / Version | Speedy 1.5.2 |
| Severity | |
| EE Version | 5.4.3 and 6.3.5 |
Aasun Eble
Oct 12, 2022Speedy stores its caches in system/user/cache/speedy/
Then there are directories for “sites” and the caches are in there
/site_1/global/
/site_1/local/
/site_1/static/
/site_2/global/
/site_2/local/
/site_2/static/
The cache clearing rules are created in each MSM site’s admin.
BUT, for site_1 channels that are used by site_2, how do you control clearing those caches when editing those channels?
The instructions show starting with global/, local/, or static/
So, no way I can see to clear out specific site_2 global caches when editing the site_1 (shared) content.
BoldMinded (Brian)
Currently there isn’t a way to do that that I can think of. The way MSM works is it doesn’t know which content is being shared across which sites, so the cache breaking rules would have to be updated to specifically account for that, which would require a bit of a refactor.
Aasun Eble
What about being able to use something like the following in the cache clearing rule:
../site_2/global/[name_of_my_cache_file]
BoldMinded (Brian)
You can try it but that might not work if you’re using Redis, but it might if using File cache. I’ve never tried it.
Aasun Eble
Perfect! Just tested and it works.
For clarity, I’m using Filesystem caching only. This is an MSM site.
For some content on site_2, I’m using site_2 templates, but displaying site_1 content. And I’m using speedy to create global (and local) caches for various segments of long/looping content.
In the site 1 CP, where the main content lives, I set up my site_1 cache clearing rules according to the docs. But, that doesn’t clear the site_2 caches for that site_1 content.
using ../site_2/global/ it works.