Issue Bug Closed

#21352Not able to save any content changes

Renga 10/24/09, 05:38 updated 05/11/10, 12:32

Description

I moved my sites from 3.8 on Windows to 4.2.9 on ubuntu hardy heron 8.04

Issues
1.0 All sites are showing up but for one. It is just showing blank white screen with “Done” at the bottom. www.nittalum.us

2.0 I am not able to change content in BE. When I change and save, the last section where I edit becomes white. When I again click on Page and page it has the old data. Nothing is saved. Suspecting the above issue I tried the patch as below

2.1 > sudo patch -b -f -p 1 -i /home/suresh/typo3/10487_nostrict.patch -o ./class.t3lib_db.php

(Stripping trailing CRs from patch.)
patching file class.t3lib_db.php
Hunk #1 FAILED at 963.

Please help

class.t3lib_db.php.rej has the following

***************
*** 963,968 ****
if (!$this->link) {
t3lib_div::sysLog(‘Could not connect to MySQL server ‘.$TYPO3_db_host.’ with user ‘.$TYPO3_db_username.’: ‘.$error_msg,‘Core’,4);
} else {
$setDBinit = t3lib_div::trimExplode(chr(10), $GLOBALS[‘TYPO3_CONF_VARS’][‘SYS’][‘setDBinit’],TRUE);
foreach ($setDBinit as $v) {
if (mysql_query($v, $this->link) = FALSE) {
--- 963,969 ----
if (!$this->link) {
t3lib_div::sysLog('Could not connect to MySQL server '.$TYPO3_db_host.' with user '.$TYPO3_db_username.': '.$error_msg,'Core',4);
} else {
+ mysql_query('SET SESSION sql_mode=\'\'', $this->link);
$setDBinit = t3lib_div::trimExplode(chr(10), $GLOBALS['TYPO3_CONF_VARS']['SYS']['setDBinit'],TRUE);
foreach ($setDBinit as $v) {
if (mysql_query($v, $this->link) = FALSE) {

3.0 I just went into class.t3lib_db.php and added the following line
mysql_query(‘SET SESSION sql_mode=\’\’‘, $this->link);

restarted Apache and mySQL. Still not working.

Then I saw the following in the Apache log

PHP Fatal error: Cannot re-assign $this in /var/www/web1/quickstart/typo3conf/ext/static_info_tables/class.tx_staticinfotables_syslanguage.php on line 41

Please HEEEEEEEEEEEEEEELP

(issue imported from #M12332)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.