[TYPO3-mvc] After introducing "tx_extbase_type" my frontend users aren't outputted
Jochen Rau
jochen.rau at typoplanet.de
Wed Apr 21 09:09:02 CEST 2010
Hi.
On 21.04.10 09:03, Stephan Reuther - development.IT wrote:
> Zitat von Jochen Rau <jochen.rau at typoplanet.de>:
>
>>>
>>> The fields are added but Ext. Manager keeps complaining about
>>>
>>> ALTER TABLE fe_users CHANGE tx_extbase_type tx_extbase_type
>>> varchar(255);
>>> Current value: varchar(255) default ''
>>> ALTER TABLE fe_groups CHANGE tx_extbase_type tx_extbase_type
>>> varchar(255);
>>> Current value: varchar(255) default ''
>>
>> This message is caused by the way TYPO3 compares the actual field
>> definition with the field definition demanded by the extension. It's
>> annoying but causes no dysfunction.
>>
>
> To prevent this "unattractive" message just add a " DEFAULT '' " to
> the mentioned sql statements.
>
> Like:
> CREATE TABLE fe_users (
> tx_extbase_type varchar(255) DEFAULT ''
> );
Sure. But the dafault should be NULL to distinguish between the types
'0' or '' and 'not set, yet'.
I am currently thinking about having '0' as default field value and
adding "recordType = 0" to the TS setup, that may solve the problems
described in this thread. What do you think?
Regards
Jochen
More information about the TYPO3-project-typo3v4mvc
mailing list