SOLVED! HELP! string(106)- "Smarty error: [in template:20 line 6]:

[TaruNi]

Hi,

First of all, sorry, I´m not sure if this is the right place but couldn´t find another more appropriate. For some reason our homepages don´t work and show this instead:
string(106) "Smarty error: [in template:20 line 6]: [plugin] unknown tag - 'sitename' (core.load_plugins.php, line 124)" string(103) "Smarty error: [in template:20 line 6]: [plugin] unknown tag - 'title' (core.load_plugins.php, line 124)" string(108) "Smarty error: [in template:20 line 9]: [plugin] unknown tag - 'stylesheet' (core.load_plugins.php, line 124)" string(106) "Smarty error: [in template:20 line 108]: [plugin] unknown tag - 'search' (core.load_plugins.php, line 124)" string(104) "Smarty error: [in template:20 line 153]: [plugin] unknown tag - 'menu' (core.load_plugins.php, line 124)" string(107) "Smarty error: [in template:20 line 175]: [plugin] unknown tag - 'content' (core.load_plugins.php, line 124)"

We have the version 1.2.2 "Holetown"
We haven´t made any changes, they worked just fine yesterday. I am such a rookie with these things, somebody else made our homepages and I have just updated them from time to time, and so far everything has worked well...  :'(

Also, when I log in as admin, there are these two rows under the content tab
--Add Me - module:FileManager string:currentpath-- /
--Add Me - module:News string:news--

I don´t have a clue what to do to fix this, please help!

[moorezilla]

Did you add some javascript or css to your template without {literal}{/literal} around it? Did you make any other changes to the template? Might check there first. Might try clearing your cache in cmsms as well. After this is fixed, you'll probably want to consider upgrading to a newer version of cmsms as well.

[Jos]

If you didn't change anything, my guess is that your hoster did.
Did they change the root-path?  You may check with them if $config['root_path'] and the other paths in the config.php is good?

[TaruNi]

Thanks so much for your help and quick answers! 
It turned out it was the host with problems, not us. Phew.

Cheers!