|
|
Posted by dorayme on 11/11/07 21:35
In article <cuGdndSdGKJ09KranZ2dnUVZ_jqdnZ2d@comcast.com>,
Ed Mullen <ed@edmullen.net> wrote:
> I'm considering using PHP to include the menus on my Web pages. I've
> tested it and it works fine (even though I know next to nothing about
> PHP). My understanding is that the page that will import content using
> a PHP include must have a .PHP extension. Which means that all my page
> names (which now end in .html) will change. Which means that the search
> engine results will point to non-existent pages.
>
> Any thoughts on what I might do about this dilemma?
On servers that you can control, you can make them check and
process for php on .html ages, either directly in config files or
via .htaccess. On servers that you do not control or do not allow
..htaccess control of this, you can ask the server admin to fix it
so that all your .html files are scanned for php.
If they will not allow this (there are some downsides, one being
servers have to work harder and less efficiently, not all html
files have php and it is wasting its time) you can ask them to
redirect all .html files to php mirror files which you can make
and put on the server to avoid having to upset already bookmarked
html files etc.
All these options I have done for different sites and purposes.
On one, I just have decided to use .php and be done (simple!).
--
dorayme
Navigation:
[Reply to this message]
|