Closed (fixed)
Project:
Services
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
17 Oct 2012 at 22:38 UTC
Updated:
30 Nov 2012 at 19:33 UTC
Jump to comment: Most recent file
Comments
Comment #1
blueminds commentedLooking at the latest repo version, this is not the case anymore and can confirm that relationships can be again addressed by non-numeric identifiers.
Comment #2
miqmago commentedStill happening on 3.2
RESTServer.inc line 606
Comment #3
miqmago commentedHere it goes the patch
Comment #4
ygerasimov commentedThis change looks good to me.
Comment #5
kylebrowning commentedlets double check the tests pass and maybe write a new test to validate this?
Comment #7
marcingy commentedThe patch as is won't allow for the value 0 which the pervious patch did, so while fixing one issue it is causing a regression in another. Likely needs to be if (!numeric .... && !empty)
Comment #8
kylebrowning commentedComment #9
kylebrowning commentedwhy not just isset()
?
Comment #10
marcingy commentedYes an isset will work
Comment #11
kylebrowning commentedFixed in dev.