[PAGES-31] Pages and DAM apps do not show bootstrapped contents Created: 27/Jul/15  Updated: 16/Jan/17  Resolved: 16/Jan/17

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 5.4
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Thomas Weckert Assignee: Jan Haderka
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Java8, Ubuntu Linux


Attachments: XML File dam.shared-contents.samples.xml    
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:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

In the website workspace I have my contents organized like this:

  • /shared-contents/text-image-combos/samples/test1
  • /shared-contents/text-image-combos/samples/standard

I export the folder /shared-contents/text-image-combos/samples and place the export into
/src/main/resources/mgnl-bootstrap/<my-module>/website.shared-contents.text-image-combos.samples.xml of my Maven module.

When I bootstrap the Magnolia module, the folder /shared-contents gets imported, but it is not shown by the pages app. I can make a search for "shared-contents" in the pages app, I get the proper search results. Also the website JCR browser shows the /shared-contents/text-image-combos/samples.

When I export /shared-contents instead of /shared-contents/text-image-combos/samples and bootstrap the module, the pages app shows /shared-contents as expected.

Same for the DAM app.

I attached a sample export/import for the DAM app.



 Comments   
Comment by Thomas Weckert [ 13/Aug/15 ]

Is somebody reading this... ???

Comment by Jan Haderka [ 16/Jan/17 ]

When you bootstrap multiple previously non existing levels, they are created as mgnl:content, however the "display content type" for pages app is mgnl:pages and for DAM mgnl:folder or mgnl:asset, thus such content is correctly not displayed. This is expected behavior. If you want to force type of parent structure, you need to bootstrap it explicitly and provide content type for it via bootstrap file or via update tasks.

BTW, if you meant to request support as an enterprise customer, you should have used https://support.magnolia-cms.com to report your problem. This project is meant exclusively for reporting issues in Pages app, but not under the terms of enterprise SLA agreement covering support.

Generated at Mon Feb 12 06:14:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.