Problem after installation
Problem after installation
Dear All,
First of all: This CMS system looks very nice and I cannot wait to get started with it. After running through the installation guide without any problems, I get the following fault message when I visit the site or try to login the admin system. (see www.olsengroup.dk as well)
string(50) "Smarty error: problem creating directory 'd:/home'" string(50) "Smarty error: problem creating directory 'd:/home'"
Warning: fetch(d:\home\olsengroupdk\www/tmp/templates_c\%%D8\D86\D862692E%%template%3A4.php): failed to open stream: No such file or directory in d:\home\olsengroupdk\www\lib\smarty\Smarty.class.php on line 1265
Warning: fetch(): Failed opening 'd:\home\olsengroupdk\www/tmp/templates_c\%%D8\D86\D862692E%%template%3A4.php' for inclusion (include_path='.;c:\php4\pear') in d:\home\olsengroupdk\www\lib\smarty\Smarty.class.php on line 1265
Look forward to hearing from you and thanks in advance.
TO.
First of all: This CMS system looks very nice and I cannot wait to get started with it. After running through the installation guide without any problems, I get the following fault message when I visit the site or try to login the admin system. (see www.olsengroup.dk as well)
string(50) "Smarty error: problem creating directory 'd:/home'" string(50) "Smarty error: problem creating directory 'd:/home'"
Warning: fetch(d:\home\olsengroupdk\www/tmp/templates_c\%%D8\D86\D862692E%%template%3A4.php): failed to open stream: No such file or directory in d:\home\olsengroupdk\www\lib\smarty\Smarty.class.php on line 1265
Warning: fetch(): Failed opening 'd:\home\olsengroupdk\www/tmp/templates_c\%%D8\D86\D862692E%%template%3A4.php' for inclusion (include_path='.;c:\php4\pear') in d:\home\olsengroupdk\www\lib\smarty\Smarty.class.php on line 1265
Look forward to hearing from you and thanks in advance.
TO.
Last edited by TO on Wed Jul 05, 2006 2:57 pm, edited 1 time in total.
Re: Problem after installation
Thanks for getting back to me. I am using the latest release.
TO
TO
Re: Problem after installation
TO wrote: string(50) "Smarty error: problem creating directory 'd:/home'" string(50) "Smarty error: problem creating directory 'd:/home'"
Warning: fetch(d:\home\olsengroupdk\www/tmp/templates_c\%%D8\D86\D862692E%%template%3A4.php): failed to open stream: No such file or directory in d:\home\olsengroupdk\www\lib\smarty\Smarty.class.php on line 1265
Have you set right permissions to template_c folder (chmod 777)?
Re: Problem after installation
My webhotel provider said that the permission should be okay, but I will check it with them again.
Will come back...
Thanks
TO
Will come back...
Thanks
TO
Re: Problem after installation
I am having a very similar problem using version 0.13 (the latest zip) after installation:
string(54) "Smarty error: problem creating directory 'C:/Websites'" string(54) "Smarty error: problem creating directory 'C:/Websites'"
This directory already exists on my server. This directory is also in the path to the CMS installation directory. Regardless of the rights on templates_c, why is CMS trying to create it? And why is it trying to create/write to anything outside of its document root?
string(54) "Smarty error: problem creating directory 'C:/Websites'" string(54) "Smarty error: problem creating directory 'C:/Websites'"
This directory already exists on my server. This directory is also in the path to the CMS installation directory. Regardless of the rights on templates_c, why is CMS trying to create it? And why is it trying to create/write to anything outside of its document root?
Re: Problem after installation
It's needed for smarty caching. Smarty is CMSms template engine.Mike8888 wrote: Regardless of the rights on templates_c, why is CMS trying to create it?
Re: Problem after installation
That doesn't explain why CMS is trying to make directory "C:\Websites" when it already exists. Also, security-wise, CMS should't be allowed to do anything outside of the "C:\Websites\CMS\" directory.
I am not a PHP coder, but ...
Looking through the script code though, I see one "Smarty" module ("[root install]\lib\smarty\internals\core.create_dir_structure.php") is trying to load a setting ("open_basedir") from some "php.ini" file. When I checked what it was loading during execution, it was an empty string, which obviously isn't correct. I looked though the installation code and saw nothing actually setting INI values using "ini_set." Am I correct that the installation is supposed to set some of the INI settings?
I am not a PHP coder, but ...
Looking through the script code though, I see one "Smarty" module ("[root install]\lib\smarty\internals\core.create_dir_structure.php") is trying to load a setting ("open_basedir") from some "php.ini" file. When I checked what it was loading during execution, it was an empty string, which obviously isn't correct. I looked though the installation code and saw nothing actually setting INI values using "ini_set." Am I correct that the installation is supposed to set some of the INI settings?
Re: Problem after installation
running windoze or linux...
went thru the installation as put fourth in the "handbook" ?
went thru the installation as put fourth in the "handbook" ?
Re: Problem after installation
Hello,
I'm remotely administering Windows 2000 Server using IIS 5.0 with PHP 4.3.8. I installed CMS version 0.13 (zip) using the Install via FTP handbook. All the steps worked successfully until I clicked the final link to test the CMS installation, which produced the "Smarty" error I posted above.
Also of note is that CHMOD using SmartFTP wouldn't work due to hosting restrictions, so I remotely changed the CMS root directory using "Remote Desktop" to allow all access for the meantime.
Thanks in advance for any help.
I'm remotely administering Windows 2000 Server using IIS 5.0 with PHP 4.3.8. I installed CMS version 0.13 (zip) using the Install via FTP handbook. All the steps worked successfully until I clicked the final link to test the CMS installation, which produced the "Smarty" error I posted above.
Also of note is that CHMOD using SmartFTP wouldn't work due to hosting restrictions, so I remotely changed the CMS root directory using "Remote Desktop" to allow all access for the meantime.
Thanks in advance for any help.
Re: Problem after installation
Ok, two suggestions here.
1. Open up lib/content.functions.php. Look for $this->use_sub_dirs = true; near the top. Change it to $this->use_sub_dirs = false;
2. Change fileloc.php to
However, please try step 1 before moving on to step 2 and let me know how it goes.
Thanks!
1. Open up lib/content.functions.php. Look for $this->use_sub_dirs = true; near the top. Change it to $this->use_sub_dirs = false;
2. Change fileloc.php to
Code: Select all
define("CONFIG_FILE_LOCATION", dirname(__FILE__) . DIRECTORY_SEPARATOR . 'config.php');
define("TMP_CACHE_LOCATION", dirname(__FILE__) . DIRECTORY_SEPARATOR . 'tmp' . DIRECTORY_SEPARATOR . 'cache');
define("TMP_TEMPLATES_C_LOCATION", dirname(__FILE__) . DIRECTORY_SEPARATOR . 'tmp' . DIRECTORY_SEPARATOR . 'templates_c');
Thanks!
Re: Problem after installation
Well, thanks a lot for getting me further. Changing the setting to false got me to the main page (your first option).
Unfortunately, when I tried to go to the administration page via the link on the main page, I got some access violation. After just reloading the page, the admin logon screen came up (and continues to come up without problem). But, upon logging in, all I get is a blank page, with the URL being one path directory up (and outside) of the document root. I know there are other forums dealing with this different issue, so I'll look into those to see what solutions exist.
Again, I appreciate your help.
Unfortunately, when I tried to go to the administration page via the link on the main page, I got some access violation. After just reloading the page, the admin logon screen came up (and continues to come up without problem). But, upon logging in, all I get is a blank page, with the URL being one path directory up (and outside) of the document root. I know there are other forums dealing with this different issue, so I'll look into those to see what solutions exist.
Again, I appreciate your help.