Feature #59129

Allow placeholder usage independently from useOrOverridePlaceholder

Added by Alexander Stehlik about 6 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2014-05-26
Due date:
% Done:

100%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Currently the placeholder value of a field will only be displayed if the mode config is set to useOrOverridePlaceholder.

I don't really see why this is handled like this. As soon as a placeholder is configured it should be displayed.

useOrOverridePlaceholder should only have influence on the display of the override checkbox (where the overwritten value is displayed).

Associated revisions

Revision f70e5986 (diff)
Added by Alexander Stehlik over 5 years ago

[BUGFIX] Placeholder attribute without useOrOverridePlaceholder

The placeholder configuration for a TCA field will now be considered
independently from the "mode" being set to "useOrOverridePlaceholder".
If a placeholder is set in the TCA it will be rendered. The mode
setting only changes the behavior of the NULL checkbox.

Resolves: #59129
Releases: master, 6.2
Change-Id: Ice7681d644623a5e94cbdd22743ddf5aab8919a9
Reviewed-on: http://review.typo3.org/30433
Reviewed-by: Frans Saris <>
Tested-by: Frans Saris <>
Tested-by: Mathias Schreiber <>
Reviewed-by: Mathias Schreiber <>
Reviewed-by: Ernesto Baschny <>
Reviewed-by: Stefan Neufeind <>
Tested-by: Stefan Neufeind <>

Revision b4d5497d (diff)
Added by Alexander Stehlik over 5 years ago

[BUGFIX] Placeholder attribute without useOrOverridePlaceholder

The placeholder configuration for a TCA field will now be considered
independently from the "mode" being set to "useOrOverridePlaceholder".
If a placeholder is set in the TCA it will be rendered. The mode
setting only changes the behavior of the NULL checkbox.

Resolves: #59129
Releases: master, 6.2
Change-Id: Ice7681d644623a5e94cbdd22743ddf5aab8919a9
Reviewed-on: http://review.typo3.org/35175
Reviewed-by: Stefan Neufeind <>
Tested-by: Stefan Neufeind <>

History

#1 Updated by Gerrit Code Review about 6 years ago

  • Status changed from New to Under Review

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/30433

#2 Updated by Gerrit Code Review over 5 years ago

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

#3 Updated by Gerrit Code Review over 5 years ago

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

#4 Updated by Gerrit Code Review over 5 years ago

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

#5 Updated by Gerrit Code Review over 5 years ago

Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/35175

#6 Updated by Alexander Stehlik over 5 years ago

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

#7 Updated by Claus Harup over 5 years ago

I was just wondering when the bugfix will find its way into the 6.2.x core - I cant seem to find any information about that?!

#8 Updated by Alexander Stehlik over 5 years ago

Hi Claus,

the patch was already merged in the 6.2 branch so it should be in the next release 6.2.10. There was already an release candidate published for 6.2.10 so it should not take that long any more :)

Kind regards,
Alex

#9 Updated by Benni Mack over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF