View Full Version : Please help. Javascript conflict on one page of web site

08-29-2011, 04:10 AM
I have two main components running on this page below.


Sobi directory and gavick photoslide. The problem is that the photoslideshow is not loading only on the page witht he directory. I did a little investaged and got a error console for firefox and it showing this error:

Error: Fx.Opacity is not a constructor
Source File: http://vtpr.net/asociacion-relacionistas/modules/mod_gk_news_image_1/js/engine_compress.js
Line: 1

I have VERY VERY limited knowledge of javascript. Any and all help is super appreciated. Thanks in advance

Old Pedant
08-29-2011, 05:13 AM
Post your URL inside of [code]...[ /code] tags. It got mangled by the forum.

08-29-2011, 05:27 AM
thank you very much for telling me. Here it is:


Old Pedant
08-29-2011, 10:34 AM
Tomorrow, if nobody else has replied. It's late here. Bed time.

08-29-2011, 07:21 PM
ok cool! you help is very very much appreciated. I've spent days trying to solve this.

Old Pedant
08-29-2011, 08:53 PM
Have to admit defeat on this one. I think you need an expert on motools.js to help you out.

08-29-2011, 10:26 PM
whoa...didn't see that one coming! thank you anyways for atleast trying to help.

But how do you know it's a mootools.js issue. This is a quote from another forum. Tell me what you think if you can:

For each of the objects which require initialization through window.onload(); located their
initialization function and placed them all into one function called by onload().

Each time you attach a function the onload() event you overwrite the previous one.
Now that I have had a second look at the functions I listed, it seems I was mistaken.
These are not affecting each other in the manner I thought.

Old Pedant
08-30-2011, 02:46 AM
As he said, he was mistaken. In point of fact, there are several things that are added via the onload event. That's not where the problem is.

I don't *know* it is in motools.js, but that compression code is pretty generic and it is being invoked from motools.js line 21 at the point the failure occurs. At least, that's what I got out of FireBug's stack trace.