view.html
{{extend "layout.html"}}
{{for q in question:}}
{{q=XML(q.quest.replace('\n','').replace('(','{').replace(')','}'),
sanitize=True)}}
{{pass}}
{{for a in answer:}}
{{a=XML(a.message.replace('\n','').replace('(','{').replace(')','}'),
sanitize=True)}}
{{pass}}
* {
Sorry , I was taking a shortcut to avoid posting much code.
Here it is, a different app still with the same issue..
def index():
return locals()
@auth.requires_membership('managers')#->this gives an erros bout q not
being defined in view_searches
def my_notes():
So it caching selects to disk or redis supposed to only work if you have
uniquely named fields? It doesn't seem to make a difference if I set
cachable=True or not.
On Tuesday, April 3, 2018 at 5:15:25 PM UTC-5, Brian M wrote:
>
> Further investigation shows that cache.redis plays nicely with
>
> @auth.requires_login()#membership('managers')->this gives an errors bout q
> not being defined in view_searches
> defnotes():
> dbhealth.health.id.readable = False
> g = SQLFORM.grid(dbhealth.health, searchable=True, csv=False,
> user_signature=True, )
> return dict(form = g)
>
Shouldn't this warrant a new release? The last stable release is 2.16.1 and
the import is missing there.
On Saturday, December 16, 2017 at 3:47:06 PM UTC-6, Massimo Di Pierro wrote:
>
> fixed on gitghub. thanks for reporting it.
>
> On Thursday, 7 December 2017 06:26:33 UTC-6, Ryan Herbert
Oh, I see, you made a good point there, I hadn't realised.
I guess I will have to take a closer look to my app code. Considering that
the problem exists in specific accounts while others work ok, and
considering also that the problem happens with any request that that
specific user makes to
Model:
dbhealth = DAL('sqlite://wellness.db',folder='/home/maurice/web2py')
dbhealth.define_table( "health",
Field('name', 'string'),
Field('definition', 'text', length= 100,
default="We'll update soon.", notnull=True),
>
> @auth.requires_login()
> def notes():
> dbhealth.health.id.readable = False
> g = SQLFORM.grid(dbhealth.health, searchable=True, csv=False,
> user_signature=True, )
> return dict(form = g)code
> question = db(db.answers.author == auth.user.id
>
My app has been ok with these code;
In controller:
@auth.requires_login()
def notes():
dbhealth.health.id.readable = False
g = SQLFORM.grid(dbhealth.health, searchable=True, csv=False,
user_signature=True, )
return dict(form = g)code
question = db(db.answers.author ==
So you might consider explaining what you try to achieve so we surely can
propose you some other, maybe better, way.
Richard
On Fri, Apr 6, 2018 at 3:06 PM, Luis Sucuc wrote:
> Mi propósito es editar los datos de usuario desde un formulario diferente
> a SQLFORM. Ya lo
Mi propósito es editar los datos de usuario desde un formulario diferente a
SQLFORM. Ya lo hago, pero necesito mostrar el número correcto de '' en
el input de contraseña, pero entiendo que no lo puedo hacer. ¡Gracias!
El viernes, 6 de abril de 2018, 12:21:05 (UTC-6), pbreit escribió:
>
>
On Friday, April 6, 2018 at 10:58:56 AM UTC-4, Lisandro wrote:
>
> Yes, in fact, I've been running that SQL command to check for locks, and
> sometimes I see that lock on other tables, but that other locks live for
> less than a second. However, when the problem happens, the lock on the
>
If the purpose is to impersonate support a user, web2py provide tool to do
it
http://web2py.com/books/default/chapter/29/09/access-control#Authentication
It explained at the end the Authentication seciton from the link above.
Richard
On Fri, Apr 6, 2018 at 2:29 PM, Leonel Câmara
Also, please don't start saving passwords in clear text to go around this.
--
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
You cannot. Passwords are actually one-way hashed, not encrypted. This is
by design so that the password can never be figure out even if your
database and code are compromised. What happens is that the password the
user enters is hashed in the same way and the result is compared to what is
in
How can I decrypt a password from the auth_user table?
user = db(db.auth_user.id == user_id).select().first()
print user.password
# --output--
#
pbkdf2(1000,20,sha512)$8d7c80fb77386465$532cd8dd495f703337cf3c261a01801b3155f36c
--
Resources:
- http://web2py.com
- http://web2py.com/book
Yes, in fact, I've been running that SQL command to check for locks, and
sometimes I see that lock on other tables, but that other locks live for
less than a second. However, when the problem happens, the lock on the
auth_user and web2py_session tables remains there for the whole 60 seconds.
Hi Anthony, again, thank you very much for your time, I really appreciate
it.
El jueves, 5 de abril de 2018, 17:52:36 (UTC-3), Anthony escribió:
>
> On Thursday, April 5, 2018 at 2:57:20 PM UTC-4, Lisandro wrote:
>>
>> Thank you Anthony, yes I'm aware of that.
>> I use it like that for this
18 matches
Mail list logo