Project

General

Profile

Actions

Bug #25025

closed

Links on graphical headers produce wrong/broken image

Added by Mikkel Olrik about 13 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2011-02-14
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.5
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When using a graphical generated header and adding a link to it, the resulting image (which should contain a graphic representation of the h1-header) gets generated with the beginning a-tag, and therefore shows nonsense instead.
If you make a header first - without a link - and save it, there's no problem. Even if you later add a link to it. I guess the cached image is used. Clearing all cache makes it break again, however, which, inthis cotext, makes sense.
The other way around (removing the link) does not solve the issue either - if a header is generated with a link from start. Not before you change the text significantly - to force gifbuilder to make a new image.

Here's the used TS:

#General header
GfxHeader = IMAGE
GfxHeader {
wrap = <h1>|</h1>
altText.field = header
file = GIFBUILDER
file {
XY = [10.w]+10,35
backColor = #FFFFFF
10 = TEXT
10.text.field =
10.text.current = 1
10.offset = 0,20
10.fontSize= 24
10.fontFile = fileadmin/templates/fonts/sansation/sansation_regular-webfont.ttf
10.fontColor = #660000
10.niceText = 1
10.antiAlias = 0

}
}

#Headers
lib.stdheader.stdWrap.typolink.parameter.field = header_link
lib.stdheader.10.setCurrent.htmlSpecialChars = 0

lib.stdheader.10.1 < GfxHeader

(issue imported from #M17570)


Files

Screen shot 2011-02-14 at 10.39.41.png (65.8 KB) Screen shot 2011-02-14 at 10.39.41.png Administrator Admin, 2011-02-14 10:48
Actions #1

Updated by Björn Pedersen about 13 years ago

I don't think it is a bug.
You should not use
10.text.current=1
, but use
10.text.field=header

Otherwise you instruct TYPO3 to use everything that is already process up to the point the image is rendered. And that includes the wrapped link in your case.

Actions #2

Updated by Mikkel Olrik about 13 years ago

Thanks - that solved the problem. I see your point.

I didn't actually make the TS myself - it was on a site, that was upgraded to 4.5 - and the old TS worked perfectly all right up untill 4.4.6 - so I thought it had to be a 4.5 bug.

But now I know how to correct it, so thanks again.

Actions #3

Updated by Björn Pedersen about 13 years ago

It could be, that the refactoring of tt_content changed the execution order in some points.

Actions #4

Updated by Georg Ringer about 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Closed
  • Target version deleted (0)

nothing to do here, no bug

Actions

Also available in: Atom PDF