>Well, I'm not sure about the 'you get what you pay for'. Some paid for
>software has less support and documentation than PHP!
In my experience, *ALL* paid-for software has less support and documentation
than PHP.
This is excluding support contracts for software you paid for -- Once you
pay Orac
Well, I'm not sure about the 'you get what you pay for'. Some paid for
software has less support and documentation than PHP!
"Justin French" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> Greg,
>
> Your attitude stinks.
>
> PHP is a FREE scripting language.
> Who said anything about M$? I don't use their crappy products so I
> don't have to deal with their security issues.
I'm the one who brought up Microsoft, I'm saying it's a whole lot better
then the alternatives.
> If PHP 4.2 is unsafe then why is it listed at the top of the page for
> down
[snip]
>Well, trying to updrade on Slackware Linux 8.0 and compiling with the GD
>(1.8.4) libraries are giving us some headaches. Some of what seems to be
>wrong;
...
You're simply looking at the old PHP.
You did stop/start Apache, right?... Cuz the new PHP won't kick in until
you do.
If so, al
Greg,
Your attitude stinks.
PHP is a FREE scripting language. Think about the amount of money you are
probably charging hosting clients, or charging in web or programming
services, or making in site revenue, or whatever way you 'commercially
function' through PHP.
The register globals 'imposit
>Well, trying to updrade on Slackware Linux 8.0 and compiling with the GD
>(1.8.4) libraries are giving us some headaches. Some of what seems to be
>wrong;
>
>phpinfo() does not show new build times for each compile, not seemingly a
>caching problem (we have shut down browsers and then re-opened t
[snip]
Can anyone that has done it comment on the complexities of the upgrade?
[/snip]
Well, trying to updrade on Slackware Linux 8.0 and compiling with the GD
(1.8.4) libraries are giving us some headaches. Some of what seems to be
wrong;
phpinfo() does not show new build times for each compile
, July 22, 2002 1:52 PM
To: Richard Baskett; PHP General
Subject: Re: [PHP] PHP Security Advisory: Vulnerability in PHP
versions4.2.0 and 4.2.1
> Well from the sound of it, it's a quick painless process to upgrade
> php to the newest version using the patch. Can anyone that has done
>
> Well from the sound of it, it's a quick painless process to upgrade php to
> the newest version using the patch. Can anyone that has done it comment
on
> the complexities of the upgrade? Im just going on what it says on the php
> homepage...
Nice and easy for me, I'm running it on windows, th
Well from the sound of it, it's a quick painless process to upgrade php to
the newest version using the patch. Can anyone that has done it comment on
the complexities of the upgrade? Im just going on what it says on the php
homepage...
Rick
"When you walk to the edge of all the light you have
Hey man, if you can't stand the heat, get out of the freakin sun.
Atleast PHP tells you about holes, not like Microsoft who will fix it
six months down the line (if they even admit a hole exists). Plus, if
your running anything past 4.1.2 on production systems, it's your own
damn fault because sev
11 matches
Mail list logo
