aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorfriendica <info@friendica.com>2014-10-28 19:29:37 -0700
committerfriendica <info@friendica.com>2014-10-28 19:29:37 -0700
commitd9c5823593400ec82ce7e547a1a0c9674aa1f248 (patch)
tree386d43064aa9f168c394ed594e3e5bf95c0a0ce4
parent653305889c26bc493a985675f35e179abde1ea0a (diff)
downloadvolse-hubzilla-d9c5823593400ec82ce7e547a1a0c9674aa1f248.tar.gz
volse-hubzilla-d9c5823593400ec82ce7e547a1a0c9674aa1f248.tar.bz2
volse-hubzilla-d9c5823593400ec82ce7e547a1a0c9674aa1f248.zip
the default permissions for new connections when using a custom role is inadequate. Until we can make it configurable start off with something like a public social role. We're typically taking the person straight to the connection editor so they can change it before any privacy damage is done
-rw-r--r--include/follow.php6
1 files changed, 5 insertions, 1 deletions
diff --git a/include/follow.php b/include/follow.php
index 14385d90d..20fd7f5fc 100644
--- a/include/follow.php
+++ b/include/follow.php
@@ -66,7 +66,11 @@ function new_contact($uid,$url,$channel,$interactive = false, $confirm = false)
if($is_red && $j) {
- $my_perms = PERMS_W_STREAM|PERMS_W_MAIL;
+
+ // fixme - we need to be able to define these somewhere for the custom role
+ $my_perms = PERMS_R_STREAM|PERMS_R_PROFILE|PERMS_R_PHOTOS|PERMS_R_ABOOK
+ |PERMS_W_STREAM|PERMS_W_WALL|PERMS_W_COMMENT|PERMS_W_MAIL|PERMS_W_CHAT
+ |PERMS_R_STORAGE|PERMS_R_PAGES|PERMS_W_LIKE;
$role = get_pconfig($uid,'system','permissions_role');
if($role) {