My plugins for controlling content access needed updating because Elgg 1.2 changed views/default/input/access.php; therefore, they no longer worked. I have made the appropriate changes to:
- nopublic
- nopublicwithfeeds
- allpublic
In the near future I will also update higherwalls.
The real news here may be how the plugins will be housed and supported. I uploaded the plugins to a wiki that also gives information about the use, configuration, and installation of these and other plugins that I have created. There will also be a link to a discussion forum offering support for specific plugins.
The plugins are available here. Please be aware that both the wiki and the forum are in early stages of development.
Related Posts
Tags: allpublic, Elgg, forum, nopublic, nopublicwithfeeds, plugins, wiki
-
Somebody has been working hard … well done Steve.
I have a suggestion regarding plugins.
Installing plugins is easy, but operating some of them is not so.
Over at phpbb they put an installation difficulty level with each mod, perhaps it would be appropriate to put an operational difficulty level at the beginning of each ‘read me’ that accompanies a plugin.
I’m thinking of plugins like kevins excellent form and flexprofile for example.
A brilliant set of plugins but probably beyond the grasp of users that want/expect to plug’n'play.
Whether it would be appropriate for you to put such guidance up at the plugin repository I don’t know.
I’m just kinda throwing an idea into the pot here, I don’t have anywhere near the level of experience as people like you and kevin but I’ll help where I can.
Best wishes to you and yours
-
Sounds like a good idea to me. Any other suggestions are welcome.
Believe me though, I am not in the same category as Kevn! I’m not even close!
-
-
Thanks Steve for all your hard work. As someone who is just learning Elgg, some of your comments on the challenges of figuring out how to do stuff certainly rings true. Thanks for creating the beginnings of what hopefully will be another resource for us that is complimentary to what the Curverider guys are doing.
I’m very strongly attracted to Elgg because of the incredible flexibility and control given to administrators and developers. However, figuring out how stuff works is a challenge at best and more often a series of experiments with confusing results. I look forward to a growing body of documentation to help.
Access is one thing that I really want to control for the site I’m building. I appreciate your various examples. Do you know whether the access options can be controlled dynamically, or is access.php only called “once in a while”? For example, I might want to identify some users as teachers and others as students. Teachers could set access as public and students couldn’t. I think I can figure out how to write the conditional statements around that and modify the array as you’ve shown in your excellent examples, but would this even work? Or differently, I might say that files can only be shared with collections of friends while blog posts can be shared more broadly. Again, I could probably muddle through how to build the conditional statements, but will this even work?
Thanks again,
Russ
-
I’m glad my blog has helped. Please contribute any of knowledge you acquire in your experiments. If we all do that, there will be a tremendous body of knowledge.
Regarding access, I think you will find this post interesting:
http://openedweb.com/blog/2008/11/06/language-override-plugin/
The meat of access control is not so much in views/default/input/access.php as it is in engine/library/access.php.
When trying to create these plugins, I originally focused on that file, but for the life of me (I’m sure it is obvious to others–so chine in), I could not find the hook and create an override for that file. Finally, I was pointed in the direction of the views directory and was able to make this work.
Can it work? I believe so. I believe that fleshing out access control is a key to the wider success of Elgg. Furthermore, an administrative interface would very desirable. It may be a good idea to create an access control forum in the developers’ section of the forum and such an area in the wiki as well. This way many could collaborate more easily rather than wading through the unorganized posts in the Google Groups.
-
-
Hi Steve, the link for the new allpublic plugin in your Wiki is not working.
-
Thanks for the heads up. It should work now!
-
-
Hi Steve
When using your nopublic plugin (version 1.2) I still see RSS and OpenDD links on some pages. I stil see the links on the following pages: Blogs, Files, Tidypics, groups, browse (members), friends etc. etc.
Maybe it easier if I list the pages where it do work: profileview, event_calendar and messages.I have deleted the rss and opendd directories from /view/default/…
Can you help me out, because I can’t find the place where I can remove the links for good.
And thumbs up for your work, it has inspired me to start developing my own plugins.
-
Indeed, there is a problem. I will look into it and have resolution no later than this weekend. This plugin is critical to what I plan to do.
I didn’t test it very extensively and just updated a few elements to reflect changes between versions of Elgg. Thanks for the heads up!
-
Reply
Creative Commons License
Openedweb by Stephen J. O’Connor is licensed under a Creative Commons Attribution 3.0 Unported License.
8 comments
Comments feed for this article
Trackback link: http://openedweb.com/blog/2008/12/24/content-access-plugins-updated/trackback/