Page 1 of 1

[Solved] Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Wed Jul 12, 2006 12:53 am
by trud
Here are my errors:

Code: Select all

string(53) "Smarty error: problem creating directory 'D:/Clients'" string(53) "Smarty error: problem creating directory 'D:/Clients'"
Warning: Smarty::include(D:\Clients\A1\mydomain.com\public_html/tmp/templates_c\%%D8\D86\D862692E%%template%3A4.php) [function.include]: failed to open stream: No such file or directory in D:\Clients\A1\mydomain.com\public_html\lib\smarty\Smarty.class.php on line 1265

[b]Warning:[/b] Unknown: open(c:\tmp\sess_o4s27h3dplcuig6avg5gjh56s0, O_RDWR) failed: Permission denied (13) in Unknown on line 0

[b]Warning:[/b] Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\tmp) in Unknown on line 0
I have set permission manually to write for the following folders/sub folders:

tmp/templates_c
tmp/cache
uploads
uploads/images
modules

Then I also changed permisson on config.php. The strange thing is that the installer has actually created the files, yet it says it can not

My server facts:


Operating System Windows 2003
PHP Version            5.12
IIS Version             6

I am on windows 2003 server, and run IIS rather then apache as you see, and for now I am not able to use apache nor linux box. So I must find a way to get around this in windows.

Re: string(53) "Smarty error: problem creating directory

Posted: Thu Jul 13, 2006 4:03 pm
by trud
From the installation guide:

Step 4

Now for the script to access the folder properly, you need to change permissions of the following files and directories on the server.
CHMOD these to 777:

    * tmp/templates_c
    * tmp/cache
    * uploads
    * uploads/images
    * modules


CHMOD?!? Well, in most cases you can alter the permissions by right-clicking in your FTP program on the directory or file in question, selecting CHMOD or File Attributes (or something similar) and enter 777 in the appropriate field. Otherwise, check the manual of your FTP program.

Step 5

In a text editor, create an empty file naming it config.php. Save that file in the CMSMS directory (same (sub)directory as in step 3).

Set permissions to that file to 666.
Has there been any changes for the installation process for version 0.13 that is not reflected in the above quoted text?
Is there other folders that need write permission?

Strange thing is when I did a test install with the previous version (0.12), that one istalls like a breeze. Delating the test install and DB, and doin a compelte new and clean install with version 0.13 once again created smarty error.

The damn thing is that the error msg is bitching about a folder/file allready created by the installer.
As long as the installer has the right to create the file in the first place and executes this right, how come it then complain about lack of permissions?

I am left with almost no hair left on my head caused by the stress of this error, so any and all help will be highly appreciated and might actually prevent me from loosing all my hairs;-)

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 13, 2006 5:24 pm
by tsw
Warning: Unknown: open(c:\tmp\sess_o4s27h3dplcuig6avg5gjh56s0, O_RDWR) failed: Permission denied (13) in Unknown on line 0


check that c:\tmp\ exists and that it has necessary permissions set (dont ask why it wants to write there ;)

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 13, 2006 5:56 pm
by trud
Yes here is antoher thing. The file path for my account at the server is D:\Clients\A1\mydomain.com\public_html\*root*\*whateverfolder*

Why it will try to access C: I do not understand. Does installer try to create any tempfiles in C: during installation? This seems rather strange cause most hosts as far as I know will not let customers accounts access files on C: cause that is mainly OS and webserver (in my case, win2003+IIS).

Maybe I get this totally wrong, and if that is the case, pls do correct me.

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 13, 2006 6:18 pm
by trud
What settings could affect the installer to try to get access to C: ?
And how can I make changes so the tempfiles get written to my domain, rather then c: ? Is there anywhere in the installer script I can make the changes, or is it php whom controlls this, or how does this actually work?

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 13, 2006 6:56 pm
by trud
I just did yet another completly clean install of version 0.13 into win 2003 server running IIS.
This time I got an even shorter error message:

string(53) "Smarty error: problem creating directory 'D:/Clients'" string(53) "Smarty error: problem creating directory 'D:/Clients'"

And I have double checked and even triple checked that I have set all the needed permissions for the installer to run and execute the install scripts. It all is ok, so why all the error?

Others on win+IIS that might have tips?

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 13, 2006 7:00 pm
by trud
Strangest thing. I noticed that the admin login still works. I log in, and things looks rather normal.
A few icons have gone missing, but it appears I can make changes and things are running.


So why do I miss some icons, and why error message when I try to view default page in browser?

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 13, 2006 7:37 pm
by trud
Solved by the help of Ted, thank you Ted. On the chat I got this link from Ted and step one solved it all for me.

http://forum.cmsmadesimple.org/index.ph ... l#msg30934

Ted said:
What got changed was setting smarty to not use subdirectories for compiled templates

Re: Smarty error after clean install ver 0.13 => Need hlp pls

Posted: Thu Jul 27, 2006 3:18 pm
by Elijah Lofgren
trud wrote: ...
A few icons have gone missing, but it appears I can make changes and things are running.

So why do I miss some icons? ...
That was a bug in CMSMS 0.13, CMSMS 1.0 beta1 fixes this.