Project

General

Profile

Actions

Feature #59129

closed

Allow placeholder usage independently from useOrOverridePlaceholder

Added by Alexander Stehlik almost 10 years ago. Updated over 5 years ago.

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

100%

Estimated time:
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).

Actions #1

Updated by Gerrit Code Review almost 10 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

Actions #2

Updated by Gerrit Code Review over 9 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

Actions #3

Updated by Gerrit Code Review over 9 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

Actions #4

Updated by Gerrit Code Review over 9 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

Actions #5

Updated by Gerrit Code Review over 9 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

Actions #6

Updated by Alexander Stehlik over 9 years ago

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

Updated by Claus Harup about 9 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?!

Actions #8

Updated by Alexander Stehlik about 9 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

Actions #9

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF