Details
-
Bug
-
Resolution: Obsolete
-
Neutral
-
None
-
None
-
None
Description
On a norsu contenttype based app, if the model has a property called 'name', the field is displayed as expected in the editor subapp. But the delivery endpoint does not deliver a 'name' property, it only delivers a '@name' property in the '@metadata' node.
Expected:
name property exists in main content..
On JCR-based contenttype, the rest response includes both a metadata (the jcr @name) and the actual content.
Actual:
name property does not exist in main content. '@name' property in the '@metadata' node.
Note:
On JCR content and delivery endpoint, there is a "name" property and a "@name" metadata property.
See comparison here: https://wiki.magnolia-cms.com/display/PMTEAM/Test+Norsu+Contenttype+and+Delivery+endpoint#TestNorsuContenttypeandDeliveryendpoint-CompareNorsuandJCRresponseforContentType
Checklists
Attachments
Issue Links
- is superseded by
-
MGNLCT-347 Norsu-based contenttype uses '$type: nameField'
-
- Closed
-
- relates to
-
MGNLCT-310 'name' property on Submodel is not stored (Norsu)
-
- Closed
-
-
MGNLCT-312 (Norsu) Contenttype model with no 'name' property shows two 'title' fields in editor
-
- Closed
-