[MGNLUI-5579] New content from content apps using content connectors is not saved to their configured root paths Created: 26/Sep/19  Updated: 23/Jul/20  Resolved: 28/Dec/19

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.5, 6.2

Type: Bug Priority: Neutral
Reporter: Julian Nodarse Assignee: Mikaël Geljić
Resolution: Fixed Votes: 0
Labels: 61
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCT-153 datasource-rootPath is ignored when i... Closed
causality
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:
Epic Link: Support
Sprint: SPA Editor 13
Story Points: 2

 Description   

Content Apps that share workspaces and use a content connector do not save newly created content in the location configured within the rootPath property.

Can confirm on 6.1.2 by creating 2 content apps that share the same workspace then having each one have different rootPaths. When you create new content, you will see that they do not appear within the content app, but they do appear in the JCR saved to the root of the workspace instead of the configured rootPath. If you move the new content node from within the JCR into the proper rootPath node manually, then the newly created content appears in its respective content app.

See linked support ticket for examples and screenshots.

This appears to be due to missing/incomplete content connector configuration within the detailTemplate.yaml file Magnolia uses to construct content apps from the content type. If we override the content connector's rootPath manually then it works.



 Comments   
Comment by Thomas Duffey [ 10/Dec/19 ]

This appears to be due to missing/incomplete content connector configuration within the detailTemplate.yaml file Magnolia uses to construct content apps from the content type. If we override the content connector's rootPath manually then it works.

Generated at Mon Feb 12 09:27:58 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.