[PUBLISHING-123] Top level nodes cannot be published on magnolia 6.2.10 Created: 27/Jul/21  Updated: 19/Jul/22  Resolved: 28/Jul/21

Status: Closed
Project: Publishing
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Lucien Elin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Same bug occurs under Windows 10 and Windows Server 2019.


Issue Links:
duplicate
duplicates EEPUBLISH-37 Publication fails on Windows machines... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: Nucleus Quality Maintenance
Team: Nucleus

 Description   

Steps to reproduce

  1.  Install Magnolia CE 6.2.10 with CLI (mgnl jumpstart)
  2. Startup, instance and Login un author instance
  3. Create a page with basic template. Publish the page.  
  4.  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. 



 Comments   
Comment by Mercedes Iruela [ 28/Jul/21 ]

Hello Lucien,

Thanks for reaching out.

This is a known issue that we are working on EEPUBLISH-37 to fix it, however you should be able to workaround the issue, please take a look at our documentation: Known Issues - Cannot publish content with path based locking.

Hope this helps, I am closing this issue as duplicated.

Regards,
Mercedes

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