[Gelöst] Forum bug: files in /wp-content/uploads/tmp/ wont be delete
This support ticket is created vor 2 Jahren, 5 Monaten. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.
I uploaded an image for another topic in this forum but my browser shown another (before uploaded) image with the same name.
So, i tried some other urls and reach this links.
Would i build a crawler wich goes trough any letter-sign-compination maybe i would get all images after a while ...
Mh, on my second test the images are correctly. I don#t know why my browser has shown this other images from /tmp as an preview.
The upload seems to work correctly now but the images are still there like https://toolset.com/wp-content/uploads/tmp/screenshot.png - maybe this tmp files should be deleted after a while?
Hi Shane,
this was more a recommendation than an issue 🙂
I would suggest to delete the files in your tmp folder after a while to prevent privacy and security interruptions.
And yes, set it as resolved.
Best
Before I make the recommendation to the relevant team. Can you explain is a much detail how I can replicate the issue so they too can understand the issue as well.
Again: I uploaded an image for another topic in this forum and my browser shown another image with the same name as preview.
I've checked the preview URL and came to the tmp folder. I've checked another simple file names (see my list) and recognized that your tmp folder will not be emptied after a while.
On my second try some days later the preview are correct.
The previously uploaded files still exists. Maybe this is a security or privacy risk. If not, mark this thread as resolved.