Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58961
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain l-i-e.com designates 67.139.134.202 as permitted sender)
Message-ID: <00ce1db3da8e20a8234e35c852e3dc81.squirrel@www.l-i-e.com>
In-Reply-To: <4F61BE09.3040705@rotorised.com>
References: <4F60F4B1.5010407@lerdorf.com> <4F611045.8040404@rotorised.com>
    <4F618F30.7060209@sugarcrm.com> <4F61BE09.3040705@rotorised.com>
Date: Thu, 15 Mar 2012 10:07:02 -0500
To: "internals@lists.php.net" <internals@lists.php.net>
User-Agent: SquirrelMail/1.4.21 [SVN]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
Subject: Re: [PHP-DEV] Let parse_str() parse more than max_input_vars args
From: ceo@l-i-e.com ("Richard Lynch")

On Thu, March 15, 2012 5:01 am, Ryan McCue wrote:
> I'm not arguing that it should, I'm saying that in the INI it refers
> to
> the HTTP arguments, while in the code (via ini_set) it would not
> affect
> this. I think that could be confusing for users who don't realise the
> script is only loaded after parsing the request.

If they don't know it by the time they need parse_str, it's time for
them to learn it... :-)

Not saying it won't cause confusion: But they have to make some effort
to figure out how PHP works.

Maybe a link in the error message to something that documents the
workflow clearly enough that they "get it" just by clicking on the
link and reading?

-- 
brain cancer update:
http://richardlynch.blogspot.com/search/label/brain%20tumor
Donate:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE