moosetrout wrote on 40246516-07-11

We're seeing this in 1.6.1 as well.

Milestone changed to Elgg 1.7.2 by cash on 40305969-01-14

trac user ugomatic wrote on 40475036-01-12

As a solution to this, I propose that in the case of invisible groups, the default access level is set to Group-only for all content posted on the group, over-riding both site and personal access levels. In order to keep things simple, users should be able to post in invisible groups only with the following access levels: (1) that Group, (2) private, (3) if possible, collections of friends where all friends are part of that invisible group

Group members should be made aware that they have joined an invisible group, perhaps with a pop-up notification upon accepting the invitation.

Apart from the current obvious problem with posting group activity on the river, there is a second one: even if I delete the original activity, it will still be listed on the river for all users to see.

cash wrote on 40475216-06-30

Deleting content should remove entries from the river. If you are not seeing that, please open up a separate bug report (especially if you are using the latest from the 1.7 branch in svn).

trac user ugomatic wrote on 40475393-01-01

You're right, this is a different issue - already covered by ticket #1856: http://trac.elgg.org/ticket/1856

cash wrote on 40489064-04-14

Current 1.7 branch does not display the group name or group icon, but it does display the title of the topic. Interestingly enough, the icon displayed is that of the current logged in user when the user does not have permissions for the group.

The core issue is that Elgg's permission model does not work well with containers. Anything within a container should not have more permissive access than the container itself. The access library does not do anything like this right now. Fixing this is not a 1.7.2 issue so I pushing it back to 1.8.

Milestone changed to Elgg 1.8 by cash on 40489064-04-14

Milestone changed to Elgg 1.8.1 by ewinslow on 40895147-01-16

Milestone changed to Near Term Future Release by cash on 42004300-01-04

@juho-jaakkola is this ticket not fixed by the fix of #6167 ?

@jdalsem Yes it is. Thanks for reviewing the ticket!