Jump to:

2081 Posts in 1001 Topics by 452 members

E-Commerce Modules

SilverStripe Forums » E-Commerce Modules » Error handling: Behavior.js

Discuss about the various e-commerce modules available:
Ecommerce, SS Shop, SilverCart and SwipeStripe
Alternatively, have a look the shared mailinglist.

Moderators: martimiz, Nicolaas, Sean, frankmullenger, biapar, Willr, Ingo, Jedateach, swaiba, simon_w

Page: 1
Go to End
Author Topic: 1589 Views
  • khaoz
    Avatar
    Community Member
    7 Posts

    Error handling: Behavior.js Link to this post

    Is there anyone who can tell me why I get this error:

    Error details web page

    Regel: 10
    Teken: 4
    Code: 0
    URI: http://xxxxxxx.nl/jsparty/behaviour.js?m=1240864752

    Bericht: Kan lid niet vinden.

    Regel: 10
    Teken: 4
    Code: 0
    URI: http://xxxxxx.nl/jsparty/behaviour.js?m=1240864752

    The problem is that the behaviour.js when trying to upload using the ecommerce module in 2.3.1 returns this error in IE8.
    I am aware that the client using SS 2.3.1 is a IE5/6 user thus different problems have to be fixed in the css but this truely is a .js error.

    Anyone??? please???

    f.y.i. the file behavior.js is in the jsparty folder...

  • Apophenian
    Avatar
    Community Member
    46 Posts

    Re: Error handling: Behavior.js Link to this post

    I'm also getting this error!

    Any help would be much appreciated...

  • KeithLeslie
    Avatar
    Community Member
    6 Posts

    Re: Error handling: Behavior.js Link to this post

    I was able to resolve this issue by using the compatability view under the tools menu in IE8. This is however something the SilverStripe developers should look into as I do not believe this is a good long-term solution.

  • Howard
    Avatar
    Community Member
    215 Posts

    Re: Error handling: Behavior.js Link to this post

    My JS knowledge is crappy so I can't help you out but I thought I'd just let you know that Behaviour.js is in the process of being totally rewritten and they're doing away with the jsparty folder for the 2.4 release so I imagine there isn't going to be any time to put into fixing this bug if it can work under compatibility mode as it's going to be a different process for 2.4.

    Here's hoping that it's not to long until next release

    1589 Views
Page: 1
Go to Top

Want to know more about the company that brought you SilverStripe? Then check out SilverStripe.com

Comments on this website? Please give feedback.