| 2009-08-29 17:33:40 |
Piotr Kęplicz |
description |
By default, suPHP is configured in a way that should enable suPHP for all sites within root directory with exception for distro-packaged webapps that reside in /usr/share (for which mod-php5 is used).
However when both suphp and php5 modules are enabled in apache2, the default for all php files is still mod-php5. With only suphp enabled, distro-packages webapps such as phpmyadmin don't work since their files are owned by root.
Debian packages carry a necessary fix that involves changing application/x-httpd-php to application/x-httpd-suphp in {/etc/suphp/,/etc/apache2/mods-available/}suphp.conf. |
By default, suPHP is configured in a way that should enable suPHP for all sites within root directory with exception for distro-packaged webapps that reside in /usr/share (for which mod-php5 is used).
However when both suphp and php5 modules are enabled in apache2, the default for all php files is still mod-php5. With only suphp enabled, distro-packages webapps such as phpmyadmin don't work since their files are owned by root.
Debian packages carry a necessary fix that involves changing application/x-httpd-php to application/x-httpd-suphp in {/etc/suphp/,/etc/apache2/mods-available/}suphp.conf.
libapache2-mod-suphp:
Installed: 0.6.2-3
Candidate: 0.6.2-3
Version table:
*** 0.6.2-3 0
500 http://pl.archive.ubuntu.com jaunty/universe Packages
100 /var/lib/dpkg/status
|
|
