[TYPO3-core] Reminder: "type" field for flexforms

[Bernhard Kraft]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dmitry Dulepov wrote:
> Hi!
> 
> (Responding to Michael's request for reminders)
> 
> There were no responses (except one from Bernhard) about one feature
> (see link below). I believe it is important for flexforms and extensions
> and much better than using "requestUpdate" in this case. It was asked a
> number of times in mailing lists. Change is simple, only two lines in
> TCEforms but gives much more power to flexforms and ensures that two
> extensions will not have conflicts (unlike "requestUpdate").

Again I must say I don't know why to introduce a new property. Look at the
following piece of code from an application of me:

  function __store_RequestUpdate(&$tca, $rQU) {
    $tca['ctrl']['requestUpdate'] .= ($tca['ctrl']['requestUpdate']?',':'').implode(',', $rQU);
  }

It just adds some fields of a Flexform ($rQU) into the "normal" requestUpdate field.

Oh. I think I just get it now. What you mean by "different extensions" have conflicts
is that they will conflict if they have fields with the same name. You set requestUpdate for
one field of the one flexform and also get it for the same named field of the other extension.

I see ...

+1

:)
don't forget to send documentation changes !


greets,
Bernhard
- --
- ----------------------------------------------------------------------
"Freiheit ist immer auch die Freiheit des Andersdenkenden"
Rosa Luxemburg, 1871 - 1919
- ----------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEDWQ7Il4dkVkDMFkRAr7mAJ9kKdVszmBKPoYf2OqaNsspKxxoWACdHRXh
mFpcMKSpueEaP/yPB2fSL0s=
=QPCo
-----END PGP SIGNATURE-----