| Re: why php echo does not show up in HTML? [message #181657 is a reply to message #181656] |
Fri, 24 May 2013 17:04   |
Tim Streater
Messages: 328
Registered: September 2010
Karma:
|
Senior Member |
|
|
In article <kno313$kpa$1(at)dont-email(dot)me>,
Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote:
> On 5/24/2013 11:47 AM, Tim Streater wrote:
>> In article <knnr88$4bg$1(at)dont-email(dot)me>,
>> Jerry Stuckle <jstucklex(at)attglobal(dot)net> wrote:
>>
>>> On 5/24/2013 9:40 AM, Tim Streater wrote:
>>
>>>> Personally I add:
>>>>
>>>> AddType application/x-httpd-php .phtml
>>>>
>>>> to the apache config file, and use that for files containing any PHP.
>>>> That way the PHP interpreter is only involved when a file actually has
>>>> PHP in it.
>>> What's the difference between using .phtml and .php (other than the
>>> former is non-standard and will not work on all systems)?
>>
>> None, I don't suppose, but it was the standard where I used to work. I
>> just followed it. I use .php for scripts that *only* contain php.
> That's reasonable, as long as you only run on servers you control. Of
> course, someone else's server could cause a problem.
Yes, in-house servers.
>> It's a shame that the universe doesn't use proper file metadata but as
>> we seem to be stuck using extensions they may as well mean something.
> I won't argue that. However, remember when the web started, many os's
> didn't support metadata (and some still don't do it properly). And,
> unfortunately, once a standard is implemented, it becomes very difficult
> to make a non-compatible change (which this would be).
Agreed, I was just having a whinge. :-) (fed up with it being cold -
it's about 6C today - and we just had a 90 min power outage)
--
Tim
"That excessive bail ought not to be required, nor excessive fines imposed,
nor cruel and unusual punishments inflicted" -- Bill of Rights 1689
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]