This is related to the issue found here: http://drupal.org/node/967786

The patch in that issue has *created* the issue (at least in the beta2 version).

I.E I'm using beta 2, and querystrings are being ignored...e.g. Making a GET request to /node?page=1 will return the default (page=0) results.
Reverting the change in the patch, (changing 'params' back to 'param'), allows querystrings to be used.
Not sure why this change was made, as it can be seen in /services/resources/node_resource.inc in the function _node_resource_definition() that all of the source items in the args array are keyed with param, and not params.

Ah, after another look at the Services codebase, the confusion may have come from services.services.api.php, where the usage comment states:

" - source: Where this argument should be retrieved from. This can be
* 'data' (indicating the POST data), 'params' (indicating the query
* string) or 'path' (indicating the url path)."

This is going to add confusion for developers of new modules, and this confusion and development is probably the reason for the patch - it'll work for the custom module, but will have broken the core services resources.

Could the documentation be changed and the patch be reverted?

Cheers

Comments

gdd’s picture

Status: Active » Closed (duplicate)