Closed (fixed)
Project:
Web File Manager
Version:
6.x-2.12
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
2 Aug 2010 at 08:16 UTC
Updated:
18 Oct 2010 at 23:06 UTC
Hi,
For a long time now I cannot move files into new subdirectories. If I try to upload the file, regardless of size and type, I get a "...could not be copied" and "...failed" in the pink box. If I try to move the file, I get a 'read-only' in yellow. These problems do not occur in the subdirectories. The problem started long back and I have since upgraded the WebFM version several times into the current version, but no joy. Would appreciate advice, as I rely heavily on this module.
thanks
Comments
Comment #1
lilon commentedclarification: by "move the file" I mean, uploading the file into an 'old' subdirectory and using drag and drop to move it to the destination 'new' folder.
Comment #2
lilon commentedI've done a bit more digging and the uploaded file is being uploaded to the temp directory and gets stuck there. Cannot be moved into the WebFM subdir. I looked at permissions and the new subdirectories I have been creating are getting 775, whereas the old ones have 777. I thought that 775 is ok on linux based hosts?
My WebFMDocumentsRoot folder sits inside the /sites(755)/default(755)/files(777)/myWebFMDocumentsRootFolder(777)
Thanks again
Comment #3
nhck commentedlilion thank you for posting this. I am sorry to say that I have not been able to replicate the reported behavior. I would like to suggest that you take a look at the servers error_log and your php.ini.
Thank you
Comment #4
lilon commentedI am thinking of removing Webfm all together and then reinstalling it. What will then happen to all the directories and the files in them when I reinstall. Will they be recognised by the new installation or will I need to delete and reupload?
Also, what will happen to all the files which are currently attached to nodes?
thanks
Comment #5
cgmonroe commentedIf you "uninstall" a module, the tables created get deleted. With WebFM this means that you loose the entries in the DB that define the files and their access rights.
To add the files back in with the default permissions, etc, someone with webfm admin privileges needs to use the "add to db recursively" option. Note that if there are a lot of files to be added, you could hit PhP's timeout / execution time limits.
Attachments are linked via the fid number in the webfm_file table (and stored in the webfm_attach table). If you drop both these tables, all current nodes with attachments will end up with none.
Also, the URLs to access files with webfm are based on the fid value. So, when you rebuild the db table, files will be added by directory and not by upload order. So, if anyone has used URLs to the files (like images in posts), the URLs will probably return the wrong file.
If you want to rebuild the tables, it might be best to dump the current data in the webfm_file and webfm_attach tables, uninstall, then import the data you dumped back in.
FYI - There is also an option to have cron "clean up" the database by removing any file entries for files that don't exist anymore.
Comment #6
nhck commented