On a brand new D7 install, under the resources tab, some methods are listed twice for some reason. Once with a description and once without. See

https://skitch.com/gregdunlap/fs8k1/services-pantsquare

CommentFileSizeAuthor
#6 service_endpoint.txt1.46 KBgdd
#2 remove-duplicates.patch987 bytesmarcingy

Comments

marcingy’s picture

marcingy commented

Have got round to testing and I can replicate

marcingy’s picture

marcingy commented
Status: Active » Needs review
StatusFileSize
new remove-duplicates.patch987 bytes

The issue was introduced by #1241998: Refactor _services_process_resource(). Patch attatched

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented
Status: Needs review » Needs work

So this applied, however it appears that if you have ever activated and saved one of these duplicated resources, then they do not actually disappear. I did various combinations of saving and clearing cache, but the duplicates for user (the only resource I had activated) still appear. Duplicates are gone in all the other resources. Is that data getting cached or stored somewhere? Might need an update hook to clear it out.

marcingy’s picture

marcingy commented

Can you provide and export your end points as I have a feeling this may be pretty hard to fix, given we are dealing with serialised structures in the db. I would be inclined to say it is a dev we have a bug, it is now fixed you need to do X to resolve it as part of the issue. After all we are only looking at 84 installs.

kylebrowning’s picture

kylebrowning commented

sub

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented
StatusFileSize
new service_endpoint.txt1.46 KB

OK I tested this on a fresh install of services on a fresh D7 site and it is still happening. The export is attached, as you can see all the actions are also listed as relationships.

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

I just found turns out to be this same bug at #1274132: 'relationships' hard coded into loop when resources are built, although I resolved it differently and it appears to be working.

marcingy’s picture

marcingy commented
Status: Needs work » Closed (duplicate)

Marking as duplicate - note the patch in the other issue is exactly the same as this one except this makes the logic no longer require a continue.