[MGNLCT-128] CTs should support multiple tabs in editing dialogs Created: 16/Jul/19  Updated: 25/Mar/22

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

Type: Bug Priority: Medium
Reporter: Scot Rhodes Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File autohandler-app.yaml     File autohandler.yaml     File es-cluster-app.yaml     File es-cluster.yaml    
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
Release notes required:
Yes
Documentation update required:
Yes
Date of First Response:
Epic Link: Headless Backlog

 Description   

Cannot display contentType property in an additional tab

It is not possible to properly display a contentType property in any other tab then the first one, "default".

If in the app definition you simply include the name of the property in the fields list of a second tab, there is no change to the UI - the field for the property is still displayed in the first tab.

See 'biography' in the attached Autohandler example

If in the app definition you include the name of the property in the fields list of a second tab, AND give it a specific class or fieldType, the the field is displayed in both the first tab and the second tab.

See 'summary' in the attached Autohandler example.

 

As a developer, based on how everything else works in Magnolia I expect that if I list the name of a ContentType property in the fields list of a new tab (as is done for both 'biography' and 'summary' above) that the fields will be displayed in those tabs, not the default one.

 

 



 Comments   
Comment by Christopher Zimmermann [ 22/Jul/19 ]

Changed description and attached 'autohandler' example which is a reduced example to emphasize the problem.

Comment by Christopher Zimmermann [ 11/Jun/20 ]

Workaround, but you have to redefine the fields under the tabs.
!content-type-m5:submission
name: submissions-m5
label: Submissions M5
subApps:
detail:
editor:
form:
tabs: !override
"first":
fields:

  • name: title
    fieldType: text
  • name: abstract
    fieldType: text
    rows: 2
    "second":
    fields:
  • name: speaker
    fieldType: text
  • name: resources
    fieldType: text
    rows: 2
Generated at Mon Feb 12 00:37:25 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.