Bug #17834
closedIRRE does not take TBE_STYLES into account
0%
Description
When using IRRE the rules from TBE_STYLES formatting are interpreted completely wrong.
(issue imported from #M6798)
Files
Updated by Johannes K almost 17 years ago
The file without-irre.png show how it should look like according to TBE_STYLES['borderschemes']:
$TBE_STYLES['borderschemes']0 = array('','','','table-0 wrapperTable');
$TBE_STYLES['borderschemes']1 = array('','','','table-1 wrapperTable');
$TBE_STYLES['borderschemes']2 = array('','','','table-2 wrapperTable');
$TBE_STYLES['borderschemes']3 = array('','','','table-3 wrapperTable');
When I enable the inline fields everything is messed up (with-irre.png).
From the TCA
Without inline-fields:
"types" => array (
"0" => array("showitem" => "company;;;;1-1-1, street, country, location, phone, fairs;;;;3-3-3, logins, assignments, material;;;;2-2-2")
),
With inline-fields "contact" and "protocol":
"types" => array (
"0" => array("showitem" => "company;;;;1-1-1, street, country, location, phone, contact,fairs;;;;3-3-3, logins, assignments, material;;;;2-2-2,protocol;;;;")
),
I know it is a seldom used feature now, but it's nice for usability (if you choose other colors than me;-))
Updated by Johannes K almost 17 years ago
a short fix that works only for one level of nesting:
l. 976-980:
case 'inline':
$this->storeSchemes();
$item = $this->inline->getSingleField_typeInline($table,$field,$row,$PA);
$this->restoreSchemes();
break;
A real solution would be to use a stack in storeSchemes and restoreSchemes
patch will follow...
Updated by Oliver Hader over 16 years ago
The t3lib_TCEforms_inline::$inlineStructure stack could be used for this issue (but some situations still have to be changed when creating/importing new records via AJAX).
Could you please send me your extension for testing this issue?
You can send it via private mail to oliver [at] typo3 (dot) org - thanks!
Updated by Alexander Opitz over 11 years ago
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz about 11 years ago
- Status changed from Needs Feedback to Closed
No feedback for over 90 days.