Jan wrote:Hi, the not deleting original images has a lot of reasons there.
E.g.:
- original images can be uploaded by other methods (ftp, media manager, etc). So Phoca Gallery cannot delete images which were not uploaded by the Phoca Gallery
- original image can be used for e.g. 5 entries in database (because there are two layers - database and file layer), so if you will delete it then it can be missed for other entries (e.g. for using it while downloading, recreating thumnails, rotating, etc.)
- if you work with images (image names in database), it can be very quickly and it is not time and performance consuming... if this will work with physical files on the server too, then the server can have problems with not enough memory and cpu. I have tested the function which will check the files (if they are not used anymore) but the searching physical files was so slow and took a lot of memory so such function was not implemented...
I think there are more possible problems (I don't remember them all
) but they are surely described in this forum, so if you are interested, try to search this forum...
BTW: This works only for backend and not for frontend. In frontend original files will be deleted if user deletes the image (there is other system for accessing the files and some functions which are working in backend are not working here)
Jan
I just have to ask some questions because i am curious. I´m not a Joomla developer so i don´t know about the inner workings of coding for Joomla. But i am an experienced PHP developer. So i can relate to the points you pointed out. But still have some questions. Maybe you can explain them to me (if you have the time) so i can understand more about Joomla.
"- original images can be uploaded by other methods (ftp, media manager, etc). So Phoca Gallery cannot delete images which were not uploaded by the Phoca Gallery"
Why? Because of file and directory rights? Can´t u use chmod() to fix this issue?
"- original image can be used for e.g. 5 entries in database (because there are two layers - database and file layer), so if you will delete it then it can be missed for other entries (e.g. for using it while downloading, recreating thumnails, rotating, etc.)"
I guess you mean that the data has relations...can´t u use transactions for this? If something fails...rollback.
"if you work with images (image names in database), it can be very quickly and it is not time and performance consuming... if this will work with physical files on the server too, then the server can have problems with not enough memory and cpu. I have tested the function which will check the files (if they are not used anymore) but the searching physical files was so slow and took a lot of memory so such function was not implemented..."
A couple of years ago a wrote a file/image library where you can upload, view, edit and delete the items. It works ONLY in file layer...no DB used. And it has worked pretty good but i don´t know any limits of the system (intended for small business owners as a webbased harddrive).
The problem with not having a "Delete image" function is pretty serious. My clients are pretty unexperienced computer users. I installed Joomla and Phoca and has taught them how to work with it. The problem is that the webservers harddrive fills up pretty fast. And how do i clean up old files? It´s hours and hours of work stepping through each file and see what files are used and not used. It´s a pretty big problem.
Maybe you can add a new page to Phoca named "Clean up". Then do the filechecking file_exists() function there?
Maybe you can also add it to the frontpage:
if (!file_exists($name_from_db)) then
displayNAImage();