Bug #17937
closed
Cannot create more than 9 related records in IRRE
0%
Description
On my new extension, IRRE shows a strange behaviour:
I can only create up to 9 related items in the sub-sub-relation.
Example:
Table.
IRRE Element A
IRRE Subelement 1
IRRE Subelement 2
IRRE Subelement 3
IRRE Subelement 4
IRRE Subelement 5
IRRE Subelement 6
IRRE Element B
IRRE Subelement 7
IRRE Subelement 8
IRRE Subelement 9
No more IRRE Subelements are possible. If I delete one of them, I can create
a new one.
My TCA:
for "Table":
"tx_powermail_fieldsets" => Array(
"label" =>
"LLL:EXT:powermail/locallang_db.xml:tx_powermail_forms.fieldsets",
"config" => Array (
"type" => "inline",
"foreign_table" => "tx_powermail_fieldsets",
"foreign_field" => "form",
'foreign_sortby' => 'sorting',
'foreign_label' => 'title',
'maxitems' => 1000,
'appearance' => Array(
'collapseAll' => 1,
'expandSingle' => 1,
'useSortable' => 1,
'newRecordLinkAddTitle' => 1,
'newRecordLinkPosition' => 'both',
),
)
),for IRRE Element A:
"fields" => Array(
"label" =>
"LLL:EXT:powermail/locallang_db.xml:tx_powermail_fieldsets.fields",
"config" => Array (
"type" => "inline",
"foreign_table" => "tx_powermail_fields",
"foreign_field" => "fieldset",
"maxitems" => 1000,
'appearance' => Array(
'collapseAll' => 1,
'expandSingle' => 1,
'useSortable' => 1,
'newRecordLinkAddTitle' => 1,
'newRecordLinkPosition' => 'both',
),
)
)Any suggestions?
(issue imported from #M7003)
Files
Updated by Oliver Hader over 16 years ago
The attached extension uses data2cal which doesn't work correctly with IRRE. This might be (part of) the problem. Furthermore it seems that some fields are missing in ext_tables.sql because I got a lot of SQL debug errors...
Updated by Mischa over 16 years ago
New ext_tables.sql uploaded. But error still remains. Will test disabling date2cal.
Updated by Mischa over 16 years ago
I've registered a 2 new strange behaviours:
1. If a mandantory field is set in an IRRE-Set and it's not filled out you cannot save the whole Form when you delete this IRRE-Set.
2. If I try to add a 10th IRRE-Set in 2nd level, I'm not able to save or close the form anymore.
Updated by Oliver Hader over 16 years ago
What is the exact TYPO3 version you're using?
Updated by Mischa over 16 years ago
It was not working on 4.1.3, 4.1.4 and 4.1.5
Updated by Mischa over 16 years ago
Even turning off date2cal doesn't solve this problem.
We additionally changed the way of fetching the XML for flexform. First we created a temporary xml-file whenever needed. Now we have several different files. But this didn't change anything except increasing speed of the backend. ;-)
Will it help to get access to our TYPO3 Backend?
Updated by Mischa over 16 years ago
Sorry for posting so much, but I think this will help. I try to find solutions as well. So I followed the Relationships of this thread and found a patch. But this - unfortunately - doesn't work in my case.
Updated by Mischa over 16 years ago
I installed this plugin on a bandnew version of TYPO3 (4.1.5 and 4.1.2) without any other ext. but both are not working.
Is it possible that my php-version or MySQL cause the problem?
PHP 5.2.4
MySQL: 5.0.45
Updated by Mischa over 16 years ago
I think I could point out the problem.
One of my fields in Level 3 is a flex-field. In my oppinion, either TYPO3 get confused with the sum of flexforms to be built or my server can't handle the amount of flexforms.
After turning off the flex-field, everything worked properly.
Updated by Oliver Hader over 16 years ago
Hm. I investigated in a similar problem where a maximum of 10 items could be created. But there were no flexforms at all. After searching for a while, the "error" was found in a Suhosin add-on for PHP (http://www.hardened-php.net/suhosin/) which seemed to block parts of the POST-data sent to typo3/alt_doc.php.
Disabling Suhosin also caused the bug to disappear. Please tell me what you experienced about that.
Updated by Oliver Hader over 16 years ago
Mischa told me via private mail, that this is working now on his system and that also Suhosin installed.
Updated by Oliver Hader over 16 years ago
Since this issue is not related to the TYPO3 Core but more to strict and hardened PHP versions on some systems, I'm closing this issue. Feel free to reopen if you think, that the TYPO3 Core has to be changed in any way though.