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.

CommentFileSizeAuthor
#2 apply_endpoint-1965612-2.patch706 bytesdeciphered

Comments

marcingy’s picture

marcingy commented
Priority: Major » Normal

Please provide a patch.

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Status: Active » Needs review
StatusFileSize
new apply_endpoint-1965612-2.patch706 bytes

I 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.

kylebrowning’s picture

kylebrowning commented
Status: Needs review » Reviewed & tested by the community

really 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.

kylebrowning’s picture

kylebrowning commented
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.