Project

General

Profile

Actions

Task #45807

closed

fe_users: Deprecate combined "name"-field

Added by Stefan Neufeind about 11 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
Start date:
2013-02-24
Due date:
% Done:

0%

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

Description

In tt_address the switch from one combined name-field to separate fields for first/middle/last name has been done quite some while ago. It's still there, but there is a setting in tt_address to disable it.

[disableCombinedNameField]
Check to disable the original tt_address name field after you updated your address records to the separate first, middle, and last name fields.

Imho we should consider a similar deprecation for fe_users as well.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #45799: feuser: Fields first_name/middle_name/last_name only if name shown as wellClosedMathias Schreiber2013-02-24

Actions
Actions #1

Updated by Mathias Schreiber over 9 years ago

  • Status changed from New to Accepted
  • 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 changed from 7.5 to 7 LTS
Actions #4

Updated by Gerrit Code Review over 8 years ago

  • Status changed from Accepted to Under Review

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

Actions #5

Updated by Gerrit Code Review over 8 years ago

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

Actions #6

Updated by Gerrit Code Review over 8 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/43679

Actions #7

Updated by Jigal van Hemert over 8 years ago

  • Status changed from Under Review to Rejected

A discussion of a few ACs with the product owner resulted in the decision that we can't create a solution for all cases; for the time being a general 'name' field together with the 'first name', 'middle name' and 'last name' fields will be useful for quite a few situations in West Europe. Therefore the patch was abandoned and the issue rejected.

If a website has further needs for extra fields and/or magic combination of name parts then it can be implemented in extensions.

Further reading about the complexity of names: http://www.w3.org/International/questions/qa-personal-names .

Actions

Also available in: Atom PDF