Forum posts to 'Archive'

Re: behaviour.js conflicts with mootools.js

Ingo — Sun, 22 Jun 2008 01:51:27 +1200

both mootools and prototype share the same bad practice of cluttering the global namespace in javascript (with the $ function). one of many reasons why we're moving to jquery

if you're sure you don't need behaviour.js (e.g. you don't want any clientside form validation), you can disable it by calling Requirements::block('jsparty/behaviour.js')

Posted to: behaviour.js conflicts with mootools.js Show Thread | Post Reply

Re: behaviour.js conflicts with mootools.js

willr — Mon, 16 Jun 2008 17:58:32 +1200

Prototype is used throughout the front end of the site - page comments, login, basically anywhere theres a form!.

One of the things coming up is SS is moving to a jQuery JS library and away from prototype. I know quite a few of us in recent projects have spent some time stripping Behaviour and prototype out of the various front end components to provide us with a clean slate. Some of this work will be part of trunk soonish I guess unless its already in there!

If you are trying to use mootools you will have to dig round and round digging out the old Behavior JS as it will pop up like a weed!

Posted to: behaviour.js conflicts with mootools.js Show Thread | Post Reply

Re: behaviour.js conflicts with mootools.js

Double-A-Ron — Mon, 16 Jun 2008 13:56:26 +1200

Yes, I've noticed the same. I've had to stop behaviour loading on any pages I'm using Mootools.

I think the error is:
Behavior is not defined.

Must be a conflict or some sort, but I havn't delved deeper. It's best to avoid Mootools unless Prototype can't help you, as prototype is packaged with Silverstripe, and is totally incompatible with Mootools. (last I heard)

Aaron

Posted to: behaviour.js conflicts with mootools.js Show Thread | Post Reply

behaviour.js conflicts with mootools.js

piksel — Thu, 27 Mar 2008 14:59:18 +1300

behaviour.js seems to be used in front-end pages if you add $SilverStripeNavigator to your template. The problem is I'm trying to use mootools and they are conflicting...

I guess it just means I can't have the SS Navigator menu on the front-end right? Or, I don't use mootools

Posted to: behaviour.js conflicts with mootools.js Show Thread | Post Reply