php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Doc Bug #34315 Installer disables php in httpd.conf
Submitted: 2005-08-31 14:05 UTC Modified: 2005-09-01 16:34 UTC
From: marcus at synchromedia dot co dot uk Assigned:
Status: Closed Package: Documentation problem
PHP Version: 5.1.0RC1 OS: MacOS X 10.4.2
Private report: No CVE-ID: None
View Developer Edit
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: marcus at synchromedia dot co dot uk
New email:
PHP Version: OS:

 

 [2005-08-31 14:05 UTC] marcus at synchromedia dot co dot uk 
Description:
------------
Everything compiles and installs ok (as an apache2filter), but 
apache2 just doesn't load it. I tracked it down to a simple 
problem in httpd.conf - the 5.1 installer comments out this 
line:

LoadModule php5_module        /sw/lib/apache2/modules/
libphp5.so

Even though make install said:

[preparing module `php5' in /sw/etc/apache2/httpd.conf]

An identical configuration of PHP 5.0.5RC2 works perfectly and 
does not comment out that line, The CLI compile of 5.1 works 
ok too.

Reproduce code:
---------------
Starting with a working install of 5.0.5RC2,

% cd php-5.1.0RC1

% grep php5_module /sw/etc/apache2/httpd.conf

LoadModule php5_module        /sw/lib/apache2/modules/libphp5.so

% make install
...
% grep php5_module /sw/etc/apache2/httpd.conf

#LoadModule php5_module        /sw/lib/apache2/modules/libphp5.so

So it's definitely the installer that's disabling it.

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2005-08-31 14:12 UTC] derick@php.net 
Jani, I think this is broken by you when you changed the apxs switch from "install" to "not install" or something, please have a look at it.
 [2005-08-31 14:16 UTC] sniper@php.net 
That change was intentional, no bug here.
 [2005-08-31 14:48 UTC] marcus at synchromedia dot co dot uk 
Any particular reason?

I can see it being not unreasonable for new installs, but for 
upgrades (i.e. where the LoadModule line is already active) it 
seems really unnecessary. It means that every install of 5.1 
will default to not working, even if it was working before.

Is this change in behaviour documented?
 [2005-08-31 14:53 UTC] derick@php.net 
It's stupid to do this - it will stop running installs from working properly when people upgrade.
 [2005-08-31 16:36 UTC] sniper@php.net 
It's done because most distributions with apache2 use the 'conf.d' style modularized configurations and the apxs tool can't handle anything but httpd.conf and that results in having the line in question in 2 places. Documentation should state this.
 [2005-08-31 16:46 UTC] marcus at synchromedia dot co dot uk 
OK, I can understand that reasoning, However, the choice is 
really between getting a (non-fatal) warning on startup for a 
duplicate LoadModule statement vs not working at all. I'd say 
the former is the more tolerable choice. While the 
complications with conf.d stuf may be true, if you find an 
uncommented LoadModule in httpd.conf, it doesn't seem likely 
that it is already duplicated elsewhere. I'm not familiar with 
how you tweak httpd.conf programatically, so I guess there may 
be more to it than that.
 [2005-09-01 16:34 UTC] sniper@php.net 
Reverted: I didn't realize it touched existing lines too and not only when it has to ADD it..
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Mon Jul 14 23:01:34 2025 UTC