Mayer, Jonathan wrote:
Just thought I'd point out that it's recommended against giving non-php
extensions to PHP code pages. Basically, making all of your include
files .inc without the server correctly configured to recognise all .inc
files as PHP files, you are opening yourself up to possib
-Original Message-
From: Ashley Sheridan [mailto:a...@ashleysheridan.co.uk]
Sent: 09 March 2009 19:55
To: Mayer, Jonathan
Cc: Gary; php-general@lists.php.net
Subject: RE: [PHP] Re: PHP includes
On Mon, 2009-03-09 at 15:10 +, Mayer, Jonathan wrote:
> >Thank you to everybod
On Mon, 2009-03-09 at 15:23 -0500, Larry Garfield wrote:
> On Monday 09 March 2009 3:07:17 pm Nathan Rixham wrote:
> > Ashley Sheridan wrote:
> > > Just thought I'd point out that it's recommended against giving non-php
> > > extensions to PHP code pages. Basically, making all of your include
> > >
On Monday 09 March 2009 3:07:17 pm Nathan Rixham wrote:
> Ashley Sheridan wrote:
> > Just thought I'd point out that it's recommended against giving non-php
> > extensions to PHP code pages. Basically, making all of your include
> > files .inc without the server correctly configured to recognise al
Ashley Sheridan wrote:
Just thought I'd point out that it's recommended against giving non-php
extensions to PHP code pages. Basically, making all of your include
files .inc without the server correctly configured to recognise all .inc
files as PHP files, you are opening yourself up to possible h
On Mon, 2009-03-09 at 15:10 +, Mayer, Jonathan wrote:
> >Thank you to everybody that replied...but it almost seems it is making
> extra
> >work.
>
> >I can understand using an include for a menu, since they tend to change
>
> >often and it is on every page, but the normal content I am not
>
Gary wrote:
Thank you to everybody that replied...but it almost seems it is making extra
work.
I can understand using an include for a menu, since they tend to change
often and it is on every page, but the normal content I am not understanding
the benefit. If I have a page that has unique co
From: Gary
>
> Thank you to everybody that replied...but it almost seems it is making
extra
> work.
>
> I can understand using an include for a menu, since they tend to
change
> often and it is on every page, but the normal content I am not
understanding
> the benefit. If I have a page that h
>Thank you to everybody that replied...but it almost seems it is making
extra
>work.
>I can understand using an include for a menu, since they tend to change
>often and it is on every page, but the normal content I am not
understanding
>the benefit. If I have a page that has unique content on
On 16 January 2004 13:54, Freedomware wrote:
> Thanks for all the tips. It's getting generally getting
> clearer, but I'm
> a little confused somewhere.
[SNIP]
> I inserted one of the functions you suggested - $includea1 = TRUE; -
> after the include, but I'm sure I did it wrong.
Just like bef
Thanks for all the tips. It's getting generally getting clearer, but I'm
a little confused somewhere.
Can I give you a better explanation of what I'm trying to do, along with
my latest code?
The pages on this site focus on various nations and states, with lots of
links like this:
[LOCAL] ../w
On 16 January 2004 00:30, Freedomware wrote:
> I should have played with this some more before I posted more
> questions. After fixing an error on the included page, I replaced
> every instance of na/a1 on both pages with a1. That seemed to fix
> everything; the first style sheet comes through, bu
On 15 January 2004 22:39, Luke wrote:
> ? Holy cow, this gets simpler all the time. Pretty soon, there'll be
> ? nothing left on my page but PHP includes and echo functions! ?
> ? Does this cut down on a website's file size? In other
> words, are the php
> ? includes effectively inactive when no o
13 matches
Mail list logo
