-
Notifications
You must be signed in to change notification settings - Fork 29
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
Unable to read file from location #195
Comments
Yeah, it's same issue. Update to latest version and that error will be silenced for production. 🤷♂️ This is same behavior as glide:data_uri tag, the core just silences any errors coming when reading from image manipulation directory cache. https://github.com/statamic/cms/blob/3.3/src/Tags/Glide.php#L212-L227 If you want you can update the issue on core saying it can happen with Sorry for the trouble! |
Ah I see. I opened this because I thought it was addressed in v2.14.2, and I was running v2.14.4. Looks like 2.14.5 handled it. I will update. Thank you! I will update my core issue. |
v2.14.2 only fixed issue if you changed the There is a bigger underlying issue that just needs to be fixed in the core. The "fix" I reapplied in 2.14.5 is simply hiding it under the rug. It has to be resolved in core. (I started writing this reply to your first unedited message FYI 😅 ) |
Bug description
Just had a random crash as a client was editing content.
I FTPd to the server to check the cache folders at storage/statamic/glide/containers/etc and the file was missing. I guess there was a reference to this file somewhere in storage/framework/cache/glide but for some reason the file did not exist.
My image manipulation cache is set to false and the website has been running fine for a month. Seems totally random.
It seems similar to this issue: #171.
I opened a core issue here: statamic/cms#7350
How to reproduce
No idea.
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
regex (default)
Additional details
No response
The text was updated successfully, but these errors were encountered: