Bug #82471: Ext:form – Read-only form elements appear in confirmation screen and email - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Bug #82471

closed

Ext:form – Read-only form elements appear in confirmation screen and email

Added by Mario Lubenka about 7 years ago. Updated about 6 years ago.

Status:

Closed

Priority:

Could have

Assignee:

Category:

Form Framework

Target version:

next-patchlevel

Start date:

2017-09-13

Due date:

% Done:

100%

Estimated time:

TYPO3 Version:

PHP Version:

7.0

Tags:

Complexity:

Is Regression:

Sprint Focus:

Description

I saw that read-only form elements such as Static Text and Content element are still shown in the form confirmation and in the emails. That's a bug because the user can't enter information there and the "-" value suggests that the user entered this value.

E-Mail:

How to reproduce

Add the elements "Static Text" and "Content element" to your form
Submit the form in frontend
Check the email: you should see the following:
```
Static text: -
Content element: -
```

Files

Download all files

form_bug_text_contentelement_mail.png (15.8 KB) form_bug_text_contentelement_mail.png		Mario Lubenka, 2017-09-13 12:21
form_bug_text_contentelement_preview.png (30.5 KB) form_bug_text_contentelement_preview.png		Mario Lubenka, 2017-09-13 12:21

Actions

Copy link

Updated by Gerrit Code Review about 7 years ago

Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54131

Actions

Copy link

Updated by Gerrit Code Review almost 7 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54131

Actions

Copy link

Updated by Ralf Zimmermann almost 7 years ago

Status changed from Under Review to Resolved
% Done changed from 0 to 100

Applied in changeset d347054867c534dd70723ef15e1bd02bee09cfee.

Actions

Copy link

Updated by Česlav Przywara almost 7 years ago

Hi,

Is there any reason why the fix has not been cherry-picked for TYPO3 8.7.9 that has been released yesterday?

Actions

Copy link

Updated by Björn Jacob almost 7 years ago

No specific reason. Was forgotten during sprint. We will take care of it. Thx for mentioning.

Actions

Copy link

Updated by Gerrit Code Review almost 7 years ago

Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55837

Actions

Copy link

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55837

Actions

Copy link

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55837

Actions

Copy link

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55837

Actions

Copy link

#10

Updated by Björn Jacob over 6 years ago

Target version set to next-patchlevel

Actions

Copy link

#11

Updated by Gerrit Code Review over 6 years ago

Patch set 3 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55837

Actions

Copy link

#12

Updated by Gerrit Code Review over 6 years ago

Patch set 4 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/55837

Actions

Copy link

#13