Needs work
Project:
Content Profile
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
6 Nov 2010 at 08:45 UTC
Updated:
14 Mar 2013 at 03:54 UTC
Jump to comment: Most recent file
Comments
Comment #1
marcingy commentedServices only includes code related to core - moving this to the appropriate project
Comment #2
decipheredRe-rolled as a patch.
Comment #3
decipheredLooks (unsurprisingly based on the date) that this is for an older version of Services and is not compatible with Services 3.x.
Marking as needs work. Will give it a go myself, probably next week,
Comment #4
decipheredPatch for Service 3.x integration.
Comment #5
decipheredForgot to mark as 'Needs review'
Comment #6
budalokko commentedIt worked fine for me.
Comment #7
decipheredFeel free to mark as RTBC if you think it's working fine, the code is all good and you think it should be committed.
Comment #8
decipheredUpdated patch with a new services resource to update the content profile.
Marked as needs work as the old service permission is too loose as it doesn't allow granular control, ie, a user can see any users content profile, no way to restrict to only seeing their own profile.
Same permission issue exists in the new resource as it's not something I currently have the time allocated to resolve.