-
Bug
-
Resolution: Duplicate
-
Neutral
-
None
-
None
-
None
-
Same bug occurs under Windows 10 and Windows Server 2019.
Steps to reproduce
- Install Magnolia CE 6.2.10 with CLI (mgnl jumpstart)
- Startup, instance and Login un author instance
- Create a page with basic template. Publish the page.
- Create an (empty) folder in assets. Publish the folder.
Expected results
.. Page and Asset Folder should be on the public instance
Actual results
- Page is not on the public instance. No error raised.
- Publishing the empty asset Folder generates the following exception
java.nio.file.InvalidPathException: UNC path is missing sharename: /\dam\/
Bug seems not te be related to the OS version.
Workaround
No Workaround
Development notes
Problem seems to occur since 6.2.9. Problem does not exist on 6.2.8
Publishing seems not to work on the top level item of any workspace. It works well on any item bellow the top level. In order to check this you need a setup with already published top level items (setup on magnolia up to version 6.2.8). You may then upgrade it to 6.2.10.
The bug seems to affect all workspaces. Tried with pages, dam and a custom workspace,
The bugs seems to be independend of the OS version.
- duplicates
-
EEPUBLISH-37 Publication fails on Windows machines with path based locking
- Closed