Project

General

Profile

Actions

Bug #19885

closed

Adding more then x IRRE child-records causes system logout

Added by Marcus Biesioroff almost 16 years ago. Updated about 6 years ago.

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

0%

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

Description

When trying to add more than 3 IRRE child-records, system logouts at save parent record operation.

Was testing with T3BLOG and rgnewsce extensions, in both cases with identical simptoms.

Reproducibility random/always:
I have two implemantations of TYPO3 system with very similar configuration (working - A / non-working - B) at different hosts, before bug reporting spent few hours to complete comparision of their configs (also with PHP settings) and make sure that they are almost identical for now. The only major difference between them is PHP version - problematic implementation (B) works on PHP5.2.0-8 and working system (A) uses 5.2.4-0.

Today I updated both TYPO3 systems to 4.2.4 with no change in IRRE matter.
(issue imported from #M10223)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #17937: Cannot create more than 9 related records in IRREClosedOliver Hader2007-12-18

Actions
Actions #1

Updated by Oliver Hader almost 16 years ago

Do you use some kind of "hardened PHP" like suhosin or something the like?
If so, please have a look into the log file or enable the logging.
In some cases suhosin stops IRRE from working when too many POST data gets transferred or argument names get too long...

Actions #2

Updated by Marcus Biesioroff almost 16 years ago

HA! That's the point!!! Rising the limits of :
suhosin.post.max_*
and
suhosin.request.max_*
directives, solved the problem for me :)

Thank you Oliver for advice.

Actions #3

Updated by Christian Kuhn almost 16 years ago

Thanks for feedback, Marcus.

Issue resolved with "no change required".

Actions #4

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF