[TYPO3-core] RFC: #2119: Clean-up in mailform code: more TypoScript flexibility

Sebastian Kurfuerst sebastian at garbage-group.de
Fri Dec 30 12:53:10 CET 2005


This is a CVS patch request.

Most of the stuff below is taken from
http://bugs.typo3.org/view.php?id=2119

Branches: 4.0

Type: Bugfix/Cleanup/new feature

Description:
This relates to the changes applied by 0001369. This new patch enhances
the features that have already been integrated into 4.0beta1 with the
following:

The admin now can configure all tags from a mailform via TypoScript.
There are now just very few tags hardcoded into PHP, mainly the tags
that represent the fields for the FORM. The TypoScript code has been
reorganized to be easier to understand and to adapt. The static
TypoScript that comes with css_styled_content has been adapted for this.

      * no more "accessibility=1" setting. All "accessible" settings are
        done just by configuring the tags and parameters in TypoScript
        itself. The default included TypoScript is now accessible
        out-of-the-box.
      * all settings that are related to a specific element type (e.g.
        RADIO, SELECT, etc) are now organized into respective setting
        groups. See the new default static TypoScript to see what it
        means. But all "old" settings are still valid for backwards
        compatibility.
      * the hardcoded "<label>" in accessibility-mode is now part of
        the TypoScript setup (labelWrap.wrap with ###ID### that gets
        replaced with appropriate ID). The user can override this per
        element-type (e.g. for LABEL type there is no <label>|
        </label> wrapping.
      * labelWrap.wrap and REQ.labelWrap.wrap can now both be overridden
        in a specific element-type

Specific for RADIO-element:

      * the user is now free to layout the radio-items appearance (used
        to be hardcoded to "[radio][label][br/]")
      * static TypoScript used to have a "testform_radio" id for all
        radio-fieldsets, this was not only wrong, but also invalid if
        you have more than one radio-fieldset. Now the ID gets set
        correctly ("###ID###") according to the field-name.
      * also the hardcoded "<legend>" is now part of the TypoScript
        setup, so it can be removed/changed/etc.

New settings (where XXX is the name of the element-type in UPPER-case):

      * RADIO.item.layout with markers ###RADIO### (the radio-button)
        and ###RADIO_LABEL### (the corresponding label, stdWrapped in
        RADIO.item.labelWrap)
      * RADIO.item.addParams with marker ###RADIO_ID### (the id of this
        specific item)
      * RADIO.item.labelWrap with marker ###RADIO_ID### (the id of this
        specific item)
      * XXX.addParams with marker ###ID### (the id of this field). This
        are attributes that will get added to the tag (input, select,
        textarea, ...) for this field in the FORM.
      * XXX.labelWrap.wrap with marker ###ID### (the id of this field)
      * XXX.REQ.labelWrap.wrap with marker ###ID### (the id of this
        field)

Obsolete (but still supported) settings and new equivalents:

params.xxx = XXX.addParams
radioWrap = RADIO.item.labelWrap
accessibility=1 = all accessible stuff can now be done directly in
TypoScript


Thanks to Ernesto who provided this patch!

Greets, Sebastian

-- 
Sebastian Kurfuerst
http://garbage-group.de/kontakt.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bug_2119_2.patch
Type: text/x-patch
Size: 14745 bytes
Desc: not available
Url : http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20051230/07c15495/attachment.bin 


More information about the TYPO3-team-core mailing list