[TYPO3-dev] WARNING!?? tslib_patcher, pp_chashchecker

Popy popy.dev at gmail.com
Thu Aug 23 10:21:05 CEST 2007


2007/8/23, Dmitry Dulepov [typo3] <dmitry at typo3.org>:
>
> Hi!
>
> Popy wrote:
> > And what about http://bugs.typo3.org/view.php?id=5531,
> > http://bugs.typo3.org/view.php?id=5161 and
> > http://bugs.typo3.org/view.php?id=5117 ? The bug is reported since 5
> monthes
> > and nothing is done in the source (even in latest developpement
> revision)
>
> Why do you expect these bugs to have higher priority than others?

Maybe because the patch is done, tested, works, and because it is a big
typo3 feature ?


> Maybe because for now this is the only way to have valid cHashes in url ?
>
> No. Extension can do it easily just by saying that it wants cHash to any
> of tslib_pibase link function. It is all already built in to core.

Read the explanations please. typolink function build a wrong cHash because
of a wrong order with linkVars, and another bug if there's no
"additionalParams"

> Is there a better way ? You know the tslib_patcher author, and maybe you
> > know my extensions too, so you should know that we always look for the
> > better solution.
>
> Sometimes it helps contacting one of core developers and asking him to
> look to that BT entry. If developer has time, of course... But releasing
> an extension with 16 XCLASSes is a bad thing.

Did you really count the number of XCLASS in tslib_patcher ?



-- 
Popy

Vulnerant omnes, ultima necat.

http://popy.sytes.net




More information about the TYPO3-dev mailing list