CMS Made Simple Forums

Hi everybody! I'm just finish installing this fantastic cms and i want to prove it but in the mainly page (the default php page after the install) i get this errors in the browser:

string(124) "Smarty error: [in preview:cms68.tmp line 9]: syntax error: unrecognized tag 'sitename' (Smarty_Compiler.class.php, line 583)" string(125) "Smarty error: [in preview:cms68.tmp line 12]: syntax error: unrecognized tag 'metadata' (Smarty_Compiler.class.php, line 583)" string(127) "Smarty error: [in preview:cms68.tmp line 15]: syntax error: unrecognized tag 'stylesheet' (Smarty_Compiler.class.php, line 583)" string(129) "Smarty error: [in preview:cms68.tmp line 18]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(129) "Smarty error: [in preview:cms68.tmp line 19]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(129) "Smarty error: [in preview:cms68.tmp line 20]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(123) "Smarty error: [in preview:cms68.tmp line 57]: syntax error: unrecognized tag 'anchor' (Smarty_Compiler.class.php, line 583)" string(123) "Smarty error: [in preview:cms68.tmp line 58]: syntax error: unrecognized tag 'anchor' (Smarty_Compiler.class.php, line 583)" string(129) "Smarty error: [in preview:cms68.tmp line 69]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(123) "Smarty error: [in preview:cms68.tmp line 77]: syntax error: unrecognized tag 'search' (Smarty_Compiler.class.php, line 583)" string(128) "Smarty error: [in preview:cms68.tmp line 84]: syntax error: unrecognized tag 'breadcrumbs' (Smarty_Compiler.class.php, line 583)" string(121) "Smarty error: [in preview:cms68.tmp line 96]: syntax error: unrecognized tag 'menu' (Smarty_Compiler.class.php, line 583)" string(123) "Smarty error: [in preview:cms68.tmp line 104]: syntax error: unrecognized tag 'print' (Smarty_Compiler.class.php, line 583)" string(130) "Smarty error: [in preview:cms68.tmp line 106]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(130) "Smarty error: [in preview:cms68.tmp line 106]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(130) "Smarty error: [in preview:cms68.tmp line 106]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(130) "Smarty error: [in preview:cms68.tmp line 106]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(124) "Smarty error: [in preview:cms68.tmp line 111]: syntax error: unrecognized tag 'anchor' (Smarty_Compiler.class.php, line 583)" string(130) "Smarty error: [in preview:cms68.tmp line 114]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(130) "Smarty error: [in preview:cms68.tmp line 115]: syntax error: unrecognized tag 'cms_selflink' (Smarty_Compiler.class.php, line 583)" string(132) "Smarty error: [in preview:cms68.tmp line 131]: syntax error: unrecognized tag 'global_content' (Smarty_Compiler.class.php, line 583)"

I supose that the problem could be the php version, i have installed a appserver with php 5 but i'm not sure it this is the problem and if i have tu install another php version like  php 3 or 4.

¿Could somebody help me?

Thank you very much.

The php version isnt the problem I run multiple cms`es on PHP 5.2.0 and 5.1.6 and no problems at all.

But I cant tell you what is, sorry If never seen this error before

The problem was related to a bug in the installer.  Either you can fix the missing slashes in config.php, or do a reinstall with the newly released 1.0.4.

Sorry for the inconvienence.

Hi, I'm still getting the same errors on a Win2003 server even after putting 1.0.4.
I've deleted everything from 1.0.3, purged the database and installed 1.0.4 fresh and continued to receive the Smarty errors.
My path is: $config['root_path'] = '\\nas31ent\domains\b\b*****.com\user\htdocs';

then I changed the paths to like '\domains\b\b*****.com\user\htdocs';
and the error went away, but Smarty is still not working - I get a simple empty Navigation&News screen without CSS.
When logged to admin everything looks right but modules are with --Add Me - module

Please help !!!

While on the real page I get no errors, in admin / content / pages, when I select the preview window, there are many errors of the type: etc. for every tag in the template.

Thank you very much now it works!!

Congratulations, can you please show me your path variables (from config.php)

I still can't get it work !!!

Anybody?

missing slashes are referred to in this posting from the config.php - coud someone tell me which ones are missing?

It seems that the problem arises from the double-backslash in front of this server's file storage, e.g. \\nas31ent\domains\b

I can't confirm anything more because I gave up on this and made the customers change to Linux hosting, where everything goes as usual.

oh right - I do have Linux hosting - my path settings are as following - can u see any wrong with these?
#------------
#Path Settings
#-------------

#Document root as seen from the webserver.  No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://fortpublishing.co.uk';

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = 'fortpublishing.co.uk/public_html';

#Name of the admin directory
$config['admin_dir'] = 'admin';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = 'fortpublishing.co.uk/public_html/uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://fortpublishing.co.uk/uploads';

helpme wrote: #Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = 'fortpublishing.co.uk/public_html';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = 'fortpublishing.co.uk/public_html/uploads';

Yes -- I think root_path and uploads_path must be absolute server filesystem paths like previews_path.
e.g. /websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html
that's assuming previews_path is correct, of course.

Yeah I have tried that.
I have also tried putting // instead of / at beginning of these paths.
Also tried \\ and \ at the beginning.
Also tried takin about most of the path and starting it just from fortpublishing for all 3 of the strings.
But nothing seems to work.

I can't think what else to try?

Maybe thats not even the problem - as no matter what I change I still get this error on front page (the path this error refers to doesnt change when I change any of my path settings in config.php ?):-

Warning: opendir(/websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/plugins) [function.opendir]: failed to open dir: No such file or directory in /websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/lib/content.functions.php on line 688

Warning: readdir(): supplied argument is not a valid Directory resource in /websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/lib/content.functions.php on line 689

Warning: closedir(): supplied argument is not a valid Directory resource in /websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/lib/content.functions.php on line 750

\, \\ or // mean nothing in the UNIX (Linux) world. All dirs are separated with /. If a path begins with / this means it begins from root (absolute path). Paths NOT beginning with / are relative to where the program is at the moment and thus cannot be used as you can never be sure where it would be at execution time.

You should check your real, absolute server paths and put them in. Nothing else. If you don't know how to look at the Linux dirs, check with your server administrator.

BTW, /websites/LinuxPackage02/fo/rt/pu/fortpublishing.co.uk/public_html/ seems to me very unusual, but your mileage may vary. Check the real path names.

Also don't forget UPPER and lower case is different in Linux. Usually they use only lower case for system folders.

Ok thanks for your help.  Ill get the hosting company to check path - but i've already been on phone to them and they said it looked ok - ill get them to check again.
Thanks.