You're blindly flailing around at trying to solve this problem rather
than slowing down and thinking about what you're doing, combined with
looking at the documentation *slowly*.  It's pretty obvious based on
your comments and your existing configuration.

For Apache 2.x this is all you should need.  Paths should be configured
appropriately to match your setup (we use FreeBSD).  Again, read slowly.


LoadModule suphp_module       libexec/apache22/mod_suphp.so

# PHP support
AddType application/x-httpd-php .php
AddHandler x-httpd-php .php
suPHP_Engine on


The DirectoryIndex line you're using in your existing config will also
nuke the ability to use index.html, index.shtml, and so on.  You can
specify more than one index document filename to DirectoryIndex.

-- 
| Jeremy Chadwick                                    jdc at parodius.com |
| Parodius Networking                           http://www.parodius.com/ |
| UNIX Systems Administrator                      Mountain View, CA, USA |
| Making life hard for others since 1977.                  PGP: 4BD6C0CB |

On Wed, Aug 22, 2007 at 09:38:06AM +0100, Jason Bhalla-Gaunt wrote:
> Okay, I disabled the suPHP module by commenting out the LoadModule element, 
> and php was still being processed, I traced it down to another config file 
> activating it and disabled it there and re-enabled suPHP, now no php gets 
> processed, instead it tries to offer it as a download to me, this is my 
> config file for suPHP (this gets executed immediately after the LoadModule 
> blocks in httpd.conf):
>
>
> # This is a apache config file for suPHP, first we load the module
> LoadModule suphp_module modules/mod_suphp.so
>
> # Now we register extensions
> AddType application/x-httpd-php .php
> AddType application/x-httpd-php-source .phps
>
> # Register index.php as a valid index page
> DirectoryIndex index.php
>
> # Enable suPHP on all websites:
> suPHP_Engine on
>
>
> I have also tried interchanging AddType with AddHandler, if I do so then 
> all I get is the raw PHP contents returned as text. I have also tried 
> removing "application/" from each one, if I do that I get the source 
> returned but interpreted as HTML so it displays nothing.
>
> How can I fix this?
>
>
> On 21 Aug 2007, at 15:56, Simon Boulet wrote:
>
>> Jason,
>>
>> On 21-Aug-07, at 10:47 AM, Jason Bhalla-Gaunt wrote:
>>
>>> Hi again Simon,
>>>
>>> Yes, PHP4 was running prior to suPHP being installed, although I can't 
>>> find any LoadModule or AddModules that reference PHP in any way in the 
>>> config file.
>>>
>>> On 21 Aug 2007, at 15:32, Simon Boulet wrote:
>>>
>>>>
>>>> Did you had PHP running as a module before installing SuPHP?
>>>>
>>>> If so, have you disabled the PHP module form config file? see LoadModule 
>>>> and AddModule in your httpd.conf
>>>>
>>>>
>>
>>
>> First, you need to make sure SuPHP is called instead of the previous PHP 
>> module you had. Try disabling mod_suphp from your httpd.conf, and see if 
>> PHP is still being interpreted. Also try running "httpd -l" on your 
>> server, perhaps PHP is built-in.
>>
>> Another trick to check is if PHP is being run as a CGI (SuPHP runs PHP 
>> scripts as CGIs...) or as an Apache module from a phpinfo(). Have a look 
>> at "Server API", it must say "CGI".
>>
>> Simon
>>
>> !DSPAM:1,46cafdec318341113612667!
>>
>>
>
> ___________________
>
> Jason Bhalla-Gaunt
> +44 (0)121 233 4838 (Direct Dial)
> +44 (0)121 200 2627 (Main Line)
>
> Made Media Ltd
> 105 Carver St, Birmingham B1 3AP
> http://www.mademedia.co.uk/
> Registered in England & Wales: 4530365
>
> ___________________
>
>

> _______________________________________________
> suPHP mailing list
> [email protected]
> http://lists.marsching.biz/mailman/listinfo/suphp


_______________________________________________
suPHP mailing list
[email protected]
http://lists.marsching.biz/mailman/listinfo/suphp

Reply via email to