Feature #31096
closed
Epic #69347: EXT:form - Optimize form wizard
EXT:form - Recipient field may be undefined
Added by Oliver Hader about 13 years ago.
Updated over 8 years ago.
Description
The recipient field of a form can by defined in the wizard. However the wizard can be saved and closed with keeping this setting undefined.
Result is a mail handling error in the frontend. The recipient field should be forced to be required in the form wizard.
Files
- Status changed from New to Accepted
- Target version changed from 4.6.0 to 4.6.1
- Target version changed from 4.6.1 to 4.6.2
- Target version deleted (
4.6.2)
- Status changed from Accepted to Needs Feedback
- Is Regression set to No
Hi,
does the problem still exists within newer versions of TYPO3 CMS (6.2.9)?
This is reproducible on current master.
- Status changed from Needs Feedback to New
- Category changed from Form Framework to 1602
- Category changed from 1602 to Form Framework
- Parent task set to #69347
- Tracker changed from Bug to Feature
- Target version set to 8 LTS
This is quite a huge task. Since we want to rewrite the form wizard I'm moving the ticket to version 8.
- Subject changed from Recipient field may be undefined to EXT:form - Recipient field may be undefined
- Complexity changed from easy to hard
- Status changed from New to Closed
- Target version deleted (
8 LTS)
- PHP Version deleted (
5.3)
The form wizard will be rewritten in version 8. We will add this requirement to the roadmap. The current wizard will not be touched anymore.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by 
Updated by