[MGNLWEBDAV-11] Verify behaviour of move and rename operations Created: 19/Oct/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: WebDAV (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: 1.2

Type: Task Priority: Major
Reporter: Magnolia International Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Comments   
Comment by Jan Haderka [ 26/Oct/09 ]

definitively some issues here caused by attempts to move node to its non-extension version

2009-10-26 12:51:49,202 DEBUG o.magnolia.module.webdav.servlet.MgnlWebdavServlet: dav: moving /magnoliaAuthor/.webdav/resources/c4.css to /c4

Happens occasionally when trying to edit file with some simple editors like vi that like to move the original file to backup version and then save edited version as a new file under the old name. If the editing cycle is slow enough for the fs caches to be flushed to the repo, the issue is less likely to occur.

Comment by Magnolia International [ 09/Nov/09 ]

Since the above log logs "from" as the request URI and "to" as the repository path as massaged by the ResourceLocator, it is not surprising that the extension is gone, since that's essentially what our ResourceLocator does.

Comment by Magnolia International [ 13/Sep/12 ]

Renaming from the OSX Finder seems to work.
However, editing from some applications (IntelliJ for example) seems problematic, apparently because of the save-to-temp-file-then-rename procedure they apply. Needs further investigation.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 11:10:54 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.