[TYPO3-dev] Possible bug: Relations with MM_opposite_field don't update the relation count of opposite field
Franz Koch
typo3.RemoveForMessage at elements-net.de
Fri Feb 12 14:46:10 CET 2010
Hi,
>> It seems to simply allow two different tables to be selected in one go
>> (like the group field using multiple table relations), only that one is
>> stored with it's regular UID (foreign_table) and the other with negative
>> UIDs (uid*-1) in the uid-list of the field as long as it's a regular
>> select field of type string. As soon as a MM-table is used, it's acting
>> like a regular MM relation (all UIDs get stored in the regular way in
>> the MM table) only that two tables are related to one field.
>
> OMG what a conceptual horror! Maybe is should stay undocumented ;-)
yep, might be better ;) And I hope I interpreted the code correctly -
didn't do much testing though because I didn't want to mess up my system
and didn't have a DEV/test extension at hand. Maybe I'll have a closer
look the next days again, just to be sure.
> Thanks for digging.
NP.
--
kind regards,
Franz Koch
More information about the TYPO3-dev
mailing list