This is a proposal for me to write a helper back end component for JUGA that will effectively allow the access control over articles to be applied at the section and category level avoiding the need for updating the JUGA site items each time an article is added.
When adding an article - say a blog entry - JUGA requires the addition of at least two and possibly five site items to access it :-
Assume the article ID is 555:
First there is the back end access :-
We need a backend item for
where we let administrators access the article. That is probably it for the back end unless you want special editing rights there.
If only it were as simple for the front end. Here we need to add :-
where we put the groups who can read the article, and
where we put the groups who can edit the article on the front end.
On a real site, articles are being added several times daily by a variety of users who will find this a rather big headache. Things will be forgotten. Users will be unhappy.
Its generally the case that the desired settings for these site items can be inferred from the section and category to which the article is being added. For example 'Brochure' section articles would be public, whereas 'Site documentation' articles would be restricted to Staff etc.
I propose writing a JUGA Helper back end component to set up tables with the groups who can do the jobs to the sections and categories as follows :-
Have an update_site_items plug in that uses these tables to:
Run the function as a plug in after new content is submitted (and when the above tables are changed).
This will effectively provide support for setting the groups on the basis of the sections and categories at the expense of being able to apply it to individual articles.There is a rough cut of the component here. I'll do some more work on it when time permits. Let me know if its useful or works (its working OK on an embedded site but I haven't had time to test the zip) by commenting here.
Australia: 07 3103 2894
International: +61 410 545 357