It goes into a model file after auth has been instantiated. Everything in
the model is globalised as models are executed every time the app is
accessed. Example in db.py:
auth = Auth(db)
...
def user_bar():
bar = reference to auth.user to generate nav bar...
return bar
then you would
Hello Lewis,
I am having the same issue. Could you tell us where did you put the code
for the navbar?
Thanks!
Sebastian
El viernes, 20 de julio de 2012 10:35:25 UTC+2, Matt Newton escribió:
Is there a simple way to make changes to the auth.navbar() helper object?
For example, the default for
How did you solve it? I'm facing the same problem - deciding where to place
the navbar code I wrote.
On Saturday, 15 December 2012 09:09:05 UTC+5:30, Lewis wrote:
I solved this.
On Friday, December 14, 2012 3:37:45 PM UTC-8, Lewis wrote:
I understand that code and put it in my controller.
I understand that code and put it in my controller.
But, where do I put the reference to it in the view (the base view that is
extended):
By default it says: div id=navbar{{='auth' in globals() and
auth.navbar(separators=(' ',' | ',''))}}/div
I assume that user.bar must replace
I solved this.
On Friday, December 14, 2012 3:37:45 PM UTC-8, Lewis wrote:
I understand that code and put it in my controller.
But, where do I put the reference to it in the view (the base view that is
extended):
By default it says: div id=navbar{{='auth' in globals() and
Unfortunately, the navbar isn't very flexible. However, it returns an HTML
helper object (a SPAN with several components), so you can manipulate it
after creation. The part after Welcome is the second component of the
span, so:
navbar = auth.navbar()
if auth.user:
navbar[1] =
I just write my own:
def user_bar():
action = '/user'
if auth.user:
logout=A('logout', _href=action+'/logout')
profile=A('profile', _href=action+'/profile')
password=A('change password', _href=action+'/change_password')
bar = SPAN(auth.user.email, ' | ',
7 matches
Mail list logo
