CMS Made Simple Forums

Hi,

I just upgraded CMSMS to 1.11 on my Wamp 2.0 test server running under Win7. Upgrade worked smoothly and the admin panel is also accessible.
Now the problem is that my front-end template doesn't work anymore and displays the following error:

Error: at line 73 in file C:\wamp\www\ga\lib\smarty\sysplugins\smarty_internal_write_file.php:

Message:

unable to write file C:\wamp\www\ga\tmp\templates_c\a733fb********8f.module_db_tpl.MenuManager;CrystalX1024_Blue : CrystalX1024.php

I already searched the forum for any help and this is what I tried/found out so far:
-I tried using another template (e.g. Left simple navigation + 1 column) and it worked fine. It wrote also correctly into the tmp folder.
-I have set and checked permissions in file properties in windows.
-I have checked permissions in the system information and they seem to be set correctly:

Permission Information
tmp Success c:\wamp\www\ga\tmp (0777)
templates_c Success C:\wamp\www\ga\tmp\templates_c (0777)

-The template worked completely fine under 1.10.3. I use the CrystalX1024_Blue template found at http://themes.cmsmadesimple.org/uploads ... e.zip.html
-Here it is running correctly under 1.10.3 at http://www.groupe-animateur.lu

Thank you very much for any help!

Regards,

Lex

Apparently adding a new template using theme import changes the 'owner' and/or it seems like you have "cache menu template" enabled, looks like it's not a good idea when hosting it on your computer, disable it and see...

Thanks for your reply! I'm not quite sure if i checked the right thing, but I looked in menu manager and there the menu template is marked as not cachable. Is this what you meant or did I miss something?
Thanks again.

Don't know what to tell you, I use XAMMP on win7 and don't have this problem and I installed it on a 1.11 site w/o problems...

http://multiintech.com/beta/index.php?p ... msms-works

Hi,
Change the name of your menu template :
CrystalX1024_Blue : CrystalX1024
to
CrystalX1024_Blue_CrystalX1024
Don't forget to change your tag

Changing the name of the template finally fixed it!
Thanks!

Lex