Issue Feature Rejected

#17131value:= function rendering sequence

Nikolas Hagelstein 03/19/07, 16:33 updated 02/19/22, 18:03

Description

Hi,
those value:= functions are applied before any data substitution (e.g. field/insertData) takes place.
Therefore something like this becomes impossible:

lib.box_headline = TEXT
lib.box_headline {
value={page:title}
insertData=1
value:=removeString(test)

}

(issue imported from #M5255)

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 11

  1. Michael Stucki commented 03/19/07, 16:55

    Right, and this is also explained in the documentation. It acts on TS parser level and doesn’t know about page fields, rootline, etc.

    You’ll need to solve your problem differently, we cannot change this.

  2. Nikolas Hagelstein commented 03/19/07, 17:21

    Right, therefor i marked it as feature request ;)

  3. Michael Stucki commented 03/19/07, 17:46

    Aha. But then the description about the “:=” syntax is misleading. Well yes, there seems to be no such feature right now. I suggest you try to implement this using a new stdWrap property.

    - michael

  4. Alexander Opitz commented and changed category status Accepted Needs Feedback target version 05/05/13, 10:25

    As this report is very old, is the handling in newer TYPO3 CMS Versions (like 6.0/6.1) more like you expect it?

  5. Chris topher commented 05/05/13, 12:44

    Alexander Opitz wrote:
    > is the handling in newer TYPO3 CMS Versions more like you expect it?

    I don’t think so. How would you do that with a current version? I don’t know of a way…

  6. Alexander Opitz changed status Needs Feedback New 05/14/13, 10:35

  7. Mathias Schreiber changed target version 01/15/15, 17:39

  8. Riccardo De Contardi changed target version 02/23/17, 14:50

  9. Susanne Moog changed category 10/29/17, 16:18

  10. Susanne Moog changed target version 01/28/18, 14:29

  11. Christian Kuhn commented and changed status New Rejected 02/19/22, 18:03

    hey. i hope it’s ok to set this ancient feature request to ‘rejected’ for now.