Open stuartcusackie opened 1 year ago
I have found one way to trigger this consistently is by changing the image_manipulations.cache
config value from false
to true
.
Two other people in Responsive Images have also reported that this can happen when editing content, one of them saying that it is possible that they were editing while a deploy was happening. However I am not aware of reproducible steps for this one unfortunately.
Hey @stuartcusackie,
Since this came up in on our helpdesk I'm curious: Which cache driver are you using? Redis by any chance?
Hi @joshuablum
It's been a while but it must be using the File cache driver, since that's all I ever use.
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.
I am using Spatie's responsive image package so I opened an issue there and the problem appears to have been solved by a package update. I will keep this issue open though as the author (ncla) states that Statamic catches these errors for glide:data_uri however the same error can still occur for
glide:data_url
How to reproduce
No idea.
Logs
Environment
Installation
Fresh statamic/statamic site via CLI
Antlers Parser
None
Additional details
No response