TYPO3 Core

Anyone who can reproduce this?

"$GLOBALS['TSFE']->fe_user->setKey('user','sessionfachgebiete',$fachgebiet);" and "$fachgebiet is an array."
I guess setKey only accepts a string. Please try to serialize $fachgebiet:
$GLOBALS['TSFE']->fe_user->setKey(
'user',
'sessionfachgebiete',
serialize($fachgebiet)
);

I tried your code, but still warnings. I also tried to store a pure string "hello" - without success. The code worked with my old typo3-installation on another server - without any warnings. And: the code still works in 4.0.4. - but with the mentioned warnings.

strange: After I tried the your code - and restored it to my original code after this, I now have 6 warnings:

Warning: mysql_real_escape_string(): 28 is not a valid MySQL-Link resource in /srv/www/vhosts/mentorado-expert.de/httpdocs/typo3_src-4.0.4/t3lib/class.t3lib_db.php on line 555

Warning: mysql_query(): 28 is not a valid MySQL-Link resource in /srv/www/vhosts/mentorado-expert.de/httpdocs/typo3_src-4.0.4/t3lib/class.t3lib_db.php on line 207

Warning: mysql_real_escape_string(): 28 is not a valid MySQL-Link resource in /srv/www/vhosts/mentorado-expert.de/httpdocs/typo3_src-4.0.4/t3lib/class.t3lib_db.php on line 555

Warning: mysql_real_escape_string(): 28 is not a valid MySQL-Link resource in /srv/www/vhosts/mentorado-expert.de/httpdocs/typo3_src-4.0.4/t3lib/class.t3lib_db.php on line 555

Warning: mysql_real_escape_string(): 28 is not a valid MySQL-Link resource in /srv/www/vhosts/mentorado-expert.de/httpdocs/typo3_src-4.0.4/t3lib/class.t3lib_db.php on line 555

Warning: mysql_query(): 28 is not a valid MySQL-Link resource in /srv/www/vhosts/mentorado-expert.de/httpdocs/typo3_src-4.0.4/t3lib/class.t3lib_db.php on line 176

Don't know why...?

Hm, this is strange. It looks like your database connection gets lost or a new connection is created and the old DB is thus invalid. Do you perform selects, connects to a different MySQL database than the TYPO3 DB?

Could you additionally turn on the MySQL debug in the Install Tool (All config, sqlDebug) and tell us the complete SQL queries? Thanks!

No, I only perform selects to the Typo3-DB. I do this with "normal" PHP-commands - not with the Typo3-DB-functions; and not in an extension but in a "normal" (external) PHP-script included as a content element (using Extension "page_php_content"). I turned sqlDebug "on" in install-tool, but no further warnings/errors are displayed. Probably because I use "page_php_content" with normal PHP-MySQL-commands?

I'm using serveral scripts like this.
At the beginning the DB is opened with $db=mysql_connect($config["datenbank"],$config["benutzer"],$config["passwort"]);
at the end it's closed with mysql_close($db);
> No warnings as long as I do not use "$GLOBALS['TSFE']->fe_user->setKey('ses','sessionfachgebiete',$fachgebiet);" in the script.

Now I discovered the following:
a) The same PHP-script in my new and in my old T3-installation
b) Using "$GLOBALS['TSFE']->fe_user->setKey('ses','sessionfachgebiete',$fachgebiet);" togehter with "mysql_close($db)" at the end of the script in the OLD installation: no warnings.
c) Using "$GLOBALS['TSFE']->fe_user->setKey('ses','sessionfachgebiete',$fachgebiet);" togehter with "mysql_close($db)" at the end of the script in the NEW installation: the mentioned warnings.
d) Commenting out "mysql_close($db)" in the NEW installation: no warnings any more.

The SQL debug information isn't shown since you do not use $GLOBALS['TYPO3_DB']. So, your script closes the TYPO3 database connection and after that mysql_close($db) the regular TYPO3 scripts are without a connection.

If it is necessary to use mysql_query directly you can use mysql_query($sqlQuery, $GLOBALS['TYPO3_DB']->link). Furthermore you can then remove the additional mysql_connect() and mysql_close() calls.
But it would be better to use $GLOBALS['TYPO3_DB']->exec_SELECTquery(...) to perform e.g. SELECT queries instead of using mysql_query(...) directly.

Result: Your external script produces the error thus it is not concerning the TYPO3 Core.

Ok, thank you very much! I will change the code using "$GLOBALS['TYPO3_DB']" to solve the problem.

What I still don't unterstand: why do the warnings only appear in my new T3-installation? And why do all my other scripts without "setKey" do not produce this warnings (I close the DB at the end of every script)?
Whatever... ;-)

Resolved, no change required as requested by reporter due to incorrect direct mysql calls.