ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

jQuery Tools Scrollable Stopped Working

June 16, 2011 11:00am

Subscribe [3]
  • #1 / Jun 16, 2011 11:00am

    Mantishead

    55 posts

    Spent about 2 hours trying to debug why jQuery Tools Scrollables had stopped working in my templates, assuming I had either a CSS or JS bug somewhere.

    Eventually ran the static code outside of EE and the effects are executing perfectly.  Now completely stumped as to why EE should be prevent JS effects from executing.

    No errors are being reported.  Completely odd.  Any ideas…?

  • #2 / Jun 16, 2011 11:10am

    Mantishead

    55 posts

    Boom.  Just caught it.  Braces in JS being processed by EE.  Weird that this hasn’t been the case for several weeks and just started happening. 
    How do I escape the braces from EE’s grasp?

  • #3 / Jun 16, 2011 11:22am

    Mantishead

    55 posts

    I just don’t understand Ellis’ reasoning behind keeping this so quiet.  All together I have spent around 4 hours chasing this one up and down:
    http://ellislab.com/forums/viewthread/177632/

    I eventually narrowed the problem down to JS being removed but wasn’t until I read the above article that I was reminded of changing the debug level last week.

    Wow is all I can say without turning to offensive language…

  • #4 / Jun 17, 2011 12:48am

    John Henry Donovan

    12339 posts

    Mantishead,

    Sorry you wasted time on this

    As per the docs we recommend that you keep your debug level set to 1

    if you want to escape curly braces then using a line break works most of the time

    Can you share the js you are using?

  • #5 / Jun 17, 2011 12:07pm

    Mantishead

    55 posts

    /* Vertical Scollable */
    $(".vertical").scrollable({ vertical: true, mousewheel: false }).navigator();

    I went ahead with the fix as described:

    var $remove_unparsed_variables = FALSE; // whether to remove left-over variables that had bad syntax

    Which has worked fine.

    Would have left debug as it was but whilst logged in I was getting PHP warning about undeclared variable which was irritating; hence why I switched off.  Didn’t think in my wildest dreams that action would introduce such an elusive error.  The UI could do with a pop up when lowering debug which states ‘warning this may affect JS or anything with braces that EE doesn’t understand’.

  • #6 / Jun 18, 2011 1:13pm

    Greg Salt

    3988 posts

    Hi Mantishead,

    Glad that you got this fixed. What was the PHP warning you were getting? You should not be seeing anything like that. We should try and diagnose and fix that issue as well.

    Cheers

    Greg

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases