[MGNLFORM-342] Decorated form processors do not execute Created: 19/Jan/21  Updated: 19/Mar/21  Resolved: 09/Mar/21

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

Type: Bug Priority: Major
Reporter: Richard Gange Assignee: Quach Hao Thien
Resolution: Cannot Reproduce Votes: 0
Labels: JavaScript, VN-Maintenance, maintenance
Remaining Estimate: Not Specified
Time Spent: 7.5h
Original Estimate: Not Specified

Issue Links:
Relates
relation
is related to MAGNOLIA-8036 Allow decoration of light modules who... Accepted
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
Sprint: Maintenance 47

 Description   

It's possible to decorate the form component's (form:components/form) formProcessor configuration node but that decoration is ignored when the processors are executed by the method AbstractFormEngine#executeProcessors(). The problem is the TemplateDefinition provider is not being used.

Targeted config:
/modules/form/templates/components/form/formProcessors

Using the Definitions app you can see the form component template is being decorated. Decoration is technically possible but the AbstractFormEngine needs to get the processor list from the aggregated template definition and not directly from JCR.

This is an important issue for those using cloud 1 because you want to be able to create complex forms, use JavaScript for processing and configure the processor with decoration rather than bootstrap.



 Comments   
Comment by Richard Gange [ 09/Mar/21 ]

Cannot reproduce in 6.2.6

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