[TYPO3-dam] New extension "damlightbox" - sounds interessting?

Dr. Ronald P. Steiner Ronald.Steiner at googlemail.com
Tue Mar 25 13:48:42 CET 2008


Hi Torsten,

thank you for your reply.

Your reply already solved my first problem:
I uninstalled most other extensions and the problem of the missing 
header data is solved. So possibly some other extension causes the problem.

Regarding the second problem, that in place where the image should be 
there is only a white field I could not find a solution now. The html of 
the lightbox is empty between the <body>-tag.

So the error must be somewhere before the image is processed?

greetings

Ron


Torsten Schrade schrieb:
> Hi Ron,
> 
>> 1) The extension kind of overwrites the header data. So title, 
>> stylesheets, is removed after including the pmkslimbox-damlightbox 
>> template.
> 
> Strange - the pmkslimbox-damlightbox TS only adds to page.headerData at 
> .1231 (some embedded styles) and .1232 (some custom .js). It should not 
> override anything whatsoever... The two includes are necessary after 
> .1230 which gets added by pmkslimbox. For a start, check the following 
> four things:
> 
> 1) Is the damlightbox / pmkslimbox-damlightbox TS included AFTER 
> pmkslimbox and css_styled_content?
> 
> 2) Check your page.headerData with and without pmkslimbox-damlightbox 
> for differences. Where is your CSS (page.headerData, page.includeCSS) 
> normaly included?
> 
> 3) Check your config object with and without the TS. For the <title> to 
> be dropped you would have to set this at config.noPageTitle but 
> damlightbox doesn't touch this.
> 
> 4) Are there any other extensions installed that may modify 
> CSS/title/tt_content.image? Maybe there's a conflict...
> 
>> 2) The lightbox opens with meta information and correct sice, but in 
>> place where the photo should be it's just empty.
>> You got any idea for the reason?
> 
> This almost certainly happens due to a wrong filepath. Open the lightbox 
> and check the HTML by doing rightclick > show frame source. Is the <img> 
> tag there? Where does it point to? Is there an img at the specified 
> location (either fileadmin or typo3temp)? Turn on debugging for the 
> lightbox in the CONSTANT EDITOR and check the fullPath property in the 
> metadata register.
> 
> Maybe the img gets lost when processed to typo3temp. Another test can be 
> to try it with an image that is smaller than the values given in 
> plugin.damlightbox.maxW/maxH (800/600). If things are set up currectly 
> this image should be opened directly from fileadmin...
> 
>> P.S.:
>> Dose your extension support a feature pass the photos through a 
>> GIFBUILDER for e.g. to use effects or to include a watermark on the 
>> photos?
> 
> Since damlightbox is 99% TS based, that is certainly possible ;) You 
> just need to modify the DAM_IMAGE marker. Here is a working example that 
> will render the DAM copyright information on the images:
> 
> damlightbox.10.10.renderObj.20.marks.DAM_IMAGE.10 {
> 
>     file >
> 
>     file = GIFBUILDER
>     file  {
>         XY = [10.w],[10.h]
>         quality = 100
>         format = jpg
> 
>         10 = IMAGE
>         10.file {
>            
>             import.cObject < temp.getDAMvalues
>             import.cObject.cObject.value = 
> TSFE:register|tx_damlightbox|metaData|{register:currentImg}|fullPath
>            
>             width.cObject < temp.getDAMvalues
>             width.cObject.cObject.value = 
> TSFE:register|tx_damlightbox|metaData|{register:currentImg}|hpixels
>            
>             height.cObject < temp.getDAMvalues
>             height.cObject.cObject.value = 
> TSFE:register|tx_damlightbox|metaData|{register:currentImg}|vpixels
>            
>         }
> 
>         20 = TEXT
>         20.text.cObject < temp.getDAMvalues
>         20.text.cObject.cObject.value = 
> TSFE:register|tx_damlightbox|metaData|{register:currentImg}|copyright
>         20.text.data = TSFE:register|tx_damlightbox|metaData|0|copyright
>         20.text.noTrimWrap = |(C) ||
>         20.align = left
>         20.offset = 20,30
>         20.fontSize = 20
>         20.fontColor = #FFFFFF
>         20.nicetext = 1
>     }
> }
> 
> Hope this helps to solve the problems. Greetings and nice Easter Monday,
> Torsten


More information about the TYPO3-project-dam mailing list