Support for v12 LTS planned?

[tomkyle]

Are there any plans to support Typo3 12.4 LTS?

Thanks for your work on this extension! A Typo3 newbie

[jweiland]

Yes, there will be an update for version 12.4, but we can't give you a time frame yet. Since we have to update 60+ extensions for each TYPO3 version, this takes some time. If you need an updated version urgently you may want to consider sponsoring the update.

Am Do., 4. Mai 2023 um 18:27 Uhr schrieb Carsten Witt < @.***>:

Are there any plans to support Typo3 12.4 LTS?

Thanks for your work on this extension! A Typo3 newbie

— Reply to this email directly, view it on GitHub https://github.com/jweiland-net/replacer/issues/20, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA3RNJTTVCFFNQSUWNNO5ATXEPKIXANCNFSM6AAAAAAXWAJDDU . You are receiving this because you are subscribed to this thread.Message ID: @.***>

--

Tipp: Datenschutzerklärung für Webseiten automatisch erzeugen und aktualisieren lassen: https://jweiland.net/typo3/codebeispiele/allgemeines/automatische-datenschutzerklaerung.html https://jweiland.net/typo3/codebeispiele/allgemeines/automatische-datenschutzerklaerung.html

TYPO3 Hosting, Schulungen, Projekte Info + Support: 0800 - 8976326 (0800

• TYPO3CM)

jweiland.net https://jweiland.net - Jochen Weiland Echterdinger Str. 57 70794 Filderstadt USt-ID: DE226345594

[Denneee]

Any new informations for a possible TYPO3 v12 Release?

[sfroemkenjw]

We are just working on it: https://github.com/jweiland-net/replacer/tree/typo3_12_compatibility

[xerc]

@sfroemkenjw "from version 3. We made the individual processing of search replacement key" PLEASE re-integrate the global enable_regex or check for /(.).+\1[a-z]*/i

[sfroemkenjw]

Hello @xerc

it does not make sense for us to have that configuration globally as it reduces the possibility for individual configuration. Why you should replace apple with banana with preg_replace? Such simple values should be replaced with str_replace. We have discussed to add a further setting to deactivate regExp again individually, but it does not get enough votes.

Stefan

[xerc]

@sfroemkenjw ; all my rules are regex therefore it would be convenient to enable globaly (inkl. no need for other checks)

[sfroemkenjw]

Good Morning @xerc

of cause, we are speaking here in a range of microseconds, but using preg_replace is 28% slower than str_replace and as more complex the RegExp is, it's up to 40% slower. PhpStorm plugin prefers using str_replace instead of preg_replace, if it detects simple word replacements. In TYPO3 core the redirect records will be grouped by RegExp to execute them at last, to prevent interrupting the fast redirects. And, of cause, you have to activate RegExp for each redirect individually.

So, for sure, you now have to adopt all of your settings. But now we prefer the option to speed up our extension a little bit and give other users much more flexible.