Project

General

Profile

Actions

Bug #84230

closed

renderType inputLink validation fails with "email" or "domainname"

Added by Gone With the Wind about 6 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
FormEngine aka TCEforms
Start date:
2018-03-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

The documentation on "inputLink":
https://docs.typo3.org/typo3cms/TCAReference/ColumnsConfig/Type/Input.html#rendertype-inputlink
mentions as possible values "email" and "domainname". To an integrator it seems to be logical to use those values with field that require the input of an email address or URL.
Furthermore, the design of such rendered input fields "recommend" to use the "Link Browser" to create those records with the use of the "Link Browser".

But if so, an error upon saving the record is caused, because (as I assume) the RegEx does not correctly parse the typoscript-like link string, that is generated as soon as any of the other offered fields (like "title" or "css-class") contain values. (Using ONLY the email or url field and leaving the others empty will work, but that would encourage people to create records that are not conforming to accessibility guidelines.)

Solutions that I could imagine:
  • The documentation clearly states that the use of "email" and "domainname" for evaluation purposes is not possible. In that case I wonder, if the Link Browser already checks for the validity of the url/email, which should be mentioned in the documentation.
  • Adapt the regexs...

The images included show the TCA configuration and the steps to create an email link, which eventually leads to the validation error.

(Not sure to which this problem should be assigned...)


Files

step_02.png (10.5 KB) step_02.png Gone With the Wind, 2018-03-13 09:33
step_01.png (23.6 KB) step_01.png Gone With the Wind, 2018-03-13 09:33
step_03.png (42.7 KB) step_03.png Gone With the Wind, 2018-03-13 09:33
step_04.png (15.5 KB) step_04.png Gone With the Wind, 2018-03-13 09:33
step_05.png (20.4 KB) step_05.png Gone With the Wind, 2018-03-13 09:33
Actions #1

Updated by Ralf Zimmermann about 6 years ago

  • Category changed from Form Framework to FormEngine aka TCEforms
Actions #2

Updated by Benni Mack about 5 years ago

  • Target version changed from next-patchlevel to Candidate for patchlevel
Actions #3

Updated by Susanne Moog about 4 years ago

  • Status changed from New to Closed

This is not a bug, this is just how eval works. You can add all eval variants to all kinds of input fields and renderTypes, however most combinations do not make sense. In your case eval=email and the linkbrowser combination does not work, but neither would an eval int or eval alpha for that matter.

Actions

Also available in: Atom PDF