-
-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Error] Undefined array key "en" in FileCacher:155 when invalidating static cache of 2nd site with path /en #7411
Comments
Please show the |
Hey Jason! Thanks for the very quick response! Pretty sure I didn't touch the strategies block... ?
|
maybe related? #7403 |
I just noticed this error in the logs:
|
Same issue here. I am trying to get Cache Invalidation in a multisite environment. Sometimes it's working, sometimes it's not... This error is also coming up occasionally. |
Experiencing the exact same error. I am using the DB queue driver. Not sure, but maybe it is related to that as well. |
Yeah, it really seems to have to do with the URL locale suffix/prefix. |
Can you try to composer patch #7509 to see if it solves your issue? |
That PR works for me. No more errors! |
I currently have issues patching this in on Mac OS Ventura (related: cweagans/composer-patches#423, though unable to solve) which prevents me from locally testing this... @jasonvarga any chance that this might make it into the core? :) |
@mnlmaier worst case if you really wanna try it: it's just two lines of code that have changed. You can update these lines inside the vendor folder. |
1 similar comment
@mnlmaier worst case if you really wanna try it: it's just two lines of code that have changed. You can update these lines inside the vendor folder. |
@AndreasSchantl sure, I almost would have done that, but it doesn't feel right editing vendor files on the client's production system were multiple people have the ability to deploy and potentially revert the change without me knowing – composer patching would at least make sure that additional deployments won't break things again :/ |
Of course – never do that in production! I was just talking about doing it locally to confirm that it works for you as well. I am sure it will be merged soon though! |
Hi guys, any updates on this? It's sadly blocking core functionality for us... |
@mnlmaier I temporarily "fixed" it with an event listener, whenever an entry gets saved, I reset the static cache. Not efficient at all, but it at least does the trick for now. 👍 |
@jlmmns I might have to make use of Event Listeners, too. Still feels not right having to do that if a fix seems to be available... :/ |
If you can confirm the PR fixes it for you, @mnlmaier we can get it into core. |
Bug description
I have a Multi-Site configuration running with Full Static Caching.
But the invalidation rules don't seem to work for my 2nd site.
Only the 1st site gets invalidated when saving an entry.
It might have to do with the path
/en
of the 2nd site. (#7403)Error in the logs:
How to reproduce
/config/statamic/sites.php
/config/statamic/static_caching.php
Logs
No response
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
runtime (new)
Additional details
No response
The text was updated successfully, but these errors were encountered: