adding web2py as left it out of the thread by mistake... On Wed, Feb 23, 2011 at 12:06 AM, Mart <msenecal...@gmail.com> wrote:
> > Hey Sebastian, > > So, I notice I skipped something... So the I meant to say... Yuu create a > "group" called 'editor', then give the users that who should be able to > edit, a membership to group editor (from table auth_memebership --> pull > down menu, choose the users one at a time). This will give some the > 'editor' privilege, and other will have read... as for your 3rd option, you > have the choice... either bloc access completely, if not logged in, or > create a "users" group,add a membership to those who should read. Anybody > else should fall in 404 error. > > Mart :) > > On 2011-02-22, at 6:13 PM, Sebastian E. Ovide wrote: > > Hey Mat, > > I've did a couple of experiments and found some add behaviour.. > > so I've created a group "editor" and created two users: "editor" and > "user". The user "editor" belongs to "editor" and the user "user" doesn't. > Then I've created 4 pages with different configurations and observed how the > wiki behaved: > > the user editor can always READ/WRITE > > 1) public, role=null > anonymous can READ > user can READ > > 2) public, role=editor > anonymous: 404 NOT FOUND > user: 404 NOT FOUND > > 3) private, role=null > anonymous: asked for login/password => after login forward to index (no > wiki) > user: 404 NOT FOUND > > 4) private, role=editor > anonymous: asked for login/password => after login forward to index (no > wiki) > user: 404 NOT FOUND > > 5) unexciting page > anonymous: asked for login/password => after login forward to index (no > wiki) > reader: 404 NOT FOUND > > > so how can I create a page (if it is already possible with the current > version) that can be EDITED by a user in editor, READ by authenticated > users and hidden to anonymous users ? > > thanks > > On Tue, Feb 22, 2011 at 5:55 PM, Martin Senecal <msenecal...@gmail.com>wrote: > >> Hey Sebastian, >> >> How are you setting up memberships? >> >> So, I think this is what Massimo intended; >> >> from auth_user table: >> 1 Sebastian >> 2 Pierre >> 3 Guy >> 4 Manon >> >> then, you can go to auth_memebership and create a new membership called >> 'editor' (notice Massimo uses singlular to define group and table names - >> just his preference, because it codes nicer ;) ) >> >> once you type your new auth_membership name, you add members form the >> auth_user table (the drop down points to them already), you just add the >> ones you want to give 'editor' privileges to. Other users can be left as is. >> When users loggin, and go to a wiki page where you set the privileges, the >> wiki will know all about what the logged in user can or can not do. >> >> then in plugin_wiki, >> >> there are those 2 settings >> if "active" then everyone can see it, if not only "editor" members >> can (but I think everyone can see the menu item regardless). >> >> This should work.. >> >> >> Also, yes it would nice to manage all those privileges in one spot and >> have different levels and possible combinations of "rights" vs "privileges". >> I think otherwise, expanding those permissions would be to use >> auth_permission (if getting started with that, I would suggest making a copy >> of you app and playing in there to start with - I wish I had ;) ) >> >> Hope it helps >> >> Mart :) >> >> >> >> >> >> >> On Tue, Feb 22, 2011 at 12:21 PM, Sebastian E. Ovide < >> sebastian.ov...@gmail.com> wrote: >> >>> Hi Mart, >>> >>> that is what I'm trying to do... some editors, some people with read only >>> access (logged in people) and rest with not any right... still could not get >>> it work.. >>> >>> assigning a user EDITOR to the groups EDITORS and setting a page as NO >>> public and with role EDITORS will grant access to EDITORS but nobody will >>> read it (bug here: users wont read it but will be able to open to editor >>> !!!!) >>> >>> I guess that the plug in would need a EDIT ROLE and WRITE ROLE... >>> >>> On Tue, Feb 22, 2011 at 4:48 PM, mart <msenecal...@gmail.com> wrote: >>> >>>> I think the idea is to create groups... >>>> >>>> I.e. >>>> group 'editor' --> can do stuff >>>> group 'users' --> can read stuff >>>> >>>> But, if the page's permissions are set to "open" & "active", and you >>>> have yourself in the "editor" group, then you will be able to edit, >>>> and users will be able to see (without having to create group "users") >>>> >>>> At least, that's how its working out for me... >>>> >>>> >>>> Hope it helps, >>>> Mart :) >>>> >>>> On Feb 22, 11:27 am, "Sebastian E. Ovide" <sebastian.ov...@gmail.com> >>>> wrote: >>>> > actually only the user that has created the page can see the menu >>>> PAGE. >>>> > >>>> > so userONE creates a page (public, active, with no roles) ... he can >>>> see it >>>> > and any other user can see it... but only userONE can see PAGES from >>>> the >>>> > menu. >>>> > >>>> > if userTWO tries to open /myapp/plugin_wiki/index he will get; Not >>>> > authorized >>>> > ACCESS DENIED >>>> > >>>> > On Tue, Feb 22, 2011 at 3:53 PM, Sebastian E. Ovide < >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > sebastian.ov...@gmail.com> wrote: >>>> > > Hi All, >>>> > >>>> > > I've created a public page and as expected I can see it even if I'm >>>> not >>>> > > logged in. Nevertheless the menu PAGE is not visible if I'm not >>>> logged in. >>>> > >>>> > > Is it working as expected ? >>>> > >>>> > > thanks >>>> > >>>> > > -- >>>> > > Sebastian E. Ovide >>>> > >>>> > -- >>>> > Sebastian E. Ovide >>>> >>> >>> >>> >>> -- >>> Sebastian E. Ovide >>> >>> >>> >>> >>> >> > > > -- > Sebastian E. Ovide > > skype: sebastian.ovide > > > -- Sebastian E. Ovide skype: sebastian.ovide +353 (0) 87 634 0149
