[TYPO3-core] RFC: fix bug: 6561 imgMax and imgStart (IMGTEXT) not working properly

Helmut Hummel typo3 at rampenlicht.org
Wed Oct 31 10:51:50 CET 2007


Hi Ernesto,

Ernesto Baschny [cron IT] schrieb:
> 
> IMAGE_NUM was the register provided by original IMGTEXT and still used
> in content(default). This was kept to provide backwards compatible
> TypoScript.

OK, thanks, that's what I at least suspected.

> IMAGE_NUM_CURRENT was added in css_styled_content because IMAGE_NUM was
> kind of buggy. With http://bugs.typo3.org/view.php?id=3416 and v4.0.1
> the original IMAGE_NUM in IMGTEXT was "fixed", and after that both
> registers seems to have the same behaviour.

Your patch

http://lists.netfielders.de/pipermail/typo3-team-core/2006-June/004719.html

introduces IMAGE_NUM_CURRENT not only for csc but for the original
IMGTEXT, too. And there the old (wrong value) is kept for backwards
compatibility (that's the location in code I pointed to).

> To be consistent both registers should do the same, 

OK, I will update my patch then and add some comments.

> which also means set
> the correct index in the image list we are running through. 

Yes, and it went wrong with imgStart set to something <> 0

> This is used
> in TypoScript to get the matching caption, alt-text, links, etc, which
> need to know which image we are currently handling.

Thanks for explanation.

Regards Helmut


More information about the TYPO3-team-core mailing list