Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: Problem with .php file extensions  (Read 4321 times)

0 Members and 1 Guest are viewing this topic.

gschimek

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Problem with .php file extensions
« on: September 13, 2005, 11:02:32 pm »

My site is hosted by Earthlink and they are running PHP version 4.  The problem is that any php scripts run on there will only work with a .php4 extension.  I tried changing install.php to install.php4 and it ran, but after putting in the initial info, it errored out, saying that install.php couldn't be found.

Is there a way to get around the .php4 issue?
Logged

kegobeer

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 4637
  • Beer - it does a body good!
    • The Kazebeer Family Website
Re: Problem with .php file extensions
« Reply #1 on: September 13, 2005, 11:22:06 pm »

Ask your host to enable .php files.  If they won't, you could try using htaccess (if you are on an Apache powered webserver) to redirect .php requests to .php4.  If you can't do that, then you'll have to open every file up, and change .php to .php4.  This may work in your htaccess file:

Code: [Select]
RewriteEngine ON
RewriteRule ^([a-zA-Z]+)\.php$ $1.php4 [L]

It should automatically redirect .php requests to .php4.
Logged
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

gschimek

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Re: Problem with .php file extensions
« Reply #2 on: September 14, 2005, 12:05:13 am »

I put that file in my coppermine folder, called it .htaccess, tried it with chmod 644 and 755, and always get a 500 Internal Server Error.  If I delete the file, it works like before but still have the php4 problem.

Any ideas.
« Last Edit: September 14, 2005, 12:17:14 am by gschimek »
Logged

Nibbler

  • Guest
Re: Problem with .php file extensions
« Reply #3 on: September 14, 2005, 08:50:55 am »

Ask your host for support. With such an odd server setup I expect they'll be asked about this problem frequently.
Logged

gschimek

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Re: Problem with .php file extensions
« Reply #4 on: September 14, 2005, 03:38:01 pm »

Well, I called them up again (Earthlink) and asked them what they could do for me.  Their answer was to try putting a 4 at the end of the extensions, and if that doesn't work, I should look for an alternative script that will work.  I thought that was a load of bulll.  Since I also had problems a couple months ago with their implementation of Perl not working with a new version of my forums, I'm going to look for another web host.

So, does anyone have a good webhost that they can suggest to me?
Logged

kegobeer

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 4637
  • Beer - it does a body good!
    • The Kazebeer Family Website
Re: Problem with .php file extensions
« Reply #5 on: September 14, 2005, 04:36:18 pm »

There are plenty of good hosts - check out the general discussion board.

They sound like lazy hosts - all they have to do is edit the httpd file and add

AddType application/x-httpd-php .php

I guess that's too much work for them, or they have absolutely no idea what they're doing.
Logged
Do not send me a private message unless I ask for one.  Make your post public so everyone can benefit.

There are no stupid questions
But there are a LOT of inquisitive idiots

Tranz

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: 00
  • Offline Offline
  • Gender: Female
  • Posts: 6149
Re: Problem with .php file extensions
« Reply #6 on: September 14, 2005, 04:54:48 pm »

They should stick to being an ISP rather than being a web host.
Logged
Pages: [1]   Go Up
 

Page created in 0.016 seconds with 15 queries.