Multiple jcr:content in the PagePersistenceStrategy

Description

Configurations:

Using this configuration in combination with the page persistence strategy will yield 'no context path available' errors because the getCollectionItemConfigName from the page persistence strategy adds jcr:content when it wasn't supposed to.
You get faulty links like ...FooterConfig/jcr:content/menu/menu1/jcr:content/links instead of ..FooterConfig/jcr:content/menu/menu1/links where it's actually persisted and thus triggering these kind of issues. Changing the getCollectionItemConfigName in the PagePersistenceStrategy to the code below seems to fix that issue.

Status

Assignee

Stefan Seifert

Reporter

Bart Wulteputte

Labels

None

Components

Priority

Minor
Configure