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.

Disable {something} replacement

April 30, 2009 4:52pm

Subscribe [2]
  • #1 / Apr 30, 2009 4:52pm

    Ok, this is a very weird problem I run into. I use jquery tablesorter script and the config option for it is:

    $("#myTable").tablesorter({widthFixed: true, widgets: ['zebra']})
            .tablesorterPager({container: $("#pager")});

    This works perfectly with previous version (<1.6.7) and after I updated it to 1.6.7, I got this in the output screen instead:

    $("#myTable").tablesorter()
            .tablesorterPager();

    Note that EE replace everything inside {} with blank.

    How do I disable this, is there a work around?

  • #2 / Apr 30, 2009 5:08pm

    Mark Bowen

    12637 posts

    Hi there,

    There’s two things you can do here to hopefully get around this. The first being adding in a hidden configuration variable into your config.php file :

    system->configuration.php

    $conf['protect_javascript'] = 'n';

    Documentation Link

    You can try that or you can place a return after any { and } characters such as :

    $("#myTable").tablesorter({
    widthFixed: true, widgets: ['zebra']
    })
            .tablesorterPager({
    container: $("#pager")
    });

    Hope that helps a bit.

    Best wishes,

    Mark

  • #3 / Apr 30, 2009 5:22pm

    I set the hidden protect_javascript conf to “y” and it still mess up the code… Not sure if it’s my server config or it’s a bug in 1.6.7

    Got it to work with the linebreak closing tag as you suggested though

    Thank you for time.

  • #4 / Apr 30, 2009 5:25pm

    Mark Bowen

    12637 posts

    I set the hidden protect_javascript conf to “y” and it still mess up the code… Not sure if it’s my server config or it’s a bug in 1.6.7

    Got it to work with the linebreak closing tag as you suggested though

    Thank you for time.

    Hiya,

    Actually it should be set to “n” as I posted above 😉

    I just posted the link to the documentation which happens to have it set to “y”.

    Glad you’ve got it all working now though.

    Hope it all goes well for you.

    Best wishes,

    Mark

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

ExpressionEngine News!

#eecms, #events, #releases