TYPO3 Core

Are you using MySQL as DB? If so, is it running in SQL strict mode?

Issue is probably related to #0006299, #0008474 and #0008542.

You are absolutly correct it's MySQL running in SQL strict mode.

I have used the default installation so I would never have thourght that it would be a problem as the requirements for Typo3 don't state any MySQL restrictions.

What would be the correct sql mode ?

Found it sql-mode="MYSQL40"

Unfortunately, it's currently not possible to run MySQL in strict mode. This would result in numerous error like that one you are reporting.

However, this is not intended. If you feel able to contribute and provide patches, this would be highly appreciated.

Added a patch which solves the issue.
Except from the BE, the same error was given when a page was cached.

The patch was created against r6127

The patch I added will turn off strict_mode for the sql-session. No other fixes to the sql-dialect necessary. Checked it on XAMP-installation, was the only way to make it work (I had no access to the servers settings).

This then even is a duplicate of 0008542

Feedback:

I downloaded and installed TYPO3 4.2.9 [typo3_src+dummy-4.2.9.zip] onto a local workstation already having Apache HTTPD 2.2.11, MySQL 5.0.51a, and PHP 5.2.8.

I logged in to the TYPO3 back end at [http://localhost/typo3/index.php] as an administrator. Once in, I clicked on the Page section of the Web module, then clicked on the globe appearing in the tree structure of the navigation area (the second column), then on "new" in the pop-up menu, then on the "Page (inside)" in the details view. In the box that appeared in the details view, I unchecked "hide page", entered "Home Page" as the Page Title, entered "Home" as the Subtitle, then clicked on the "save and close document" disk icon button. I received the [SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1'] error. I logged out of the TYPO3 back end, then stopped the Apache HTTPD service.

After researching the problem, I used the [10487_nostrict.patch] offered by Niels Fr?hling (0030995) to add a MySQL 'SET SESSION sql_mode=\'\'' instruction to the [t3lib/class.t3lib_db.php] file. I started the Apache HTTPD service, then repeated the procedure above to create a new page. This time, I did not receive the SQL error. Instead, the procedure was successful, and the new page appeared in the tree structure.

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

http://www.rengucha.com/phpInfo.php will show all config details.

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) {

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

This problem is also resistent in TYPO3 v4.3.1

But one thing:
Why don't you add the SQL-command into the var $GLOBALS['TYPO3_CONF_VARS']['SYS']['setDBinit'] which you can set in the install-tool ??

If you use this option you don't have to modify the TYPO3-core ...

For all coreFreaks ...
I've debugged this function and searched for a useful solution ... (Using TYPO3 v4.3.1)

MySQL-Default-Value is "0" ... This is only set in the MySQL!! I can't find it anywhere in the PHP-code (f.e. the $TCA[]).

The field we're talking about is "storage_pid" and if you look into the $TCA[] this field is defined as: { type:"group", internal_type: "db", allowed: "pages", size: 1, maxitems: 1, minitems: 0, show_thumbs: 1, witards: { suggest: { type: "suggest" } } }

Because the type of this fild is "group" we have to look at the function $t3lib_TCEmain->checkValue_group_select() (If you want to know why - look at $t3lib_TCEmain->checkValue_SW() )
In this function he checks the internal_type which is set to "db". Than he calles $t3lib_TCEmain->checkValue_group_select_processDBdata() to check which data is selected and he will return an empty array. So far all steps are correct - but after he has confirmed this call - he should check if the returned value is empty and check if this field has an default-value (this is also missing in the $TCA[]). I think if we'd use $unsetResult we could get troubles if we edit a page :)

• add a check after checkValue_group_select_processDBdata()
• add the default-value to the $TCA-array as it's set in the database (or use $unsetResult after the check if this don't cause troubles - I haven't tested ...)

A more complex way would be to read out the MySQL-default-value for this column an set this value if an empty array is given by the function checkValue_group_select_processDBdata()

Feedback

This problem persists in TYPO3 v4.4.4. Here is a short procedure checklist for TYPO3 administrators already logged in to the back end when this error occurs. (This procedure is based on Simon Schick's suggestion on 17.01.10 11:07.)
1. Go to "User tools>User settings". Click on the "Admin functions" tab. Click "Create Install Tool Enable File".
2. Go to "Admin tools>Install". Enter your password and click "login". Click "All Configuration".
3. Search the page for "setDBinit" (or scroll to [SYS][setDBinit]). You may see a line in the textarea saying, "SET NAMES utf8;". After that line, enter "SET SESSION sql_mode='';" without the first and last double quotes ("). Go to the bottom of the page, and click "Write to localconf.php". Continue, and confirm that your line has been entered by looking at the "setDBinit" section again.
4. Click "Logout from Install Tool". You are done. Return to the back end, and continue your task.

Patch set 2 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 3 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 5 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 6 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 7 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 8 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 9 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 10 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 11 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch set 12 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/19671

Patch was reverted again since, after some discussion, this was not the right place to add the additional check. Will need a follow-up. The general idea itself however was okay.