unrecognized tag error - FEU login form - "clear cache" SOLVED
Posted: Sun Sep 21, 2008 12:03 pm
CMS-MS 1.4.1
Windows XP SP3 with XAMPP 1.6.6
Site with CustomContent and 3 FEU groups, each of which sees a different menu when logged in.
Problem: Occasionally, especially when a user logs out, the FEU users login form is replaced by an error message, along the lines of:
"string(173) "Smarty error: [in module_db_tpl:FrontEndUsers;feusers_loginform line 27]: syntax error: unrecognized tag: $mod->Lang(\'info_forgotpw\') (Smarty_Compiler.class.php, line 446)" string(145) "Smarty error: etc etc"
As soon as the window is refreshed, the error message disappears and the login form reappears.
The error can be reproduced by clearing the cache *while a user is logged in*: as soon as the user logs out, the error message appears.
Can anybody help? Could it be a problem with a path variable? (I've checked the root-path variable in config.php using realpath and have found it to be correct.)
Thank you.
Stephen
SOLVED
The problem was caused by the backslashes that had somehow crept into the FEU login template (e.g. \'info_forgotpw\')
Windows XP SP3 with XAMPP 1.6.6
Site with CustomContent and 3 FEU groups, each of which sees a different menu when logged in.
Problem: Occasionally, especially when a user logs out, the FEU users login form is replaced by an error message, along the lines of:
"string(173) "Smarty error: [in module_db_tpl:FrontEndUsers;feusers_loginform line 27]: syntax error: unrecognized tag: $mod->Lang(\'info_forgotpw\') (Smarty_Compiler.class.php, line 446)" string(145) "Smarty error: etc etc"
As soon as the window is refreshed, the error message disappears and the login form reappears.
The error can be reproduced by clearing the cache *while a user is logged in*: as soon as the user logs out, the error message appears.
Can anybody help? Could it be a problem with a path variable? (I've checked the root-path variable in config.php using realpath and have found it to be correct.)
Thank you.
Stephen
SOLVED
The problem was caused by the backslashes that had somehow crept into the FEU login template (e.g. \'info_forgotpw\')