Hi,
I am working with CMSMS 1.2.4 on my own server to test and it works great. Now I have installed it on another server which has 1 odd thing: the path for the writable data directory is different from the normal path.
So lets say my normal path is /site/www . This directory is not writable for my server. There is another data directory with path /site/data.
So I thought I would just put the /site/www as root_path (in the config) and /site/data/tmp/cache and /site/data/uploads as the tmp and upload dirs because they need to be written to (and that can only be done in de data dirs).
I dont yet know if I will encounter a problem with modules (since this also need to be writable), but I am faced with my first problem:
It seems that even though I have set the tmp/cache path, in the admin when I want to preview a page (I have transferred all pages and data from my old server, so that is why I can enter the admin and there are some pages there) I get the following error:
string(94) "Smarty error: problem creating directory '/site/www/tmp'" string(135) "Smarty error: the $compile_dir '/site/www/tmp/templates_c' does not exist, or is not a directory."
So am I correct in thinking that here it does not take the tmp/cache path from the config? Because it takes the root and puts tmp/ and tmp/templates_c behind it.
Is it even possible to have split paths, one for writeable directories and one for the rest?
Sincerely,
Sirab
[SOLVED] paths in config/split paths for writable data and other files
[SOLVED] paths in config/split paths for writable data and other files
Last edited by sirab on Mon Apr 28, 2008 11:05 am, edited 1 time in total.
Re: paths in config/split paths for writable data and other files
You must edit fileloc.php also.sirab wrote: I am working with CMSMS 1.2.4 on my own server to test and it works great. Now I have installed it on another server which has 1 odd thing: the path for the writable data directory is different from the normal path.
So lets say my normal path is /site/www . This directory is not writable for my server. There is another data directory with path /site/data.
So I thought I would just put the /site/www as root_path (in the config) and /site/data/tmp/cache and /site/data/uploads as the tmp and upload dirs because they need to be written to (and that can only be done in de data dirs).
I dont yet know if I will encounter a problem with modules (since this also need to be writable), but I am faced with my first problem:
It seems that even though I have set the tmp/cache path, in the admin when I want to preview a page (I have transferred all pages and data from my old server, so that is why I can enter the admin and there are some pages there) I get the following error:
string(94) "Smarty error: problem creating directory '/site/www/tmp'" string(135) "Smarty error: the $compile_dir '/site/www/tmp/templates_c' does not exist, or is not a directory."
For modules, install via files and not ModuleManager
Alby
Re: paths in config/split paths for writable data and other files
Thanks for your fast reply.
In fileloc.php I see the following:
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');
How do I change this for my situation?
And I don't see the tmp directory itself or even the modules directory to be defined. Can I define the tmp path itself somewhere also (so not only the tmp/cache)?
Sincerely,
Sirab
In fileloc.php I see the following:
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');
How do I change this for my situation?
And I don't see the tmp directory itself or even the modules directory to be defined. Can I define the tmp path itself somewhere also (so not only the tmp/cache)?
Sincerely,
Sirab
Re: paths in config/split paths for writable data and other files
In this moment I don't remember use of tmp directory only ....sirab wrote: Thanks for your fast reply.
In fileloc.php I see the following:
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');
How do I change this for my situation?
And I don't see the tmp directory itself or even the modules directory to be defined. Can I define the tmp path itself somewhere also (so not only the tmp/cache)?
for fileloc:
define("TMP_CACHE_LOCATION", "/site/data/tmp/cache");
define("TMP_TEMPLATES_C_LOCATION", "/site/data/tmp/templates_c");
you cannot modify admin,lib,modules,plugins directories
Alby
Re: paths in config/split paths for writable data and other files
I found it. I did:
define("TMP_CACHE_LOCATION", '/site/data/tmp/cache');
etc.
That worked. Thanks
define("TMP_CACHE_LOCATION", '/site/data/tmp/cache');
etc.
That worked. Thanks
-
- Support Guru
- Posts: 8169
- Joined: Tue Oct 19, 2004 6:44 pm
Re: paths in config/split paths for writable data and other files
the tmp directory itself is used for various file uploads, and downloads, and for the template externalizer and other modules. It is recommended that you not change this structure as it may break something.
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.