[TYPO3-mvc] After introducing "tx_extbase_type" my frontend users aren't outputted

Marco Huber Marco.Huber at marit.ag
Wed Apr 21 10:09:08 CEST 2010


 
 


Hi Jochen,

>
> 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?
>


> this might work in this case, because you created the type field, but
i 
am not sure if this can be the "general" solution to avoid such a 
problem. If a model does not care about the type field, than it 
shouldn't be part of the generated query.

> If it does care and distinguishes between the types, than a ts setting

or a property in the model should indicate, that the type field has to 
match.


Regards,
Andreas
_______________________________________________
TYPO3-project-typo3v4mvc mailing list
TYPO3-project-typo3v4mvc at lists.typo3.org
http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-project-typo3v4mvc


More information about the TYPO3-project-typo3v4mvc mailing list