Project

General

Profile

Actions

Bug #19129

closed

Modul List T3 Backend

Added by Maik Ernemann almost 16 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2008-07-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.2
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hello TYPO3 Community!

An Error occurred by klick on modul list in the typo3 backend. I have changed further lines. I hope its helpfully. I think the problem stems from bad data, which is stored on this site.

Error: Warning: mysql_num_rows(): supplied argument is not a valid MySQL result resource in /usr/local/apache/htdocs/typo3_src-4.2.1/t3lib/class.t3lib_db.php on line 795
typo3_src-4.2.1/t3lib/class.t3lib_db.php - Line 795:
Current:
return mysql_num_rows($res);

New:
if ($res) return mysql_num_rows($res);

Error: Warning: Invalid argument supplied for foreach() in /usr/local/apache/htdocs/typo3_src-4.2.1/typo3/class.db_list.inc on line 695
typo3_src-4.2.1/typo3/class.db_list.inc - Line 694:
Current:
foreach($TCA[$table]['columns'] as $fN => $fieldValue) {
if ($dontCheckUser ||
((!$fieldValue['exclude'] || $BE_USER->check('non_exclude_fields',$table.':'.$fN)) && $fieldValue['config']['type']!='passthrough')) {
$fieldListArr[]=$fN;
}
}

New:
if (is_array($TCA[$table]['columns'])) {
foreach($TCA[$table]['columns'] as $fN => $fieldValue) {
if ($dontCheckUser ||
((!$fieldValue['exclude'] || $BE_USER->check('non_exclude_fields',$table.':'.$fN)) && $fieldValue['config']['type']!='passthrough')) {
$fieldListArr[]=$fN;
}
}
}

For Pach see above!

(issue imported from #M9009)

Actions #1

Updated by Tino Tischer over 15 years ago

This error happens when you take a fresh Typo3 4.3.2 (src + dummy) and install the Direct Mail (direct_mail) Extension Version 2.6.0

Everytime I used the List module I recieved this error.

Actions #2

Updated by Jacco Lammers over 15 years ago

I can confirm on the same. Tested the fix: works.

Typo3 4.2.1
direct_mail 2.6.0

Actions #3

Updated by Christian Kuhn over 15 years ago

This should be analyzed further. Why and how is this error triggered by direct_mail? At first glance this looks like a faulty setup in the extension to me, and the t3lib_db error is just the symptom.

Actions #4

Updated by Dmitry Dulepov over 15 years ago

It means that tables were not created properly. The fix must not be applied as described in the bug report. Please, contact the author of the extension to fix the problem. The issue is closed.

Actions #5

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF