[TYPO3-dev] set_no_cache is bad. What's next?

Elmar HInz elmar.hinz at team.MINUS.red.DOT.net
Sat Mar 31 21:04:06 CEST 2007


> 
> what do you think about making a new function in pi_base, like
> 
> function 
> pi_makeLink($str,$urlParameters=array(),$cache=0,$additionalConf=array(),$altPageId=0) 
> {...}
> function 
> pi_makeLink_url($urlParameters=array(),$cache=0,$additionalConf=array(),$altPageId=0) 
> {...}
> 
> so we have 1(2) new functions as typolink-Wrapper, keep a simple handling 
> and be compatible to old versions.
> $additionalConf would be overriding conf for typolink.
> 
> vg  Steffen


Hi Masi, Steffen, Michael,

that's the direction. I suggest a class that extends tslib_pibase,
so that backward compatibility is fully given.

a) It would replace all cryptical stuff with human readable aliases. 

b) It would reduce the amount of link functions you need to learn.

c) IMPORTANT: Link functions should work without the
   $this->pi_USER_INT_obj value. That would simplify the learning
   of "proper caching" a lot, because that is the confusing point to
   understand.

d) $this->pi_USER_INT_obj becomes obsolete by this. The link functions
   that still use it should best be overwritten with an empty stub.

Regards

Elmar











More information about the TYPO3-dev mailing list