[TYPO3-dev] class.t3lib_tcemain.php $this->substNEWwithIDs
Franz Holzinger
franz at fholzinger.com
Tue Apr 25 18:57:23 CEST 2006
Hello,
can anybody confirm that this is a bug?
function checkStoredRecord($table,$id,$fieldArray,$action) {
,,,
foreach($fieldArray as $key => $value) {
if ($this->checkStoredRecords_loose && !$value && !$row[$key]) {
// Nothing...
} elseif (strcmp($value,$row[$key])) {
$errorString[] = $key;
}
}
causes this error message with the table tt_address extended with an
additional field containing an id to a mm table.
I have used an XCLASS. And in the modification the multiple selections
for tx_addresssearch_coating_id get stored in a mm table. However I do
not want that this writes anything into the tx_addresssearch_coating_id
field of tt_address.
So is this a necessary feature that the 1,4,5 in this case have to be
written into the tx_addresssearch_coating_id field when this
relationship has already been written into the mm table?
It would be a drawback if the tx_addresssearch_coating_id in tt_address
must be written, because it would make SQL queries more difficult. (e.g.
'... WHERE tt_address.tx_addresssearch_coating_id in (1,2,5)' would not
be possible :-( ).
Greets,
Franz
P.S.: Here the example values in the variables:
$fieldArray
String (10) phone 040-788884
String (5) tx_addresssearch_coating_id 1,4,5
Integer tstamp 1145981853
$row
String (1) uid 2
String (3) pid 541
String (10) tstamp 1145981853
String (1) hidden 0
String (23) name xxx
String (4) title yyy
String (0) email
String (10) phone 040-7888840815
String (0) mobile
String (0) www
String (19) address Mühlenhagen 777
String (35) company Company
String (7) city Hamburg
String (5) zip 20550
String (11) country Deutschland
String (0) image
String (10) fax 040-7555555
String (1) deleted 0
String (0) description
String (1) tx_addresssearch_coating_id
More information about the TYPO3-dev
mailing list