Project

General

Profile

Actions

Bug #67107

closed

Fieldtypes "none" and "user" auto-save field value on record creation

Added by Andreas Wolf over 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
DataHandler aka TCEmain
Target version:
Start date:
2015-05-22
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When a field is configured with type "none" or "user", FormEngine sends a value to DataHandler when the record is created. This could lead to errors if the field is not present.

For further save attempts of existing records, no value is sent. This behaviour is inconsistent and should be fixed in one or the other direction (I tend to never set a value, at least for user).

Actions #1

Updated by Andreas Wolf over 9 years ago

  • Category changed from FormEngine aka TCEforms to DataHandler aka TCEmain

The field is not set by DataHandler, but the default value is initialized by DataHandler, so this is where this should be fixed.

If a default value is specified for type none, this should be set, but otherwise the field should be left out.

Actions #2

Updated by Alexander Opitz over 9 years ago

  • Target version changed from 6.2.13 to 6.2.14
Actions #3

Updated by Alexander Opitz over 9 years ago

  • Target version changed from 6.2.14 to 6.2.15
Actions #4

Updated by Alexander Opitz about 9 years ago

  • Target version changed from 6.2.15 to 6.2.16
Actions #5

Updated by Christian Kuhn about 6 years ago

  • Status changed from Accepted to Closed

i tested this again: type=none (at least in v9 master and probably since v7) does NOT neccessarily need a db field in the database and as far as i can see, it is also never written.
for type=user this is different, a db field must exist.

Actions

Also available in: Atom PDF