Project

General

Profile

Actions

Bug #21974

closed

SQL error if i want to create a page by using "Page (inside)"

Added by Simon Schick over 14 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2010-01-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

If I create a page by using the "Page (inside)" and click on save or select another page-type I allways get the error-message:

2: SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW4b522b434065e)

I don't know where exactly this bug is in the code because I don't have a backtrace :)

(issue imported from #M13264)


Related issues 1 (0 open1 closed)

Is duplicate of TYPO3 Core - Bug #20052: SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW499d21cdec168)Rejected2009-02-19

Actions
Actions #1

Updated by Simon Schick over 14 years ago

Hey, I've got the same problem if I want to create a page by using "Page (after)"

2: SQL error: 'Incorrect integer value: '' for column 'storage_pid' at row 1' (pages:NEW4b522cbd215bf)

Only the method "Page (select position)" is working ...

p.s. If it's important I'm developing on Windows7 with the ZEND-Server Community Edition. The browser i've tested with is FireFox 3.5.7

Actions #2

Updated by Simon Schick over 14 years ago

Now I tried to create a specific content-type and this didn't work also ...

hey - If I'm the only one with this problem - let me know ...

2: SQL error: 'Incorrect integer value: '' for column 'parent' at row 1' (tx_templavoila_tmplobj:NEW4b522e74f1544)

I can't create an TemplaVoilà-TemplateObject - but I can create an TemplaVoilà-DataStructure ...

Actions #3

Updated by Christian Kuhn over 14 years ago

Resolved as duplicate of #20052.

@Simon, this is a problem with mysql running in STRICT mode, please have a look at the duplicate issue.

Actions #4

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF