I'm really sorry, i read all the threads i could find on this subject but i remain stumped.
I'm running v.1.5.4 "Carolina" and i've not had a single issue up until i tried to move to a new server. That might be a clue in and of itself, but i'm danged if i know what sort of clue because it's the same basic WHM/Cpanel configuration as my old server.
Anyway i've been converting all of my clients to CMSMS, working locally and then editing the config.php, zipping it all up, uploading and unzipping it, then importing the db and setting file permissions. It's been working like a charm.
The first time i tried this on my new server, the website goes fine but the backend crawls. I'm just guessing it's a problem with a module. The "Modules" section claims that the modules directory is not writable. I've logged in as user, and set permissions as user with both FTP and bash. The only thing come close to working was to recursively set 777 on modules directory and all subdirectories and files. That removed the "Change Permissions" link anyway, but not the warning at the bottom. ("Change Permissions" doesn't work, either.) The "Modules" folder says 777. Safe mode is not on.
I will readily admit to being a Linux ignoramus but i've done this before, just like this, so i can't understand why it don't work. The files should belong to the person who logged in and performed the operations, yes/no?
BTW the official "How To" at...
http://wiki.cmsmadesimple.org/index.php ... er_.281.29
...says to set permissions as so:
chmod 775 tmp; \
chmod 775 tmp/templates_c; \
chmod 775 tmp/cache; \
chmod 775 uploads; \
chmod 775 uploads/images; \
chmod 775 modules
This has never worked for me. Thus far /templates_c and /cache have insisted on being 777
Modules Directory Not Writable
-
- Forum Members
- Posts: 14
- Joined: Tue May 19, 2009 8:03 pm
Modules Directory Not Writable
Last edited by Joe McPlumber on Wed Jun 10, 2009 1:42 am, edited 1 time in total.
Re: Modules Directory Not Writable
Permission depend to many factors but primary to your setting provider
CMSMS permissions must be related to php OWNER (many times is same of web OWNER) and not of
Have you look in System operaton and in error logs for other infos?
Alby
CMSMS permissions must be related to php OWNER (many times is same of web OWNER) and not of
php files run in any accounts but if must perform some operations then php engine must has right permissions for that operationJoe McPlumber wrote: person who logged in and performed the operations
Have you look in System operaton and in error logs for other infos?
Alby
-
- Forum Members
- Posts: 14
- Joined: Tue May 19, 2009 8:03 pm
Re: Modules Directory Not Writable
Ah then it is my Linux ignorance.CMSMS permissions must be related to php OWNER (many times is same of web OWNER) and not of
Quote from: Joe McPlumber on Yesterday at 19:38
person who logged in and performed the operations
php files run in any accounts but if must perform some operations then php engine must has right permissions for that operation
I mean, the permissions look (to me) identical on both servers, and they say 777 (or rwxrwxrwx) and all files belong to user who owns the account and the group owner is of the same name as the user. By default, if i log in as "foo" then whatever files i put on the server belong to user "foo" and group "foo" and are read-and/or writable by user or group "foo".
So how do i, as described, give the php engine permissions to manipulate said files?
Re: Modules Directory Not Writable
You must know user/group of php owner.Joe McPlumber wrote: So how do i, as described, give the php engine permissions to manipulate said files?
If your php is "apache2handler", php run with httpd (web) owner/group, if run in cgi depend of your provider
However, try to install directly via browser (with cPanel).
Look if you can upload whole pack and uncompress directly from the web filemanager
Alby