I bought Directory Opus 12 Pro couple of days ago and I must say that this is hands down the most enjoyable and throughout "just like what I needed" that I have found to date when it comes to file management. Good job guys, I really mean it. Keep up the awesome work.
But now the one thing that keeps being an issue for me with my 2 Synology NAS's (920+ and 218+). I encountered an "directory not empty, can't delete" issue multiple and multiple times when deleting folders.
I pinpointed the issue to be the extended attribute directories called @eaDir that are in the millions here and there. Is there a way for Directory Opus to recognize the @eaDir folders and delete them also when deleting the folder that has them?
If you delete a folder, Opus would normally delete the subfolders first. If Synology has a special synthetic folder inside which can never be deleted, that's non-standard. But Opus would probably still go on to request that the folder itself be deleted, and the "directory not empty" error then comes from the operating system, and ultimately from the NAS.
So it sounds like an issue with the NAS, not with Opus. I'd expect the same problem to happen no matter which software was used to delete the folder in that case, unless something strange is going on.
Just tried this on my Synology DS418J and seems no issue. Created a new folder with three hierarchical sub-folders, copied some files to the base level folder then moved back to the root and selected the folder and hit delete. Worked fine.
Perhaps permissions on your Synology are not set correctly for the specific user with which you are accessing the directory through Opus or something on the Synology has the file/folder locked.
I think I got that @eaDir idea wrong (I thought that Dopus just can't see them at all). The move / cut/paste issues seem to be "random" that gets solved if I move other folder first and then retry to move the one that gave an error. Or sometimes it seems to get through if I retry.
There seems to be an permission(?) issue with Icon files (Icon, Icon_, Icon$) instead, especially when trying to delete folders. Might be related to my different user accounts for my PC and MAC, although they are the same permission-wise (group, both users not admins). So I think that coherent "can't delete issue" is going to be solved through this. The NAS's are ~6 months old and btrfs scrubbing done 6 days ago, just to mention.
There's another thing to ask about that I am wondering and like to get cleared out (sorry if I should have created a new thread for this):
I am moving lots of assumed duplicate folders onto each other with "merging in mind", so I repeatedly do this:
CTRL + 2 to move
Click Skip > Skip all
After the moving starts, I get an error about "the folder is not empty"
Click Skip > Skip all conflicting
Dopus does its thing and this might sometimes be quite slow (comparison?)
When the operation is done, I delete the source folder because it is now merged
And my questions are:
What is that step (3) when I get warned about a folder not being empty, when I already have "answered to that" with the first dialog when I am being asked do I want to replace or skip the files that are found in the destination?
Is there a more straightforward operation to do "folder merging" that I configure once and just merge folders with "one click"?
That "folder not empty" after skipping things is happening because the source folder can't be deleted as part of the move, as there are still things left in it (the skipped items).
It's something we're going to improve in the future as while it's a "true" error, it's not a very useful one.
"Source folder cannot be deleted because having skipped items" --> got it
But why do I have to do the step 4, when I have already done it (afaik) before the move operation started on step 2? Feeling stupid here.
Ps. that folder merging / duplicate folder handling is the main thing going on for me atm. There are multiple copies of the same folder here and there that have e.g. "files for project X from different times, and have files being saved in different times". So If I would delete all but one of them, I would delete unique files --> have to merge all the folders. Those works are separated because of "foldering by month" and some random copy backups and so one.
Really hard to tell "which is the right one", so have to just merge them all and that's it. Would be more than awesome to have a duplicate folder feature, so I could just search for "exact and partial" folder duplicates and merge them right there. (The folder names can change that indicate timestamp or something else)
I'm not sure, to be honest. It needs investigating in detail, which will take some time. I think we may have already fixed it internally as I can only reproduce the problem with 12.24, not our current codebase, but it may be more complex than that.
Using the Unattended mode may avoid having to click skip for the non-empty folders.
Yes the unattended would be a thing -- but it is that step 4 dialog that has that unattended option. I like the options etc. on those dialogs, I just don't know why there are 2 different (and I mean different too, not the same "replace or skip" dialog implementation) dialogs asking the same thing (to which I answer "skip all") as far as I understand them. There might be a point, but does not come up to my mind atm. But good to know that it might have been under the works already.
I can click unattended option checked after this error dialog, so it does not solve this issue because that option should be on the first dialog so this error dialog does not even appear. Just wondering.
