I'm using fireBug to seeks my bug in FF and I found out that the LightBox have a big problem.

When ever i click on an image to pop it up the lightbox pop half of the white background and stop.

and i get this error in my Firebug.

[code:1]effect.element has no properties
[Break on this error] setStyle(effect.element.firstChild, {bottom:
effects.js (line 689)[/code:1]

I looked it up in Effects.js and here what it seem to be the problem

[code:1] setStyle(effect.element.firstChild, {bottom:
(effect.dims[0] - effect.element.clientHeight) + 'px' }); }},[/code:1]

If anyone have a solution about this it would be more than welcome. I really light the lightbox effect and use it around in most of my website thanks a lot

Hello,

I have the same problem. After more than one year, out of the blue it's not functioning anymore within IE and Firefox. Screen stays white, and you will see the errorcount increase. (Offcours it could be a javascipt conflict...)

I really don't know what is causing this issue..

Hope somebody from Joomlapolis can help us

Thanks in advanced,
Rstyle

I found out that it has something to do with the code on line 119 within MooTools.1.11.js.

If I disable that line, than the lightbox is working again! So probably somekind of a javascript conflict!

Are you using MooTools also?

This is the code in MooTools:

[code:1]},removeEvents:function(A){if(!this.$events){return this;}if(!A){for(var B in this.$events){this.removeEvents(B«»);}this.$events=null;}else{if(this.$events[A]){this.$events[A].keys.each(function(C){this.removeEvent(A,C);[/code:1]

Im using the Mootoolsv1.1.js

but its seems like its a modified version of it... may i ask how you found out it was that line who was defective ?

Post edited by: claudeesti, at: 2008/05/26 22:57

Use Firefox and install the free plugin "firebug".
Go to your page and hit F12. Than you can find there all your (errors) and conflicts.

Also go to "net" and "JS" and see if you having the same problem.

Javascripts conflicts...

Cheers,
R

i am having this problem also, I was wondering did it get fixed by deleting that line of code you mentioned?
Would this impact on anywhere else. Also is this file within the mootools in my template folder because I could not find that line?