[MGNLFORM-144] Update of forms module from 1.2.4 to 1.3.2 causes the confirmContentTypetext to not appear in email as its now replaced with contactMailBody Created: 29/Nov/12  Updated: 03/Dec/15  Resolved: 03/Dec/15

Status: Closed
Project: Magnolia Form Module
Component/s: migration & updates
Affects Version/s: 1.3.2
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Rory Gibson Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: form
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu


Issue Links:
duplicate
duplicates MGNLFORM-120 Content need an update when version 1... 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   

Update of forms module from 1.2.4 to 1.3.2 causes the confirmContentTypetext to not appear in email as its now replaced with contactMailBody.

This has affected about 159 forms on our site and means that when site visitors submit a form, the email message that is received has no content in it because the template value is not present in the same field as 1.2.4.

This may be related to
http://jira.magnolia-cms.com/browse/MGNLFORM-120
http://jira.magnolia-cms.com/browse/MGNLFORM-118
http://jira.magnolia-cms.com/browse/MGNLFORM-119

Some of which are still open.



 Comments   
Comment by Michael Mühlebach [ 03/Dec/15 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an outdated version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is together with it's associated version no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

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