New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACCESS_PRIVATE should be a real ACL #8073
Comments
what would be the added gain? As for each user you would add 2 db rows (1 for access collection, 1 for access collection membership). On large communities this would add a lot of rows to the db. |
Example use case: The Showcase sites are private until validated. If admin adds a comment "You need to change X before I can validate this" to a showcase site, the showcase owner doesn't see it at all because the commend inherits the ACCESS_PRIVATE but Elgg considers it to be private for the admin not for the site owner. |
Also comments and discussions, if you have an entity with comments, and you make that entity private - as a non-admin you lose any of the comments as they inherit private access but in relation to the comment owner. |
@beck24 is this something you're going to get to soon (i.e. for 2.0?) |
This isn't looking like it will make it for 2.x. Feel free to add back to milestone if you disagree... |
Moving this to Elgg 6. Priority is not that high, but impact is very large. We already have a few very high impact changes in Elgg 5. |
Much like ACCESS_FRIENDS and for the same reasons (namely inheritability): #5038
Each user would have an access collection containing only themselves. This would be the access_id stored on anything private to them and anything that inherits that access.
The text was updated successfully, but these errors were encountered: