I think it would be good to keep this as simple as possible.<br>One super-user who can do everything and possibility to restrict/allow access to created page by choosing user/users.<br><br>(*the following might differ from your goals*)
<br>What if all the elements were similar to "render component"?<br>That way it would be possible to _build_ custom cms. Cms-pages would be just like the other pages, but with restricted access.<br>Superuser would just place components on the right pages and give access to the page to right users.
<br><br>I did 2 ajax render components for fun. They worked pretty well. One was for adding posts and one for uploading images. Static version would then be used on the front end. I had to modify the code a bit, so that it passes rest of the url (the part that it didn't recognize as pages) to the component. That way the component could show a certain post based on the id. Ajax-versions didn't need that of course.
<br><br>(*cms worth looking*)<br>I tried Rubricks CMS today. It looks really flexible, but the UI wasn't clear. Drag'n'Drop works well and user management seems good.<br><pre><a href="http://rubricks.org/index_en.html" rel="nofollow">
http://rubricks.org/index_en.html</a></pre><br>-- Heikki<br><br><div><span class="gmail_quote">2006/4/17, Martin Scheffler <<a href="mailto:martinscheffler@googlemail.com">martinscheffler@googlemail.com</a>>:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div style="direction: ltr;">Hi all,<br><br>I took a look at various methods for authentication and ownership handling.
<br><br>Could you tell me what your ideas for authentication are?<br>
I would go like this:<br>
Three roles: admin, designer, editor<br>
Editor can only edit content and pages<br>
Designer can also edit templates<br>
Admin can also edit element types and users<br>
<br>What kind of permission system do we need for pages and content? Do we need any at all? <br>In all my previous projects I never had any use for fine-grained access control, every user could edit every page. What do you think?
<br><br>This is the stuff I found:<br><br><span style="font-weight: bold;">UserStamp plugin</span><br><a href="http://www.delynnberry.com/pages/userstamp/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.delynnberry.com/pages/userstamp/</a><br>The Userstamp Plugin extends
<em><a href="http://api.rubyonrails.com/classes/ActiveRecord/Base.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ActiveRecord::Base</a></em> to add automatic updating of <em>created_by</em> and
<em>updated_by</em> attributes of your models in much the same way that the
<em><a href="http://api.rubyonrails.com/classes/ActiveRecord/Timestamp.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">ActiveRecord::Timestamp</a></em> module updates <em>created_(at/on)</em>
and <em>updated_(at/on)</em> attributes.<br>Could be useful, have to take a closer look
<br><br><span style="font-weight: bold;">LoginEngine+UserEngine: </span><br>simple, wide-spread usage, tested, takes long to install?<br><br><span style="font-weight: bold;">ActiveRBAC<br></span><a href="https://activerbac.turingstudio.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
https://activerbac.turingstudio.com</a><span style="font-weight: bold;"><br></span>Authentication with more fine-grained role handling, role inheritance model, groups. Seems to be pretty new. I got it to work without problems.
<br><br><pre><font style="font-weight: bold; font-family: arial,sans-serif;" size="2">Mac Engine<br></font><font style="font-family: arial,sans-serif;" size="2"><a href="http://www.ruby-forum.com/topic/61145#new" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.ruby-forum.com/topic/61145#new<br></a></font><font style="font-weight: bold; font-family: arial,sans-serif;" size="2"><br></font>to provide finer grained control over ActiveRecord results than can be<br>achieved by using user_engine. The intention is to provide filtering of
<br><br>results and assigning permissions to users/groups over what they can<br>access.</pre>Didn't really take a look at it, but is described as alpha software<br></div><div style="direction: ltr;"><span class="sg"><br>Martin
<br>
</span></div><br>_______________________________________________<br>Adminpages-development mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:Adminpages-development@rubyforge.org">Adminpages-development@rubyforge.org
</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://rubyforge.org/mailman/listinfo/adminpages-development" target="_blank">http://rubyforge.org/mailman/listinfo/adminpages-development</a><br><br>
</blockquote></div>