CMS Made Simple Forums

Hi,

I am attempting to upgrade from 1.1.1 to 1.2.2. However, I noticed that a bunch of subdirectories have strange owners (like nobody or www-data).

I have not run into this problem in previous upgrades and am at a loss to figure this out.

According to the docs, when you upgrade, all you do (which I have done numerous times in the past) is to upload the upgrade setup for CMS Made Simple to your existing site and then overwrite all files in question. Now, however, at 1.2.2, when I do this I get really odd upload failures due to these ownership/permissions issues.

For instance, here is a partial listing of my modules permissions/owners:

-rw-r-----  1 nobody nobody 18292 Jul 17 20:32 UserManipulator.class.php
-rw-r-----  1 nobody nobody  3934 Jul 17 20:32 action.addgroup.php
-rw-r-----  1 nobody nobody  5759 Jul 17 20:32 action.addprop.php
-rw-r-----  1 nobody nobody  4223 Jul 17 20:32 action.addprop2.php
-rw-r-----  1 nobody nobody  1596 Jul 17 20:32 action.adduser.php
-rw-r-----  1 nobody nobody  8559 Jul 17 20:32 action.defaultadmin.php
-rw-r-----  1 nobody nobody  3405 Jul 17 20:32 action.do_addgroup.php
-rw-r-----  1 nobody nobody  4603 Jul 17 20:32 action.do_addprop.php
-rw-r-----  1 nobody nobody  2223 Jul 17 20:32 action.do_adduser1.php
-rw-r-----  1 nobody nobody  5995 Jul 17 20:32 action.do_adduser3.php

When I look at my other CMSMS server (my work server) - which has been running 1.2 for a while, I see this:

-rw-r--r--  1 www-data www-data  4224 2007-11-26 22:48 action.addgroup.php
-rw-r--r--  1 www-data www-data  4307 2007-11-26 22:48 action.addprop2.php
-rw-r--r--  1 www-data www-data  5759 2007-11-26 22:48 action.addprop.php
-rw-r--r--  1 www-data www-data  1596 2007-11-26 22:48 action.adduser.php
-rw-r--r--  1 www-data www-data  3910 2007-11-26 22:48 action.admin_exportgroup.php
-rw-r--r--  1 www-data www-data 11763 2007-11-26 22:48 action.admin_importgroup.php
-rw-r--r--  1 www-data www-data  1400 2007-11-26 22:48 action.admin_logout.php
-rw-r--r--  1 www-data www-data  2045 2007-11-26 22:48 action.admin_setlostun_template.php
-rw-r--r--  1 www-data www-data  8829 2007-11-26 22:48 action.defaultadmin.php
-rw-r--r--  1 www-data www-data  3970 2007-11-26 22:48 action.do_addgroup.php
-rw-r--r--  1 www-data www-data  4659 2007-11-26 22:48 action.do_addprop.php
-rw-r--r--  1 www-data www-data  2223 2007-11-26 22:48 action.do_adduser1.php

These were installed using CMS MS to install the modules either through the module manager or XML upload via the modules tab. My upgrade to 1.2 at work was done using FTP and my upgrade at home going from 1.1.1 to 1.2.2 was done using ssh via FileZilla. Both logged in as the proper account owner (not a special ID or something).

I'm assuming that as root I can change the ownership of all these to my account id...but why is this happening? Is this a bug? Or is there something I am not considering?

-p

Hmmmm....I just noticed something else as well...when you list the modules sub directories, I noticed that all the modules that have "incorrect" owners now are the ones I installed after the update. Here's the listing:

[root@bobo modules]# ls -al
total 192
drwxrwxrwx  32 brady  brady  4096 Dec  3 09:04 .
drwxr-xr-x  63 brady  nobody  4096 Dec  3 08:57 ..
-rwxrwxrwx  1 brady  brady  6148 Dec  3 09:28 .DS_Store
drwxr-x--x  6 nobody nobody  4096 Jul 17 20:12 ABFlashGallery
drwxrwxrwx  5 brady  brady  4096 Sep  1 07:28 CMSMailer
drwxrwxrwx  4 brady  brady  4096 Jun 29 13:12 CSSMenu
drwxr-xr-x  5 nobody nobody  4096 Nov 18 11:01 Comments
drwxr-x--x  3 nobody nobody  4096 Jul 17 20:29 CustomContent
drwxr-x--x  4 nobody nobody  4096 Jul 17 20:30 Diagnostics
drwxrwxrwx  4 brady  brady  4096 Jun 29 13:12 EllNav
drwxrwxrwx  5 brady  brady  4096 Jun 29 13:12 FCKeditorX
drwxr-xr-x  8 nobody nobody  4096 Dec  2 14:04 FeedbackForm
drwxr-x--x  7 nobody nobody  4096 Jul 17 20:32 FileManager
drwxr-xr-x  8 nobody nobody  4096 Dec  1 11:22 FormBuilder
drwxr-xr-x  5 nobody nobody  4096 Dec  2 14:23 Forum
drwxr-x--x  5 nobody nobody  4096 Jul 17 20:32 FrontEndUsers
drwxrwxrwx  5 brady  brady  4096 Jun 29 13:12 Kalender
drwxrwxrwx  5 brady  brady  4096 Sep  1 07:28 MenuManager
drwxrwxrwx  4 brady  brady  4096 Sep  1 07:28 ModuleManager
drwxrwxrwx  5 nobody nobody  4096 Jul 17 20:34 MysqlDump
drwxrwxrwx  4 brady  brady  4096 Dec  3 09:04 News
drwxrwxrwx  9 brady  brady  4096 Jun 29 13:12 Oscommerce_
drwxrwxrwx  2 brady  brady  4096 Dec  3 09:04 Printing
drwxr-xr-x  5 nobody nobody  4096 Nov 18 11:05 RateThis
drwxrwxrwx  3 brady  brady  4096 Sep  1 07:28 Search
drwxr-x--x  4 nobody nobody  4096 Jul 17 20:37 SelfRegistration
drwxr-x--x  5 nobody nobody  4096 Jul 17 20:39 SystemInfo
drwxrwxrwx  4 brady  brady  4096 Sep  1 07:28 ThemeManager
-rwxrwxrwx  1 brady  brady  50872 Dec  3 09:28 ThemeManager-1.0.4.xml
drwxrwxrwx  5 brady  brady  4096 Sep  1 07:28 TinyMCE
drwxr-xr-x  5 nobody nobody  4096 Dec  1 11:05 TinyMCEAdv
drwxr-x--x  5 nobody nobody  4096 Jul 17 20:40 Uploads
drwxr-x--x  4 nobody nobody  4096 Jul 17 20:41 VisitorStats
-rwxrwxrwx  1 brady  brady      0 Dec  3 09:28 index.html
drwxrwxrwx  4 brady  brady  4096 Sep  1 07:28 nuSOAP


So in this output, everything with an owner of 'nobody' was installed using CMSMS's internal module management function.

Seems more and more like a bug...

Nope its not a bug, thats how php on apache works.

php is run with the permissions set to it (quite often nobody or www or apache or something else). now when php process downloads the file from modulerepo and extracts it the files will be owned by the process that created them.

There are ways around this (suexec, suphp and so on) but most hosting companies wont use them as there is a slight overhead for it.

If you check the module listing there is a "Change permissions" link just for this. As the change permissions script is again run with the php permissions it has rights to change the perms.

You can read more on google

Hi,

Thanks. I do know about the change permissions link in modules, but often it does not work for me (in recent additions of modules). I should have posted that here...but got busy and forgot about it. If I see it again, I'll post it to this board.