>
> May I ask how did you figure out? I mean, did you already know about that
> jquery stuff, or did you made some search with the parameter's names?
>
Just did a Google search with some of the parameter names and found that
Reddit post.
> P/D: I looked in the web2py's website and I didn't f
OMG! Anthony you really rock man!!
Thanks **a lot**
That's exactly what's going on, and it explains the error being so sporadic.
Definitely, I'll transform the request.get_vars before passing it to URL()
in order to avoid the error.
May I ask how did you figure out? I mean, did you already know
>
> This is a login button, present in the layout, so it's in every page:
>
> LOGIN
>
> The url of the login button uses the vars argument to pass the "_next"
> key. The _next key contains the current url (with current request.args and
> request.get_vars).
>
Check out
https://www.reddit.com/r/
Sorry for the delay on this, I wanted to make a second full review.
I confirm that there is no call to URL() in my code that uses vars argument
with a 'title' key. I checked all the included and extended files.
However, I have these lines to point out, because they seem a bit
"suspicious" to me,
>
> I see that there is a 'title' key in the list_vars, but those vars are
> related to urllib.
>
list_vars is a local variable within web2py's URL() function -- it contains
the keys/values passed in via the "vars" argument. So somewhere there must
be a call to URL() with those values. Are you
Thanks for pointing out that part Anthony.
I see that there is a 'title' key in the list_vars, but those vars are
related to urllib.
I mean, how do they arrive as keys to that function? I can't figure it out.
In the ticket details, when I click the "code" button related to my view,
it shows a
Looks like in your call to URL, the vars dictionary includes:
'title': u'Eva de Dominici pos\xf3 como una chica Guess y cont\xf3 sus tips
beauty'
Notice that the title is a unicode object. If the title is the only item
that might be unicode, you can simply encode it before passing it to the
UR
Sorry about that, the image quality was reduced after uploading it.
Here I made a new screen capture and uploaded it to my drive account, so
It's full quality:
https://drive.google.com/file/d/0B0y0m_8LgjGIT3hCU000T0hQamM/view?usp=sharing
But the character you noticed was just some noise in the im
On Thursday, December 22, 2016 at 8:32:16 AM UTC-8, Lisandro wrote:
>
> Hi there, sorry for the delay, I was waiting for the error to occur.
> Today the error triggered again, and I had disabled tickets2email, so I
> have the ticket, but it doesn't show any code, its odd.
>
Using my magnifying
Hi there, sorry for the delay, I was waiting for the error to occur.
Today the error triggered again, and I had disabled tickets2email, so I
have the ticket, but it doesn't show any code, its odd.
Here is a screen capture of the error ticket detail.
Not sure if a screen capture is the best way, b
Note, it is line 971, not 917. In the admin app, you can view the Python
code of the compiled view in the error ticket.
Anthony
On Tuesday, December 20, 2016 at 6:31:37 PM UTC-5, Lisandro wrote:
>
> Thank you all for the help.
>
> @Anthony, sorry my ignorance, I was looking in the wrong place (l
Thank you all for the help.
@Anthony, sorry my ignorance, I was looking in the wrong place (looking in
the module, asuming the error was triggered there).
Considering your answer and the traceback error, I say "ok, the error is
triggered from the view, in the line 917".
But how do I know which i
Issue appears to have come up a few times on stack overflow.
http://stackoverflow.com/questions/9942594/unicodeencodeerror-ascii-codec-cant-encode-character-u-xa0-in-position-20/9942885
On Tuesday, December 20, 2016 at 2:08:00 PM UTC-5, Dave S wrote:
>
>
> On Tuesday, December 20, 2016 at 10:3
The traceback refers to line 971 in the compiled view (not in a module),
indicating a call to the URL() function on that line.
On Tuesday, December 20, 2016 at 1:33:18 PM UTC-5, Lisandro wrote:
>
> Thanks for the quick answer.
> Yes, I have automated my app with a function; it sets the app in
>
On Tuesday, December 20, 2016 at 10:33:18 AM UTC-8, Lisandro wrote:
[...]
> Does the ticket store info about the content of vars and args when the
> error triggered?
> I'm sending tickets2email, so I don't conserve the original ticket, but If
> I could find that info in the ticket, I guess I
Thanks for the quick answer.
Yes, I have automated my app with a function; it sets the app in
mantainance mode (message for the public), updates the code from
repository, compiles the app, restarts uwsgi, and turns off mantainance
mode.
Just in case, I've just checked and it is running compiled
Which line is 971? Are you sure you re-compiled the app after making the
code change?
On Tuesday, December 20, 2016 at 6:38:07 AM UTC-5, Lisandro wrote:
>
> Hi there!
> I have a web2py application running, it's been running for a long time, it
> is a website that serves hundreds of thousands of
17 matches
Mail list logo
