Js Conflict

More
13 years 1 month ago #2234 by dgjoom
Replied by dgjoom on topic Re: Js Conflict
Hi.. thanks for reply.
As my first post, i use T3 Framework with JA Elastica template (responsive template), the template use "masonry.js" to made the template elastic.
detail active js, see the file.
Thanks
Attachments:

Please Log in or Create an account to join the conversation.

More
13 years 1 month ago #2235 by ced1870
Replied by ced1870 on topic Re: Js Conflict
do you see which error you have in your browser console ?
Can you send me all the code from your page from top to </head>
CEd

Joomlack Webmaster and Developer

Please Log in or Create an account to join the conversation.

More
13 years 1 month ago #2237 by dgjoom
Replied by dgjoom on topic Re: Js Conflict
Yes sure.
Here all the file

Thanks
Attachments:

Please Log in or Create an account to join the conversation.

More
13 years 1 month ago #2238 by ced1870
Replied by ced1870 on topic Re: Js Conflict
and do you have an error in your browser console ?
Is seems that the slideshow is not loaded in the page that you gave the code...

Joomlack Webmaster and Developer

Please Log in or Create an account to join the conversation.

More
13 years 1 month ago #2303 by ced1870
Replied by ced1870 on topic Re: Js Conflict
Please try with the version 1.0.3
www.joomlack.fr/extensions-joomla/slideshow-ck

CEd

Joomlack Webmaster and Developer

Please Log in or Create an account to join the conversation.

More
13 years 3 weeks ago #2487 by davy
Replied by davy on topic Re: Js Conflict
Thanks! I spent hours trying to figure this out!

However, this would be problematic as I would be limited to using module extensions that have this option or that don't create a conflict. Do you have a longer-term fix to the problem?

The console always shows something of the sort:

Uncaught TypeError: Object #<Object> has no method 'getStyle' mega.js:230
(anonymous function) mega.js:230
(anonymous function) mootools-core.js:88
d mootools-core.js:367
e mootools-core.js:368
Uncaught TypeError: Cannot read property 'parentNode' of null mootools-core.js:293
w.before mootools-core.js:293
Element.implement.inject mootools-core.js:316
(anonymous function) mega.rjd.js:22
(anonymous function) mootools-core.js:375
h mootools-core.js:33
Array.implement.each mootools-core.js:40
invoke.fireEvent mootools-core.js:374
g mootools-core.js:514
Uncaught TypeError: Object #<Object> has no method 'masonry' about:362
(anonymous function) about:362
jQuery.extend.ready jquery-1.4.4.js:447
DOMContentLoaded about:288

I came across a post on another forum suggesting the T3 Framework plugin should load after all other plugins that use mootools to avoid the conflict. I don't know if that's relevant, but the order of the T3 Framework plugin in the plugins list is 1000 - so i figured it's already last in line.

I hope you have a suggestion, thanks in advance!

Please Log in or Create an account to join the conversation.

Time to create page: 0.240 seconds

Fast and powerful creation, customizable and responsive.

Read More

We have 1113 guests and no members online