Multi-dimensional arrays should be passed as:

array('arr[]' => array(1,2,3))

Produces:
arr[]=1&arr[]=2&arr[]=3

This is not really a useful solution... I think that fetch should accept any multi-dimensional array in $extra_parameters and do all the intelligent stuff itself.

First, how would you know whether to send 'arr=1&arr=2' or 'arr[]=1&arr[]=2' ? Not all servers behave like PHP.

Second, which service are you consuming that requires passing a multi-dimensional array?

I agree with datibbaw, it's not clear how we'd support this 
beyond PHP.

If the goal is to pass multidimensional values you should 
use a format which properly supports them, ie XML/JSON.

Can you give us some information around which API you are 
using which requires this?

- JJ

I'm just expecting that OAuth::fetch will behave like other PHP functions, eg. http_build_query is doing the right thing:

$array = array('one' => array('two' => array('three')));
echo http_build_query($array, null, '&');
// Outputs: one[two][0]=three

Leaving this open to fix the provider issues, but after that I'm closing it.

Unless there's a public API that requires passing multidimensional arrays, this is not considered a bug, though it could be mentioned in the manual I suppose.

We were going to release our public API this week but when we found this bug we figured we'd better wait and find a solution before consumer developers send bugs.

I think we will implement an option server-side an option for sending either POST arrays or JSON (which is btw the best imho), and we'll write in the documentation what kind of POST arrays we accept (and it'll be up to the developer to send something we'll understand).

What is a real bug here, is that OAuth::fetch is throwing a array to string error notice and sending to the server incomplete datas (like index=Array, weird). It should either throw an exception or do something like http_build_query, but sending the 'Array' string to the server is neither elegant nor useful for developers.

I agree, I think you should use a format which is more fit for 
the data hierarchy you are trying to represent (+1 on JSON).

- JJ

Dear friends,

Any app using Rails as backend would need to send a 
multidimensional array in POST and PUT requests.

For example, if you check the code in 2.2.2 here:
http://guides.rubyonrails.org/v2.3.8/layouts_and_rendering.h
tml#using-render
... you'll see that Rails expects an array with a 'book' 
index, containing another array. If we use nested 
attributes, we can have even another array inside it!

In other words, anyone trying to use Rails + OAuth in the 
backend wouldn't be able to use PECL::OAuth::fetch() to send 
data to the server in other format other than json (I had 
troubles using XML!).

Hope this helps to clarify the problem posted here.

Thanks for the info - JSON does seem to be the best choice for this use 
case.

- JJ

Think I still have a fix lying around to throw an exception 
whenever a multi-dimensional array is passed ... will look for 
it tonight.

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Open". Thank you.