From 0039ccf38265e7d200bd311cb1a5cc2eecdc3dbf Mon Sep 17 00:00:00 2001 From: gerhard6380 Date: Sun, 7 May 2017 21:43:29 +0200 Subject: [PATCH] applied documentation convention --- doc/api.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/api.md b/doc/api.md index d1f2ebc86b..2cf4cee001 100644 --- a/doc/api.md +++ b/doc/api.md @@ -790,8 +790,10 @@ On error: * allow_cid/allow_gid/deny_cid/deny_gid (optional): on create: empty string or omitting = public photo, specify in format '``````' for private photo; on update: keys need to be present with empty values for setting a private photo now to public -both calls point to one function for creating AND updating photos. Saves data for the scales 0-2 to database (see above for scale description). Call adds non-visible entries to items table to enable authenticated contacts to comment/like the photo. -Client should pay attention to the fact that updated access rights are not transferred to the contacts. i.e. public photos remain publicly visible if they have been commented/liked before setting visibility back to a limited group. Or: previously limited photos remain limited even if changed to publicly visible. +both calls point to one function for creating AND updating photos. +Saves data for the scales 0-2 to database (see above for scale description). +Call adds non-visible entries to items table to enable authenticated contacts to comment/like the photo. +Client should pay attention to the fact that updated access rights are not transferred to the contacts. i.e. public photos remain publicly visible if they have been commented/liked before setting visibility back to a limited group. Currently it is best way to inform user that updating rights is not the best way, offer a solution to add photo as a new photo with the new rights. #### Return values