On Wednesday, March 11, 2015 at 7:38:20 AM UTC-7, Anthony wrote: > > Obviously auth hasn't been defined at that point. Hard to say why without > knowing more about the app (i.e., where is this code, where is auth > defined, etc.). >
If this is the out-of-the-box style, with blog_entries in a controller (eg, accessed by http://myhost/myapp/default/blog_entries) and auth in the model, I would expect auth to be defined by this time. (Looks like a controller, having no args.) And the OP seems to be saying that a high percentage of visits occur correctly, so auth must be defined for those visits. What effect does having code in a model have on auth access? Is it just that an import is needed? /dps > On Wednesday, March 11, 2015 at 9:54:54 AM UTC-4, Mark Billion wrote: >> >> We've been very stable, but this just happened last night. Im guessing >> its a random error, but wanted to see if anyone had any thoughts. Here's >> the code.... >> >> . >> >> 6. >> 7. >> 8. >> 9. >> 10. >> 11. >> >> >> #global route to static images. >> g_im_handle = '/home/mmb21167/web2py/ba_1_1/applications/welcome/static/%s' >> @auth.requires_login() >> def blog_entries(): >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
