Comments? Deleted image Files Remain on server if REPLACED through C5 File Manager.
Permalink 1 user found helpful
Before I report this as a bug for C5 version 5.5 installs, I thought I hear what others have to say about this.
Problem:
If C5 File Manager Replace function is used to replace a file, and even if the old versions of that image file are removed or even if that image file is deleted, the original uploaded image file remains on the server. This can cause large amounts of (depending on hosting site design and usage) of wasted disk space per Concrete 5 installation.
Example:
Steps
1. An 8MByte image file is uploaded using C5 File Manager.
2. It is found that the same quality and relative size is displayed with an optimized image of 80KByte file.
3. The 80KByte file is uploaded using the C5 File Manager Replace upload function.
4. Later that whole image is no longer needed, and deleted using the C5 File Manager.
5. Scanning the WHW1 hosting server file system using WHW1 hosting control panel (cpanel) File Manager shows that the original 8MByte file is still on the server.
6. Even after old page versions are deleted, and cache cleared, and job updates done, and verification done that the file does not list in the C5 File Manager, the old 8MByte file continues to remain on the server. Even if the image was never used on a page design, and simply uploaded for testing and deleted, it gets left behind, but only if the REPLACE method is used.
Example Installation Info:
Concrete 5.5.2.1.
Problem is consistently reproducible.
Questions:
Known problem?
Best way to locate all the left over and unused and unneeded image files?
Actions taken by others against this problem?
Suggestions, feedback, or comments?
How to reproduce:
C5 Control panel >> Dashboard >> File Manger >> Left Mouse Click on an image file >> Select Replace >> Browse and Upload new image file >> Delete Old Version of Image File (extra step to be sure) >> Delete Image file using C5 File Manager >> Check for original file on hosting server.
Problem:
If C5 File Manager Replace function is used to replace a file, and even if the old versions of that image file are removed or even if that image file is deleted, the original uploaded image file remains on the server. This can cause large amounts of (depending on hosting site design and usage) of wasted disk space per Concrete 5 installation.
Example:
Steps
1. An 8MByte image file is uploaded using C5 File Manager.
2. It is found that the same quality and relative size is displayed with an optimized image of 80KByte file.
3. The 80KByte file is uploaded using the C5 File Manager Replace upload function.
4. Later that whole image is no longer needed, and deleted using the C5 File Manager.
5. Scanning the WHW1 hosting server file system using WHW1 hosting control panel (cpanel) File Manager shows that the original 8MByte file is still on the server.
6. Even after old page versions are deleted, and cache cleared, and job updates done, and verification done that the file does not list in the C5 File Manager, the old 8MByte file continues to remain on the server. Even if the image was never used on a page design, and simply uploaded for testing and deleted, it gets left behind, but only if the REPLACE method is used.
Example Installation Info:
Concrete 5.5.2.1.
Problem is consistently reproducible.
Questions:
Known problem?
Best way to locate all the left over and unused and unneeded image files?
Actions taken by others against this problem?
Suggestions, feedback, or comments?
How to reproduce:
C5 Control panel >> Dashboard >> File Manger >> Left Mouse Click on an image file >> Select Replace >> Browse and Upload new image file >> Delete Old Version of Image File (extra step to be sure) >> Delete Image file using C5 File Manager >> Check for original file on hosting server.
I have a site that is primarily a library of whitepapers. The site needs migrating, but, due to up to 8 versions of every file hosted, the overall size of the site + /files/ exceeds the space available in its intended destination. In the meantime, it is a drag on the other sites with which it currently shares a server.
In 2011, someone posted a script that would loop through and delete all inactive versions of files (The forum thread is here —http://www.concrete5.org/community/forums/chat/delete_versions_of_f... ), but that solution makes me a bit nervous.
I'm interested to hear how other people have dealt with this.