davidof
New Member Posts:2
|
01/08/2013 2:03 PM |
|
I'm using version 05.03.09 of DMX and version 05.06.02 of DNN. I have encountered an issue where someone opened a folder using Windows Explorer, and uploaded multiple files. When viewing the folder from the DMX ajax interface only a single old file is shown, but if the folder is opened with windows explorer all the newly added files are shown. After a bit of investigation i discovered this occurs when a user soft deletes a folder and then recreates the folder with the same name. Webdav seems to recognise the newer folder but dmx still points to the older soft deleted folder. To get round this i just downloaded all files from windows explorer and dmx, hard deleted both folders, recreated and uploaded files. I am wondering what would be the best method of preventing this from happening in the future, is there a way to prevent users from creating folders with the same name as a deleted folder or would somebody have a better solution? |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
01/09/2013 11:40 AM |
|
The fact that DMX loads the old folder means you had (Doc)Admin rights, correct? The old folder was deleted and a new one was created. Then WebDAV continued with the new folder. In a sense I think this would be as expected. The old one was flagged for deletion. Are you saying the deleted folder should have been revived when the user recreates it? I'm not saying that shouldn't be so, but just want to know what you think. Peter |
|
|
|
|
davidof
New Member Posts:2
|
01/10/2013 1:06 PM |
|
Users cannot see newly added files on DMX, which leads to confusion. I am looking for the best way to avoid this |
|
|
|
|
Peter Donker
Veteran Member Posts:4536
|
01/10/2013 2:43 PM |
|
If the delete happened in the Web UI, it is always a soft delete. If it is done through WebDAV it is either a soft or a hard delete depending on the setting on the main options page. You could optionally empty the recycle bin every so often in a scheduled task. This is not a waterproof solution to your issue, but it'll probably prevent it from happening again. Peter |
|
|
|
|