The access control in Elgg is nice, but for my users, I know it will be too confusing. So I installed the AllPublic (edit access.php so only option is "Public.") plugin and revised it so only "Logged In Users" was available. Then I simply deleted the dropdown list form element (stupid move).
I thought, stupidly, that created content access would default to "Logged in Users". I was wrong, for some reason it defaults to private. So I searched for every instance of "access_id = 0" and changed it to "access_id = 1." This did not work. Then upon reading this, I tried adding that bit of code in my allpublic plugin. Again, no change, content still defaults to private.
I am guessing that I cannot simply delete the dropdown form element from access.php. I noticed in its code a mention of disabling. How is this done?
Considering my dillema, any suggestions? My users' content should always be available to logged in users only, and so they should not even be aware of that option.
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
have you looked at walled garden or higher walls ? to fence in your site content.
I suggest that you wait until Elgg 1.5, which has a site default access level you can set.
of course you could always over-ride the access pull down with a hardcoded hidden field.
not a big coder, how do i do that?
and would that ensure all created content to be access_id = 1?
;-) s.l.o.p.p.y of me -- forgot re: new elgg being incubated @ "v1.5" -- I wonder which older plugins will be made redundant by v1.5 new func`s ?
the problem i see is: hidden field requires an input type, something that should be on access.php, but that i cannot find.
i don't have time to wait for 1.5, any suggestions on implementing this hidden field idea? look at access.php, i don't see where it could apply.
If you search through the core trac, you'll see a patch that I submitted that changes the access code for every core function and plugin. You can use that to find the places to set access. The title of it was something like "sitewide default access permissions".
Cash,
I looked through your patch documentation and I have a few questions. I'm no expert so please excuse my asking of anything that is obvious.
Does your patch make the access control dropdown invisible?
How do I install this patch?
figured it out, the trick is editing the correct file in each plugin's action folder:
for example, in mod/blogs/actions/edit.php
i had to change:
to:
that will overide anything submitted from any form. i don't know what any of it means, especially "int", but that's fine. I think this will work.
- Previous
- 1
- 2
- Next
You must log in to post replies.