Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54073
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.186 cause and error)
Message-ID: <4E255A82.3030200@lsces.co.uk>
Date: Tue, 19 Jul 2011 11:20:50 +0100
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.19) Gecko/20110420 SUSE/2.0.14-2.2 SeaMonkey/2.0.14
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <20110718143939.GB23368@panix.com> <alpine.DEB.2.02.1107181721370.25471@whisky> <4E24B7AA.20309@gmail.com> <4E24BD03.9040108@thelounge.net> <CAH-PCH7kCUArcrKbKsyUse+RfrSsGJ3Sd-vrsQGR9=xKqJfeyg@mail.gmail.com> <4E2529DD.4050104@thelounge.net> <CAH-PCH43NGNqrkte-=66sCQvptNZ1BEvmu8WxTUyrSOkUDn6gQ@mail.gmail.com> <4E253E98.9070405@thelounge.net> <4E254325.40701@lsces.co.uk> <4E2546F8.1050707@thelounge.net>
In-Reply-To: <4E2546F8.1050707@thelounge.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] Magic Quotes in PHP, the Finalle
From: lester@lsces.co.uk (Lester Caine)

Reindl Harald wrote:
>>> magic_quotes_gpc is deprecated as of 5.3
>>> >>  http://php.net/manual/en/migration53.deprecated.php
>>> >>  only the default values was left to 1
>>> >>
>>> >>  how dumb is this?
>>> >>
>>> >>  if i deprecate something i do not like to use it in
>>> >>  future and at the same time i enable it as default?
>>> >>
>>> >>  there is no logical reason
>> >
>> >  Actually it is perfectly logical when one looks at 'BC'.
>> >  It may not have been the correct choice in hindsight, but it was implemented
>> >  at a time when PHP6 was on the road map, and that is no longer the case.
> does not matter
>
> anybody who maintains a server should make a explicit config
> and not relying on random defaults

Fine if you actually have ACCESS to the ini file !!!!
If you are on a service where access is not available, and the settings change 
breaking your site ...

The point I was trying to make is that simply switching something off that 
running and currently functional code expects to be on - because that is how 
they are provided with the service currently - is what needs managing. Hopefully 
we are not going back to the days when things were simply broken without 
warning, such as happened when PHP5.1 was pushed out ...

It is more about managing the change than simply removing magic quotes? The 
history of that proposed change is relevant since it highlights why some perhaps 
now incorrect choices were made, but simply reverting a choice needs to be 
documented properly.

Perhaps what I am looking for is some notes somewhere to direct people to WHEN 
their sites stop working as they have been for many years? Yes I know it's not 
the developers problem, but just as the change from PHP4, there is a LOT of 
legacy code that someone will need to change, and where people have made that 
change, their input would be helpful to others?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php