Re: FW: Cookies, Dammit!
| From: | CC Zona | Date: | Wed, 17 Jan 2001 09:40:27 +0000 |
| Subject: | Re: FW: Cookies, Dammit! | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-35003@lists.php.net to get a copy of this message | ||
In article <NEBBKDGLILKGILMDBCBKKEEHCCAA.rscrawford@mossroot.com>,
rscrawford@mossroot.com ("Richard S. Crawford") wrote:
> The problem is that the main page doesn't use an include file of any sort;
> it's straight HTML which is frequently updated by hand. I agree that it
> would be nice if /index.htm had an include file that contained most of the
> content, and if I could convince my boss that it would be the best way to
> go, then I'd be set. :) Unfortunately, that's not the route that we've
> chosen to go (in fact, I'm still at the stage where I'm trying to convince
> people around here that PHP is a much better way to go than straight HTML
> for some of these documents). So, if I were using an include file to build
> /index.htm, then I would use it in microsite45/index.htm. But since I'm
> not, I can't. I've got permission to use document.write in /index.htm, so I
> was looking for a solution which would allow /index.htm to remain nothhing
> but static HTML (with the exception of some JavaScript).
Is this on Apache? <warning: untested idea> I'm wondering if you couldn't
use an Apache <FILES> directive to turn on PHP's auto-append feature for
that one page. Then the people who need to tinker with the HTML could do
so freely without the possiblity of messing with the include; in fact,
they'd never have to know about the include file's existance, it'd just
happened "automagically" as far as they (and the boss) are concerned.
--
CC