-
Notifications
You must be signed in to change notification settings - Fork 712
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replacement of symbolic links is no longer working #610
Comments
Hi Ufroehling, thanks for the detailed info on the bug, was able to recreate and will look into the cause. |
Commit b47bea tightened the Symbolic Link behavior but also introduced the bug you encountered. Submitted pull request to resolve. |
Did a little more research and don't think b47bea introduced the issue. Most likely it was later changes to FileSystemPageFactory.createSymbolicPage (bug only started happening with release 20140630). The fix remains the same. |
Issue #610 - Allow Sym Link rename/replace on existing Sym Link.
fixed by Matt |
I have a symbolic link with name=XyTeam and path=.MyApp/XyTeam/TrunK. Now i try to replace it i by entering the existing name and the new desired path = .MyApp/XyTeam/ReL11 and click on the Create/Replace button. I then get the error message "... already has a child named XyTeam ".
Version is the latest from 20150114.
In our live version 20131110 the replacement is still possible and used regularly.
The text was updated successfully, but these errors were encountered: