[MGNLFORM-7] The text field group requires a field name otherwise it throws an error Created: 15/Jan/09  Updated: 27/Nov/13  Resolved: 26/Jan/09

Status: Closed
Project: Magnolia Form Module
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Bug Priority: Major
Reporter: Boris Kraft Assignee: Teresa Miyar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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   

If I create a text field group, the dialog just states that I am unable to reference the text fields unless I give the group a name. Since the field is not required, if I leave it empty (because I don't care about referencing the text fields ) I get the error below.

I suggest to simply use default group names (prepopulate the group name with group-1 to n). And make the field mandatory. Also, the template should probably handle it more gracefully if no such group name exists - it should work because the group name is not required.

FreeMarker template error!

Expression content.controlName is undefined on line 3, column 12 in form/paragraphs/formGroupEdit.ftl.
The problematic instruction:
----------
==> ${content.controlName} [on line 3, column 10 in form/paragraphs/formGroupEdit.ftl]
----------

Java backtrace for programmers:
----------
freemarker.core.InvalidReferenceException: Expression content.controlName is undefined on line 3, column 12 in form/paragraphs/formGroupEdit.ftl.
at freemarker.core.TemplateObject.assertNonNull(TemplateObject.java:124)
at freemarker.core.Expression.getStringValue(Expression.java:118)

---------------



 Comments   
Comment by Christoph Meier [ 27/Nov/13 ]

it's fixed and very old.

Generated at Mon Feb 12 05:35:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.