[TYPO3-core] RFC #11221 : Feature : Separate firstname and lastname columns in fe_users table

[JoH asenau]

> we voted for this.
> I don't think this is really bloating.
> 1) it must be backward compatible

That's the case as long as the extension is not creating a new table but
extending the original fe_users table.
It could be part of the extension list that's already showing up in the
install tool to give you stuff like the scheduler.
After all this is what compat versions are for.

> 2) the fields should be a basic set, and name parts are really basic
> parts. So you should build up your site without using extension.

Basic parts to enable or disable an fe_user login at a restricted site are:
username, password, groups and enable fields - that's it.
A real name will only be necessary if you want to adress this fe_user
personally - i.e. at a "myDomain" site or a shop system.
The fe_user record is just the key to a locked room, which is not
necessarily connected to just one person.

> Again, as it's for 4.4, there is the chance to make a proper proposal
> with patch etc for a new model. Again basic fields should be in core,
> anything else could be part of an extension eg a A-class user register
> with dynamic field additions.

I fully agree, but Benni was not talking about a new model but about a
streamlined core, which is something completely different.

So +1 for the revert.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your gob sometimes!)
Dieter Nuhr, German comedian
Xing: http://contact.cybercraft.de
Twitter: http://twitter.com/bunnyfield
TYPO3 cookbook (2nd edition): http://www.typo3experts.com