[MGNLPCK-42] Packages Containing "only sub nodes" Cannot Be Installed Created: 18/Apr/11  Updated: 07/Sep/11  Resolved: 23/Jun/11

Status: Closed
Project: Packager (closed)
Component/s: None
Affects Version/s: 4.0.5
Fix Version/s: 4.0.6

Type: Bug Priority: Major
Reporter: Lee Haslup [X] (Inactive) Assignee: Ralf Hirning
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows Tomcat Derby (none of this matters)


Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

When a package is defined with ACL items that specify "only sub nodes" such packages cannot be installed. This is possibly related to MGNLPCK-41 which I had previously believed to affect the display of the package in the packageOpen dialog but further experimentation reveals that the packages are not merely misdescribed but cannot be installed.

I have a package that has an ACL line that reads Include | only sub nodes | (website/)secure-operations

When I attempt produce a backup of this package and attempt to install it in a difference instance of Magnolia the following error messages appear in the log:

2011-04-18 12:47:32,093 ERROR mgnl.magnolia.cms.pack.model.jcr.JcrRepositoryUtil : failed to resolve path 
secure-operations/* relative to node /: 'secure-operations/*' is not a valid path. '*' not a valid name 
character. 

This error also occurs when the packageOpen dialog displays the package.

Also, the packageOpen dialog for the uploaded package differs from the packageOpen dialog for the package from which the backup was made in that the uploaded package shows a "/*" after the line in the package. ie:

Package	      Include	this and sub nodes	/imaging/ncmmis-standard/*
              Include	this and sub nodes	/website/ncmmis-standard/*
              Include	this and sub nodes	/website/secure-operations/*

One final note: It would be nice if there was some indication when a package fails to install because of an error. Currently, the only way to know that an error has occurred is to notice that the installation went really fast, or to dig through the magnolia-error.log looking for package-installer-ish error messages.



 Comments   
Comment by Ralf Hirning [ 23/Jun/11 ]

If the type was sub, the path was not always extracted correctly from the package.
Corrected in trunk

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