Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Forum Module /

Discuss the Forum Module.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Javascript problem


Go to End


12 Posts   4318 Views

Avatar
Nivanka

Community Member, 400 Posts

8 July 2009 at 10:45pm

Ah this is mootools again, I heard this problem from one of my friends. But I couldn't figure it out, to use mootools with other Javascript libraries, such as jQuery or Prototype. I am not sure whether there is a way though.

I have raised this as a question somewhere on this forums, (cant remember where :) ). Anyway try asking about it on the mootools IRC. I will try too.

Avatar
draft

Community Member, 57 Posts

9 July 2009 at 4:02am

Hi,

Thx for the reply.. Unfortunately you also don't have any answer :(
The exact problem now is between mootools and prototype that conflict. When creating a form, there are some javascript loaded, and the prototype and protoype_improvements.js that caused the problem.. So right now the temporary solution to make the mootools animation work is by block that 2 javascript, it just make the form validation will reload the whole page when validating.

Anyway thx for your reply nivanka, and please inform me once you have the answer, i will also look around to see if there are someway to avoid this conflict.

-Draft

Avatar
Nivanka

Community Member, 400 Posts

9 July 2009 at 4:39am

yes thats correct, prototype and mootools conflicts, anyway if we can find an answer for this it will be more useful for others as well.

Avatar
draft

Community Member, 57 Posts

9 July 2009 at 2:40pm

Yes, i think it would be very helpful.. Do you think we can raise this to the silverstripe senior developer? Probably they can find a way to change the form validation method..

Go to Top