Topic-icon javascript error?? on latest release.

Active Subscriptions:

None
10 years 10 months ago #33758 by jdekempenaer
Hi Alex, can I break in on this thread. I am experiencing a javascript conflict after upgrading to the lastest SCLogin (btw very nice login module, like it a lot!). I identified SCLogin as the cause by switching on and off various modules. I am using the Shape 5 vertex template by the way with the S5 flex menu.
What happens is this: When SCLogin is active and Load JQuery is set to yes the drop-downs on the S5Flex menu are not working anymore but the login and register buttons are working fine. When I then click on a menu that has no drop-down the page shows up and THEN the drop downs start working again.
Now if I set Load JQuery to NO then the drop-down will work as they should but the login button (pointing to #login-modal) is dead. When I set the display type to always visible the login button works fine again, so i suspect the problem is with loading the modal popup....
the S5 flexmenu does not allow me to switch loading JQuery on or off and i have not managed to find any option to change the order for these two modules to load....
Kinda stuck now ....
It looks as if i do not have the zip file of the previous version anymore so cannot revert back to the previous sclogin ...
jk
The topic has been locked.
Support Specialist
10 years 10 months ago #33761 by alzander
All aboard! :) No problem for jumping in. Though generally it's best to create a new topic unless your issues are directly related to the rest of the thread.

First off, the v2.0 SCLogin module can be downloaded below in case you want to revert:
www.sourcecoast.com/index.php?option=com...ease&Itemid=248&id=4

As for your issue, jQuery is used to load the modal popup. It sounds like there's likely a conflict in jQuery itself, which is odd, but may be caused by different versions. We're using v1.9.1, which is backward compatible, but it may introduce some issues somewhere. Can you post, or Private Message, me a link to your site where we can see the troublesome module? We're planning to release v3.0.1 (hopefully) later this week, so if there's a fix we can implement to make things more compatible then, we'd love to do it.

Thanks,
Alex
The topic has been locked.