[MGNLCT-124] Content bootstraps at startup should succeed when namespace and nodetype defined in YAML content type file Created: 17/Jun/19  Updated: 19/Nov/19

Status: Open
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Major
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 7
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
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)
Release notes required:
Yes
Documentation update required:
Yes

 Description   

Bootstraps with content which has namespaces or nodetypes defined in Content Type Definition files fail to install correctly at system / module startup.

The bootstraps should install correctly.

This was originally reported by uscheidegger on docs page:
https://documentation.magnolia-cms.com/display/DOCS60/Content+type+Data+source+definition?focusedCommentId=194481371

Possibly the system should scan all modules first for content type definitions, before any bootstrap loading.


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