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.

Parsing error in 2.2.1

July 25, 2011 7:52am

Subscribe [5]
  • #1 / Jul 25, 2011 7:52am

    Benoît Marchal

    204 posts

    I’m running EE 2.2.1 build 20110705 and I have encountered the following which I assume is a bug.

    I have the following code in one my embedded template. The template is embedded in a [removed] tag in the main page. This code was written in 1.5.x migrated to 1.6.x, migrated to 2.1.x and it has always worked, according to the history the last time I worked on it was in April 2010 so I would have considered it rock-solid 😊

    $('#tamron').flash({ swf:'{site_url}clic/theme/ads/Tamron_B005_120x600_prague_v2_FR.swf',width:120,height:600, hasVersion: 7 });

    In EE 2.2.1, it renders as:

    $('#tamron').flash();

    so it removes the arguments for the function. I had to rewrite as:

    $('#tamron').flash({
       swf:'http://www.declencheur.com/clic/theme/ads/Tamron_B005_120x600_prague_v2_FR.swf',width:120,height:600, hasVersion: 7 });

    Note the line break and the removal of the {site_url} variable. I assume this is a bug in the 2.2.1 parser. Please confirm and I’ll file a bug report.

    Thanks

  • #2 / Jul 25, 2011 6:19pm

    Sue Crocker

    26054 posts

    Just a quick question - do you have debug=“0” still? See this post: http://ellislab.com/forums/viewthread/193583/

  • #3 / Jul 26, 2011 1:42pm

    Benoît Marchal

    204 posts

    What does this debug=0 do exactly?

  • #4 / Jul 27, 2011 12:06pm

    Dan Decker

    7338 posts

    Hello Benoit,

    $config[‘debug’] = “0”

    was deprecated in 2.2.0, but has likely been carried forward through your upgrade process via your config.php file. Can you set the value to “1” and see if that clears things up for you?

    Thanks,

  • #5 / Jul 27, 2011 1:01pm

    Benoît Marchal

    204 posts

    $config[‘debug’] = “0”
    was deprecated in 2.2.0, but has likely been carried forward through your upgrade process via your config.php file. Can you set the value to “1” and see if that clears things up for you?

    It does but what does debug=0 does?

  • #6 / Jul 27, 2011 4:02pm

    Brandon Jones

    5500 posts

    Benoît,

    Setting debug to 0 will hide all errors, including what EE believes to be invalid EE tags (which is what your JS looked like to it). Please keep the setting at 1. Glad that works!

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

ExpressionEngine News!

#eecms, #events, #releases