Project

General

Profile

Actions

Feature #53239

closed

TCEFORM disabled field must be not rendered but still editable

Added by Mehdi Guermazi over 10 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
FormEngine aka TCEforms
Target version:
-
Start date:
2013-10-31
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

If we disable a field with TCEFORM we don't want it to render but he should be able to edit it. If we must put a default value for a user without letting him see the field in the form we can't use the disabled option anymore.

example :
In the form of a content properties we disable the colpos field. On page module if we want to create a content in the left column the content is created in the center column because the user is not allowed to edit the colpos field.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #92119: Hiding field colPos for backend users breaks normal content creation and moving content between columnsClosed2020-08-27

Actions
Actions #1

Updated by Mathias Schreiber about 9 years ago

  • Tracker changed from Bug to Feature
  • Target version set to 7.4 (Backend)
Actions #2

Updated by Susanne Moog over 8 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #3

Updated by Benni Mack over 8 years ago

  • Target version deleted (7.5)
Actions #4

Updated by Alexander Opitz over 6 years ago

Hi, as the issue is very old I like to ask, do you still have this issue? Which TYPO3 version are you using?

Actions #5

Updated by Riccardo De Contardi about 4 years ago

  • Status changed from New to Needs Feedback

As far as I have understood from the description, the following page TSConfig should work

TCEFORM.tt_content.colPos.disabled = 1
TCAdefaults.tt_content.colPos = 1

am I missing something? Could we have a step-by-step example of what's not working?

Actions #6

Updated by Loek Hilgersom over 3 years ago

  • Related to Bug #92119: Hiding field colPos for backend users breaks normal content creation and moving content between columns added
Actions #7

Updated by Christian Kuhn over 2 years ago

  • Status changed from Needs Feedback to Closed

Closing due to lack of feedback and use case. To my knowledge, there are enough possibilities to readonly / hide fields using tca.

Actions

Also available in: Atom PDF