I had a probably similar problem that I solved by patching pydal.
See https://github.com/web2py/pydal/issues/403
<https://github.com/web2py/pydal/issues/403#issuecomment-238115508> and
https://github.com/web2py/pydal/pull/404.
However, as mention in the issue thread, the change shall be done in
web2py.
Alas, I did not have time to try to reproduce with a more recent web2py.
If you use a recent web2py and the dal PR#404 solves the problem for you,
then I propose that you open a new bug in web2py.
Best regards,
-Mathieu
On Thu, Sep 22, 2016 at 9:17 PM Jacinto Parga <jpar...@gmail.com> wrote:
> The same error when I try to register an user: Unable to send email.
>
>
> Mail.send failure:coercing to Unicode: need string or buffer, lazyT found
>
> I don't know what to do
>
>
> El domingo, 31 de julio de 2016, 8:36:02 (UTC+2), Massimo Di Pierro
> escribió:
>
>> OK. will check this today.
>>
>> On Friday, 29 July 2016 15:40:26 UTC-5, webm...@trytha.com wrote:
>>>
>>> Nope, same error in: 2.14.6-stable+timestamp.2016.05.10.00.21.47 (the
>>> source code off the web2py site).
>>>
>>> If you want me to try a nightly or something, let me know.
>>>
>>> The only semi-unique thing about my app is that I allow usernames for
>>> login as well. Here is my default/user():
>>>
>>> def user():
>>>
>>> db.auth_user.first_name.writable = False
>>> db.auth_user.last_name.writable = False
>>>
>>> # NOTE: This is an addition I found that enables using usernames
>>> (default is email as login).
>>> if 'login' in request.args:
>>> db.auth_user.username.label = T('Username or Email')
>>> auth.settings.login_userfield = 'username'
>>> if request.vars.username and not IS_EMAIL()(request.vars.username)[1]:
>>> auth.settings.login_userfield = 'email'
>>> request.vars.email = request.vars.username
>>> request.post_vars.email = request.vars.email
>>> request.vars.username = None
>>> request.post_vars.username = None
>>>
>>>
>>>
>>> return dict(form = auth())
>>>
>>> Everything was working fine in 2.12.2, but I can't say for certain it
>>> was working in my 2.13 deployment.
>>>
>>>
>>>
>>>
>>> On Friday, July 29, 2016 at 6:26:11 AM UTC-7, Massimo Di Pierro wrote:
>>>>
>>>> This may have been fixed already. Can you upgrade and try it?
>>>>
>>>> On Friday, 29 July 2016 00:49:14 UTC-5, webm...@trytha.com wrote:
>>>>>
>>>>> I just uploaded an updated version of web2py to my server, replacing a
>>>>> much older version (likely 2.12.2), and now it won't send password
>>>>> recovery
>>>>> emails. The error in the logs is:
>>>>>
>>>>> Mail.send failure:coercing to Unicode: need string or buffer, lazyT
>>>>> found
>>>>>
>>>>> This suggests to me that somehow a string is not properly being
>>>>> passed. I gather that lazyT has something to do with the built-in
>>>>> translation capabilities of web2py? Probably don't need to be translating
>>>>> email addresses (though I guess it could be trying to translate the
>>>>> recovery message). Either way, GAE wants nothing to do with it.
>>>>>
>>>>> How can I fix 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 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 web2py+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
