one is a bug. The behaviour issue I am not sure. Will fix these
tonight.
On Jun 6, 8:43 am, annet <annet.verm...@gmail.com> wrote:
> Massimo,
>
> I updated to 1.63.5 and got the updates from r992, but that did not
> solve my first problem:
>
> > auth.settings.login_url=URL(r=request,c='authentication',f='login')
> > auth.settings.login_next=URL(r=request,c='core',f='index')
> > auth.settings.logout_next=URL(r=request,c='default',f='index')
> > In 1.61.4 the first two worked, in 1.63.1, when the user logs in the
> > next page is default/index instead of core/index. Commenting the
> > auth.settings.logout_next=.. doesn't make any difference.
>
> Besides, this issue, when I expose a function from appadmin, I am
> redirected to login, when I login I am redirected
> to:http://127.0.0.1:8000/admin/default/design/cms, which cannot possibly
> be correct.
>
> I bookmarked the login page. When I login I am redirected
> to:http://127.0.0.1:8000/cms/authentication/login. Whereas I set
> auth.settings.login_next=URL(r=request,c='core',f='index')
>
> Is it possible that the issue described below has something to do with
> the user only being allowed to be a member of one group?
>
> In 1.61.4 I had the following records in my auth_membership table
> id user_id group_id
> 1 1 1
> 2 2 1
> 3 2 2
>
> Furthermore I had two controllers core.py and site.py. In these
> controllers I had functions which read like:
>
> In core.py:
>
> @auth.requires_membership('core_manager')
> def update_company():
> ...
> return dict(form=form)
>
> @auth.requires_membership('core_manager')
> def crud_address():
> ....
> return dict(form=form,records=records)
>
> In site.py:
>
> @auth.requires_membership('site_manager')
> def crud_openinghour():
> ...
> return dict(form=form,records=records)
>
> @auth.requires_membership('site_manager')
> def update_openinghour():
> ...
> return dict(form=form)
>
> When user 1 was logged in he had access to the functions in core.py (a
> core_navigation menu was displayed). When user 2 was logged in he had
> access to the functions in both core.py and site.py (a core_navigation
> and site_navigation menu were displayed) In web2py this worked all
> flawless. In web2py 1.63.1 only core.py and core_navigation work all
> right. When user 2 logs in both menu's are displayed, however, every
> time user 2 navigates to one of the functions in site.py a flash is
> displayed: Insufficient privileges.
>
> In version 1.61.4 all my update functions worked, in version 1.63.5
> the update works but the check to delete functionality doesn't, it
> issues a ticket:
>
> Traceback (most recent call last):
> File "/Library/Python/2.5/site-packages/web2py_1_63_5/gluon/
> restricted.py", line 107, in restricted
> exec ccode in environment
> File "/Library/Python/2.5/site-packages/web2py_1_63_5/applications/
> cms/controllers/site.py", line 182, in <module>
> File "/Library/Python/2.5/site-packages/web2py_1_63_5/gluon/
> globals.py", line 97, in <lambda>
> self._caller = lambda f: f()
> File "/Library/Python/2.5/site-packages/web2py_1_63_5/applications/
> cms/controllers/site.py", line 29, in update_openinghour
> form=crud.update(db.openingstijd,request.args[0],next=(URL
> (r=request,f='crud_openinghour')))
> File "/Library/Python/2.5/site-packages/web2py_1_63_5/gluon/
> tools.py", line 1609, in update
> onvalidation=onvalidation):
> KeyError: 'id'
>
> Is it possible to revert to the tools.py of version 1.61.4 in version
> 1.63.5?
>
> Kind regards,
> Annet.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
