[MAGNOLIA-4939] maxComponents property causes editing capabilities to become disabled when max is reached Created: 28/Mar/13  Updated: 17/Apr/13  Resolved: 16/Apr/13

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: 4.5.8
Fix Version/s: 4.5.9

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MAGNOLIA-4901 Add possibility to set maximum number... Closed
dependency
depends upon MGNLUI-1028 maxComponents property causes editing... Closed
relation
is related to MAGNOLIA-4116 Render areas of type list that don't ... Closed
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   

When the property maxComponents is used it can cause components to become un-editable. Meaning, the edit bar is not shown.

Here are some steps to recreating this issue on the demo site:

  1. Add the maxComponents here: config:/modules/standard-templating-kit/templates/components/features/stkFAQ/areas/faqItems[maxComponents] = 1
  2. Load http://demoauthor.magnolia-cms.com/demo-project/service/faq.html

It appears that when the number of components reaches the maximum not only is the new component option disabled but also the edit options are disabled.



 Comments   
Comment by Roman Kovařík [ 03/Apr/13 ]

Port to master is missing.

Comment by Roman Kovařík [ 04/Apr/13 ]

The second part of this fix for 5.0 is under MGNLUI-1028.

Comment by Jan Haderka [ 09/Apr/13 ]

It seems you are reintroducing old code in master in AreaBarTagTest and AreaDirectiveTest

-        paragraph1.addNode("stage", NodeTypes.Area.NAME);
+        paragraph1.addNode("stage", MgnlNodeType.NT_AREA);

AFAIR NodeTypes are replacing MgnlNodeType

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