All apps are separate and they do not talk to each other by default, except that the wiki asks admin if the current user is the administrator.
On Friday, 8 February 2013 06:28:44 UTC-6, Michael Beller wrote: > > Thank you! That was it. > > I was testing using multiple tabs within one browser. I was logged into > admin on one tab and was testing using another tab (using multiple accounts > with different group memberships). I assumed that since they were > different applications that would be ok. > > This raises the question: if I had multiple applications within one web2py > site and an end user was using both within the same browser would their > credentials work properly, i.e., does this only create a problem for the > admin site? > > On Thursday, February 7, 2013 2:30:32 PM UTC-5, Massimo Di Pierro wrote: >> >> Not every user is added to wiki_editor. Only if the user is logged into >> "admin". >> >> You are probably testing this by logging out from the app and creating >> multiple accounts. You need to do this while not logged into admin. I agree >> that this behavior is annoying when testing but if a user a a system >> administrator and can edit the app, he should be able to edit the content >> as well. >> >> On Thursday, 7 February 2013 11:15:39 UTC-6, Michael Beller wrote: >>> >>> Thank you for the clarification but I don't think that addresses the >>> problem that every new user is added to wiki_editor group. I saw >>> earlier in this thread there was a fix but I'm still experiencing that >>> problem. Is there something else I should check? >>> >>> On Thursday, February 7, 2013 11:32:30 AM UTC-5, Massimo Di Pierro wrote: >>>> >>>> The documentation needs to be fixed. There are two different >>>> "everybody". >>>> >>>> In Wiki if you set manage_permissions=True you can use a group >>>> "everybody" to set permissions on wiki pages. This group is not really >>>> created but just a dummy. It tells the wiki the page can be accessed by >>>> everybody. >>>> >>>> In Auth there is the concept of an "everybody" group but auth does not >>>> create it for you. You can do: >>>> >>>> g = db.auth_group(role='all people'): >>>> if g: >>>> gid = db.auth_group.insert(role='all people') >>>> else: >>>> gid = g.id >>>> auth.settings.everybody_group_id = gid >>>> >>>> Notice that in this case the role/name is irrelevant and, in fact, I >>>> used "all people" instead of everybody. >>>> >>>> On Thursday, 7 February 2013 06:33:16 UTC-6, Michael Beller wrote: >>>>> >>>>> I noticed in the documentation that there should also be an >>>>> 'everybody' group (which I did not have). I thought that maybe if that >>>>> group did not exist users are added to 'wiki_editor' by default but >>>>> adding >>>>> 'everybody' group did not fix the problem. >>>>> >>>>> Anybody else having this issue? >>>>> >>>>> On Tuesday, February 5, 2013 5:38:51 PM UTC-5, Michael Beller wrote: >>>>>> >>>>>> I'm still having this error in 2.3.2 >>>>>> >>>>>> Every new user is added to wiki_editor group. Even if I remove the >>>>>> user from the group, the user still has access to the wiki menu (I've >>>>>> specified menugroups - see below) and when the user logs out and logs in >>>>>> again they are automatically added back to the wiki_editor group. >>>>>> >>>>>> I have the following statement in my model after auth.define_tables: >>>>>> >>>>>> auth.wiki(resolve=False, manage_permissions=True, >>>>>> menugroups=['wiki_editor','wiki_author']) >>>>>> >>>>>> On Thursday, November 8, 2012 5:25:43 PM UTC-5, Massimo Di Pierro >>>>>> wrote: >>>>>>> >>>>>>> Please open a ticket. Will fix this tonight. >>>>>>> >>>>>>> On Thursday, 8 November 2012 14:50:51 UTC-6, Dragan Matic wrote: >>>>>>>> >>>>>>>> I can confirm and replicate this bug, the same happens on windows >>>>>>>> binaries and on ubuntu with source with latest stable version - 2.2.1. >>>>>>>> >>>>>>>> Here are the steps to replicate the bug: >>>>>>>> >>>>>>>> 1. create new app >>>>>>>> 2. create new page (default/wikipage.html) and controller that >>>>>>>> returns auth.wiki(manage_permissions=True) >>>>>>>> 3. go to wikipage, I am now redirected to user login >>>>>>>> 4. register first user, go to default/wikipage >>>>>>>> 5. create first wiki page, accept defaults and submit >>>>>>>> 6. logout, register second user >>>>>>>> 7. go to appadmin, check auth_membership table, second user is not >>>>>>>> a member of wiki_editor >>>>>>>> 8. with second user visit default/wikipage >>>>>>>> 9. go to appadmin, check auth_membership table, second user has now >>>>>>>> automatically become a member of wiki_editor >>>>>>>> >>>>>>>> >>>>>>>> On Thursday, November 8, 2012 5:23:24 PM UTC+1, Massimo Di Pierro >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> The rule is the first user to register is also a wiki_editor. This >>>>>>>>> should not happen for other users. If it happens it is a bug. Can you >>>>>>>>> confirm this is working as intended? >>>>>>>>> >>>>>>>>> On Thursday, 8 November 2012 08:00:31 UTC-6, Dragan Matic wrote: >>>>>>>>>> >>>>>>>>>> I am doing an auth.wiki(manage_permissions=True). >>>>>>>>>> >>>>>>>>>> Basically, I want to have a wiki writer and a wiki_reader who >>>>>>>>>> will not be able to edit wiki posts. Two users (reader and writer) >>>>>>>>>> are >>>>>>>>>> registered and two groups are automatically opened (user_1 and >>>>>>>>>> user_2). For >>>>>>>>>> every wiki post user_1 and user_2 are set to read it and only user_1 >>>>>>>>>> can >>>>>>>>>> edit it. However, whenever wiki reader logs in, a row is >>>>>>>>>> automatically >>>>>>>>>> inserted into auth_membership table which maps wiki_reader user to >>>>>>>>>> wiki_editor group, so he can also edit posts. Is this a bug or is >>>>>>>>>> there a >>>>>>>>>> way to set a user to be a wiki reader only? >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> Dragan >>>>>>>>>> >>>>>>>>> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
