CMSMS 2.0 installer creates wrong folder and file ownership

[d4creative]

I have installed the 2.0 system successfully, but when trying to upgrade I can't change any of the files or folders or change the permissions because I do not have ownership of the system as installed by the original 2.0 installer. My FTP lists the Owner/Group as "48 48" for anything installed automatically and I cannot alter anything. Other files that I have uploaded via FTP have "10244 2522" as the Owner/Group and I can modify those.
The net result is that I cannot perform any upgrade or modification to the CMSMS 2.0 install.

Any ideas why this would be? Anyone else experienced this problem? I should not have to get tech support from my hosting provider (Uber Global/AussieHQ) to manually go in and change permissions or ownership every time I need to upgrade it.

David

[velden]

Check the hosting's admin tools (DirectAdmin, Plesk, ...). I'd expect a file manager giving you the possibility to 'reset' ownership and if needed permissions recursively.

Probably you would face the same 'problem' when installing modules from within CMSMS (or any other web application on that server) or uploading files via a CMSMS module.

[d4creative]

The Plesk admin does not allow any change of ownership (on this host at least) and anything I haven't got ownership also I can't mod the permissions.

I have never come across ownership problems before using CMSMS with this host so it must be something to do with the new installer method. Always previously the files were all copied to the site via FTP as an unpacked ZIP (no unzip tools on the server end).

Perhaps this new install is using a script to write files from a different location defaulting to a different ownership?

[d4creative]

Adding more details: the CMS files added by the installer have user and group ownership set to "apache".

[velden]

It is using another method but you should be able to obtain ownership/change permissions. If not ask your provider.

The same problem would arise when for example uploading new files through any other php script.

[d4creative]

I have installed this in a sub-domain to test it out and I discovered a difference in how the sub-domain was setup. In the main hosting PHP is set to run as "Fast CGI Application" whereas in the sub-domain it was set to run as "Apache module".
I'm going to wipe the installation and run it again to see if it comes up different.

[d4creative]

After talking to tech support it seems the different setting for the php module may be the culprit.