[Typo3-dev] RFC (core patch): flexform field path
Bernhard Kraft
kraftb at kraftb.at
Sat Oct 1 15:17:12 CEST 2005
Hallo,
I run into a obvious "bug" or more a "non-feature" of T3 Flexforms.
If you use an <itemsProcFunc> for generating the elements of an
<type>select</type> field and those items shall depend on the value of
another field in the flexform then you get the problem that the
<itemsProcFunc> doesn't know which flexform-field it renders actually.
Of course you have the name of the field - but if you use a flexform
with sections (variable number of sub-elements) then you can't know in
which section you are actually.
I made two patches to correct this. The first one is simpler but you
will have to parse the passed "formPrefix" string in your itemsProcFunc
to find out the path of the field in the flexform.
The second one keeps track of the actual path in the flexform as an
array and uses this as argument to the itemsProcFunc.
The pathes are here:
1:
http://www.think-open.org/kraftb/01_flexField_path_patch.diff
2:
http://www.think-open.org/kraftb/02_flexField_path_patch.diff
Could somebody please take a look at those two and tell me which one is
more safe to implement into the core concerning downwards compatiblility
etc.
greets,
Bernhard
More information about the TYPO3-dev
mailing list