bluemultimedia Posted November 14, 2018 Share Posted November 14, 2018 I ran into a weird problem with the WireTempDir (site/assets/cache/WireTempDir). A client uses cheap hosting that still works well with ProcessWire. But it does for some reason have a file & directory count limitation. And after reaching 260.000 files and directories the file system becomes read only. After some digging, I found that the site/assets/cache/WireTempDir was responsible for about 99% of the reported directories / files. It seems like the temp directories were never cleared. Now: I don’t think this a general ProcessWire problem, as I have other sites, that have an empty or – at least – not as full WireTempDir. Are there automated cleanup operations that may not be called due to some weird hosting issues? How are those dummy directories usually handled? Link to comment Share on other sites More sharing options...
bernhard Posted November 14, 2018 Share Posted November 14, 2018 Quote maxAge (integer): Maximum age of temp dir files in seconds (default=120) https://processwire.com/api/ref/files/temp-dir/ So it should keep itself clean by default... Link to comment Share on other sites More sharing options...
matjazp Posted November 14, 2018 Share Posted November 14, 2018 https://github.com/processwire/processwire-issues/issues/704 2 Link to comment Share on other sites More sharing options...
bluemultimedia Posted November 21, 2018 Author Share Posted November 21, 2018 Thanks matjazp! That helps! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now