ahh, yes i've been playing that game with my URL calls as well. i'll keep
an eye out for places in my code that do the same. thanks!
cfh
it was this definition:
auth.messages.verify_email
= request.env.http_host+str(URL(r=request,c='default',f='user',
args=['verify_email']))+'/%(key)s to verify your email'
which I had changed from:
auth.messages.verify_email
= request.env.http_host+URL(r=request,c='default',f='user',
args=['verif
i'm curious about what that bug in db.py was that broke the dev_appserver.
if we ever get to the point where development and production environments
are exactly the same, think about how many QA jobs would be lost! ;)
cfh
ah ha!
a bug in my app's db.py was preventing dev_appserver.py from calling my task
url... sensitive chap.
these subtly differences between web2py, dev_appserver and GAE are
frustrating - I'll be happier when it's all in the cloud :)
On 2 June 2011 15:28, Carl Roach wrote:
> thanks for the feedb
thanks for the feedback.
my task is called correctly when I manually "Run" it from
http://localhost:8080/_ah/admin/tasks?queue=default
I've given the task a name (to make it unique) using a mixture of a-z0-9-
The fact that dev_appserver is failing to call the URL correctly / URL is
failing to cal
taskqueue is no longer a labs feature, but a trunk feature on GAE, so use:
from google.appengine.api import taskqueue
can you try and load the logged URL by hand in the browser? It should
follow the same URL processing and i have not had to add special routes.py
or app.yaml to make it work.
c
6 matches
Mail list logo
