Solved in two different ways.
1. Must have done something dumb, but it works to put a custom auth.bar in
a model, menu.py is a good one. This worked:
def user_bar():
if auth.is_logged_in():
logout = A('Logout', _href = URL('full', 'user', args='logout'))
profile = A('Profile
Tried putting the function in a model and calling the return value in the
view. Didn't work.
I think what is confusing me is use of two different controller files.
Certainly easy to reference actions when used in menus and anywhere in
code just using the URL function. But, this auth code nee
Sure, if I called it already. To do so, might make most sense to put in a
model.
But, I was hoping that the view would call it. There is another path
through the app with very simplified pages that uses its own auth and I
expect most users to follow that path. so, only folks editing content
It seemed a good idea to break up a large controller file into two. Now I
have default.py and full.py.
User() is in full.py. So, now my views are broken because auth won't work
to create the auth links in the navbar.
The default views reference auth as: {{='auth' in
globals() and auth.navbar
4 matches
Mail list logo
