Feature #19347: Integrate string replacement to stdWrap - TYPO3 Core - TYPO3 Forge

Actions

Copy link

Feature #19347

closed

Integrate string replacement to stdWrap

Added by Oliver Hader about 16 years ago. Updated over 11 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Oliver Hader

Category:

TypoScript

Target version:

Start date:

2008-09-17

Due date:

% Done:

100%

Estimated time:

PHP Version:

5.2

Tags:

Complexity:

Sprint Focus:

Description

With stdWrap it's not possible yet to do (ordered) string replacements for processing content data.

On introducing a new stdWrap property "replacement" that takes a ordered list of replacement definitions multiple manipulations could be executed the same time. Additionally it regular expressions can be used if required.

<b>TypoScript example:</b>

20 = TEXT
20 {
  value = There_is_a_cat,_a_dog_and_a_tiger_in_da_hood!_Yeah!
  stdWrap.replacement {
    10 {
      search = _
      replace.char = 32
    }
    20 {
      search = in da hood
      replace = around the block
    }
    30 {
      search = #a (Cat|Dog|Tiger)#i
      replace = an animal
      useRegExp = 1
    }
  }
}

The indexes 10, 20, 30 are just for setting an order on the execution of the replacement. Each subkey "search", "replace" and "useRegExp" has again stdWrap functionality.

(issue imported from #M9373)

Files

Download all files

0009373.patch (3.51 KB) 0009373.patch		Administrator Admin, 2009-05-28 17:49
0009373_typoscript.txt (333 Bytes) 0009373_typoscript.txt		Administrator Admin, 2009-05-28 17:49
0009373_documentation.txt (1.45 KB) 0009373_documentation.txt		Administrator Admin, 2009-05-28 18:13

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Steffen Kamper about 16 years ago

Great!

where is the patch? :D

Actions

Copy link

Updated by Oliver Hader over 15 years ago

One thing should possibly be disabled: The disposal of the "e" (PREG_REPLACE_EVAL) modifiert to evaluate the replacement with PHP...

Actions

Copy link

Updated by Michael Klapper over 15 years ago

Great!

Actions

Copy link

Updated by over 14 years ago

Any news about that? It's pending in core list for 10 months. Discussion seems to have ended without a decision.

Actions

Copy link

Updated by Dmitry Dulepov over 13 years ago

Category deleted (~~Communication~~)

I would prefer a different, simpler, syntax:

10 = TEXT
10.value = Hello, World!
10.replace = "World", "TYPO3"

10.replace = /world/i, "TYPO3"

Actions

Copy link

Updated by Xavier Perseguers over 13 years ago

Target version changed from 4.6.0 to 4.6.0-beta1

Actions

Copy link

Updated by Mr. Hudson over 13 years ago

Patch set 1 of change I05a067e06cf6d6d664a178c6cf91e17178d691a8 has been pushed to the review server.
It is available at http://review.typo3.org/3855

Actions

Copy link

Updated by Stefan Neufeind over 13 years ago

Dmitry, I agree that "simplicity" would be nice. But imho a clear separation of search/replace makes it easier to handle. Also this allows us to add additional features/settings later. One of the things that came to my mind (not yet done) would be a "limit"-option.

Actions

Copy link