I have the following setup:
* MLE 1.6.6
* Gallery 1.1.2
* Formbuilder 0.6b2
* Captcha 0.4
* CGExtentions 1.17.6
Yesterday I deleter FormBuilder and today I have re-installed CGExtentions.
I'm getting various smarty error messages across all pages it seems. It doesn't happen every time, but is common.
So far I've seen the following 3 messages:
string(114) "Smarty error: [in tpl_body:27 line 55]: syntax error: unrecognized tag 'var' (Smarty_Compiler.class.php, line 590)" string(110) "Smarty error: [in tpl_body:27 line 56]: syntax error: unrecognized tag: (Smarty_Compiler.class.php, line 446)" string(111) "Smarty error: [in tpl_body:27 line 56]: syntax error: unrecognized tag '' (Smarty_Compiler.class.php, line 590)"
string(114) "Smarty error: [in tpl_body:24 line 47]: syntax error: unrecognized tag 'var' (Smarty_Compiler.class.php, line 590)" string(110) "Smarty error: [in tpl_body:24 line 48]: syntax error: unrecognized tag: (Smarty_Compiler.class.php, line 446)" string(111) "Smarty error: [in tpl_body:24 line 48]: syntax error: unrecognized tag '' (Smarty_Compiler.class.php, line 590)"
string(114) "Smarty error: [in tpl_body:23 line 56]: syntax error: unrecognized tag 'var' (Smarty_Compiler.class.php, line 590)" string(110) "Smarty error: [in tpl_body:23 line 57]: syntax error: unrecognized tag: (Smarty_Compiler.class.php, line 446)" string(111) "Smarty error: [in tpl_body:23 line 57]: syntax error: unrecognized tag '' (Smarty_Compiler.class.php, line 590)"
I've had a look through the s/w documentation and on the forums, but right now I'm not sure where to start with trouble shooting this. Can someone point me in the right direction?
Thanks,
Richard
SOLVED: Smarty errors (problem was Google Analytics code)
SOLVED: Smarty errors (problem was Google Analytics code)
Last edited by RJK on Mon Dec 21, 2009 1:26 pm, edited 1 time in total.
Re: Smarty errors
This is now solved. It turned out the issue was to do with the Google Anakytics code. It appeared that as it contained '{' and '}' in the code that it was messing everything up. Putting it in to GCB such as {global_content name='analytics'} resolved it.