[WEB4LIB] Re: migrating to php

[Pecaut, Mark J.]

Just have php parse .html files instead of just .php or .php3 files.  
>From the php manual (http://www.php.net/distributions/bigmanual.html):
---
17. Edit your httpd.conf or srm.conf file and add: 
      
     For PHP 3:   AddType application/x-httpd-php3 .php3
     For PHP 4:   AddType application/x-httpd-php .php
 
  You can choose any extension you wish here.  .php is simply the one
  we suggest.
---
Just add a line to your httpd.conf file like this:

AddType application/x-httpd-php .html

and restart your webserver.  
-Mark


> -----Original Message-----
> From: Thomas Dowling [mailto:tdowling at ohiolink.edu]
> Sent: Wednesday, September 06, 2000 1:05 PM
> To: Multiple recipients of list
> Subject: [WEB4LIB] Re: migrating to php
> 
> 
> > For some time now we've been discussing the idea of moving our links
> > collection to a database and php format for easier management by
> > the reference staff.
> >
> > We've done some testing, and everything looks good. The 
> staff is even
> > excited about the web-based forms for adding and deleting links. But
> now
> > it occurs to me that this is going to mean re-naming a good 
> portion of
> our
> > files from .html to .php. And as we all know, this breaks the first
> web
> > commandment of never renaming or moving files and/or directories.
> >
> > I see in the archives that a few of you have already added this
> feature
> > (some using php, others using perl). I would be interested 
> to know how
> you
> > handled the change from .html files to .php or .cgi.
> >
> 
> If you're using Apache, and if you're able to maintain the other parts
> of the directory and file names, you can do a RedirectMatch:
> 
>   RedirectMatch permanent /our_cool_links/(.*).html
> /our_cool_links/$1.php
> 
> 
> http://www.apache.org/docs/mod/mod_alias.html#redirectmatch 
> for details
> 
> 
> Thomas Dowling
> OhioLINK - Ohio Library and Information Network
> tdowling at ohiolink.edu
>