CMSMS 2.x installer weirdness

[kikinovak]

Hi,
I've been using CMSMS since version 1.x, and I like it a lot. The new installer for 2.x is nice, but there's something weird. Let me explain.
On my public servers (all running Slackware Linux), the Apache server is running as user 'apache' and group 'apache'. I'm using Apache Virtual Hosts, and I have a few dozen sites hosted on each server. As is to be expected, all webpages are owned by user 'apache' and group 'apache'.
On my workstation (also running Slackware Linux) I have a bit of a special setup. My only user on that workstation is 'kikinovak' with 'users' as primary group. On this machine I'm doing some local web development, and since I'm the only user on it, I decided to run the Apache web server with the limited rights of my own user, meaning kikinovak:users. Here's what I have in /etc/httpd/httpd.conf:

Code: Select all

User kikinovak
Group users

All my webpages are under ~/Web, and there's quite many virtual hosts, all belonging to kikinovak:users. There's even quite a few CMS Made Simple 1.x based sites, all working nicely.
Now when I try to install CMS Made Simple 2.x using the new installer, I get a 301 error, and the installer stops short quite early in the process. I can install everything using a quirk by running Apache temporarily as apache:apache and making a recursive chown -R apache:apache on my installation. Then, once everything is installed and the site is running, I can chown -R kikinovak:users my new CMS Made Simple 2.x installation and reconfigure Apache to run as my normal user.
CMS Made Simple 2.x is the only web application that shows this kind of behavior. I'm running all kinds of web applications on this machine (Dolibarr, GEPI, Wordpress, etc.), they all work as normal user.
Any idea what's going on here?

[Jeff]

My guess is that somewhere in the apache or php setup you still have user apache:apache. Since we don't have access to your machine it is very difficult to say with any amount of certainty what is going on.

The main 2.x installer uses a PHAR install file unlike the 1.x or Wordpress(IIRC). Maybe something with how the PHAR is access/loaded is using a module that still is running with user apache.

Try installing with the expanded installer and see if that gives any different results.