Hello Lisa, it looks like there is an issue with the guide re. membership.remove_member (p. 102).
NOTE: This API previously allowed you to use a GET method. You should instead use POST. GETwill not work in a future release.
If I may suggest an improvement to the CV Developer guide, it'd be very useful to list the different status values that each API may return... currently it's a bit of test&try guess work to find out and handle specific status returns...
Emmanuel, I will see what I can do. Just to clarify, you want more detail on the possible return values of the Status Code.
Hi Lisa, yes this is correct...
Status code=8 -> "User already exists"
Emmanuel, I was able to correct the problem you mentioned in the updated Developer Guide regarding membership.remove_member. We will work on adding more status code values in a future update.
Thanks Lisa. I have another comment... The examples listed for cvauth.set_cookie do not work with IE8/9 at least, due to the default security policy used by IE (it rejects session cookies set in an iframe or similar, unless a particular P3P header is used by the inner page). In CV case, it blocks CV Session cookie on IEx while it works on other browsers. I think a warning or a different example in the dev guide would be useful.
Hello Lisa, there seem to be a new CV API available: user.notification which is undocumented in the CV Dev Guide. Could you provide some details on it? Thanks.
Emmanuel, there are a few APIs that have not been QA'd, and therefore are not documented. This is one of them.
A quick question. Is there a reason why "phone" is omitted from profile.get_profile_for_user. I noticed that it's not listed as an id. but it's available to set in proifle.update_user_profile and is a field in profile.
@Rob, I checked with the Developers, and those return values were accidentally omitted from the product specification. I will refresh the book shortly and add the missing return values. Thanks for bringing this to my attention!