Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The following is what I have found to be the fix.
In services/includes/services.resource_build.inc, Line 170
- $resource[$class][$op]['endpoint'] = empty($cop['endpoint']) ? array() : $cop['endpoint'];
+$resource[$class][$op]['endpoint'] = empty($cop['settings']) ? array() : $cop['settings'];
Thanks.
Comment | File | Size | Author |
---|---|---|---|
#2 | apply_endpoint-1965612-2.patch | 706 bytes | Deciphered |
Comments
Comment #1
marcingy CreditAttribution: marcingy commentedPlease provide a patch.
Comment #2
Deciphered CreditAttribution: Deciphered commentedI spent much to time on this issue, I assumed there must be more to it as the fix was just to simple. However, a simple answer is better than no answer.
Find patch attached.
Comment #3
kylebrowning CreditAttribution: kylebrowning commentedreally all of this code needs ot be cleaned up because its confusing.
Are we doing something with the endpoint? Or settings for the endpoint? Why then is it going into an index array with 'endpoint' if it is SETTINGS.
I tried to fix this once and it broke a lot of things.
Unfortunately im slammed on other things so I cant really look at the larger 'semantic' issue but this looks good to me.
Comment #4
kylebrowning CreditAttribution: kylebrowning commented