On 20/05/2009 12.50, Ford, Mike wrote:
Humph! Yes, ok, I concede this point. I also bow to Daniele's need to
process forms designed by someone else with (not-PHP) in mind. Actually,
I can see the validity of both sides of the argument, and I teeter on
the fence as to whether the [] method is "ri
On Wed, May 20, 2009 at 6:50 AM, Ford, Mike wrote:
> On 19 May 2009 17:10, Andrew Ballard advised:
>> var toppings = document.sundae.toppings;
>> // To work with PHP, the above line would
>> have to be changed:
>> // var toppings =
>> document.sundae.e
Hello,
Here's another quick solution that shouldn't add much overhead:
// get input
$qry =
'toppings=sprinkles&toppings=nuts&toppings=fudge&toppings=caramel&toppings=strawberries';
//$qry = $_SERVER['QUERY_STRING'];
// parser input
$qry = str_replace('&toppings=','&toppings[]=',$qry);
parse_st
On 5/20/09 6:50 AM, "Ford, Mike" wrote:
> Humph! Yes, ok, I concede this point. I also bow to Daniele's need to
> process forms designed by someone else with (not-PHP) in mind. Actually,
> I can see the validity of both sides of the argument, and I teeter on
> the fence as to whether the [] meth
On 19 May 2009 17:10, Andrew Ballard advised:
> On Tue, May 19, 2009 at 10:11 AM, Ford, Mike
> wrote:
>> On 19 May 2009 14:37, Daniele Grillenzoni advised:
>>
>>>
>>> My complaint is this: a I can have a select multiple with a normal
name,
>>> which is allowed by every spec, but PHP requires me
Daniele Grillenzoni wrote:
On 20/05/2009 2.45, Nathan Rixham wrote:
Daniele Grillenzoni wrote:
On 19/05/2009 18.09, Andrew Ballard wrote:
On Tue, May 19, 2009 at 10:11 AM, Ford, Mike
wrote:
On 19 May 2009 14:37, Daniele Grillenzoni advised:
My complaint is this: a I can have a select multi
On 20/05/2009 2.45, Nathan Rixham wrote:
Daniele Grillenzoni wrote:
On 19/05/2009 18.09, Andrew Ballard wrote:
On Tue, May 19, 2009 at 10:11 AM, Ford, Mike
wrote:
On 19 May 2009 14:37, Daniele Grillenzoni advised:
My complaint is this: a I can have a select multiple with a
normal name,
whic
Daniele Grillenzoni wrote:
On 19/05/2009 18.09, Andrew Ballard wrote:
On Tue, May 19, 2009 at 10:11 AM, Ford, Mike
wrote:
On 19 May 2009 14:37, Daniele Grillenzoni advised:
My complaint is this: a I can have a select multiple with a
normal name,
which is allowed by every spec, but PHP requi
On 19/05/2009 18.09, Andrew Ballard wrote:
On Tue, May 19, 2009 at 10:11 AM, Ford, Mike wrote:
On 19 May 2009 14:37, Daniele Grillenzoni advised:
My complaint is this: a I can have a select multiple with a
normal name,
which is allowed by every spec, but PHP requires me to use []
in order
to
On Tue, May 19, 2009 at 10:11 AM, Ford, Mike wrote:
> On 19 May 2009 14:37, Daniele Grillenzoni advised:
>
>>
>> My complaint is this: a I can have a select multiple with a
>> normal name,
>> which is allowed by every spec, but PHP requires me to use []
>> in order
>> to properly retrieve the valu
On 19 May 2009 14:37, Daniele Grillenzoni advised:
>
> My complaint is this: a I can have a select multiple with a
> normal name,
> which is allowed by every spec, but PHP requires me to use []
> in order
> to properly retrieve the values.
I really don't understand the problem with this -- in fa
On 18/05/2009 10.42, Peter Ford wrote:
Daniele Grillenzoni wrote:
I noticed that php's way to fill $_GET and $_POST is particularly
inefficient when it comes to handling multiple inputs with the same name.
This basically mean that every in order to function
properly needs to have a name ending
Daniele Grillenzoni wrote:
> I noticed that php's way to fill $_GET and $_POST is particularly
> inefficient when it comes to handling multiple inputs with the same name.
>
> This basically mean that every in order to function
> properly needs to have a name ending in '[]'.
>
> Wouldn't it be ea
13 matches
Mail list logo