Project

General

Profile

Actions

Bug #19532

closed

Introduce substituteMarkerArrayNotCached

Added by Steffen Kamper about 16 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2008-10-30
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

As it's long discussed here is a non-cached version of substituteMarkerArrayCached with same syntax but without caching

(issue imported from #M9689)


Files

substituteMarkerArrayNotCached.diff (2.8 KB) substituteMarkerArrayNotCached.diff Administrator Admin, 2008-10-30 13:54
Actions #1

Updated by Ingo Renner about 16 years ago

dude, we already have substituteMarkerArray() and substituteSubpartArray() !

-1 for now

Actions #2

Updated by Steffen Kamper about 16 years ago

but not for marker, subpart and linkparts.

I don't make this for no reasons, look at cal: because of flooding DB with endless entries of the markers there is now a simular function with same usage and no cache!

Actions #3

Updated by Ingo Renner about 16 years ago

so where's the difference between a combination of the two existing functions and your new function? Maybe this can convince me then ;)

BTW: it should be added to t3lib_parsehtml instead of tslib_content, tslib_content should just have a wrapper

Actions #4

Updated by Steffen Kamper about 16 years ago

as you can see my function also use substituteMarkerArray, so it's a kind of wrapper function.
There was a discussion to add a parameter to the substituteMarkerArrayCached to prevent caching, but this sounds like nonsense: calling substituteMarkerArrayCached and say "no cache", so the new function is an equivalent to substituteMarkerArrayCached using same parameters.
To use it you can change the call from substituteMarkerArrayCached to substituteMarkerArrayNotCached without changing more.

I'm ok with moving it to t3lib_parsehtml for usage in BE too and leave a wrapper in tslib_content.

Actions #5

Updated by Alexander Opitz over 11 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)

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

Actions #6

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed
  • Is Regression set to No

No feedback for over 90 days.

Actions

Also available in: Atom PDF