url needs to be a valid url.
Documentation is ok, but if you "hardcode" fixed values you need to be sure
that the routes are always exactly as in your development server.
If you're not messing with default applications and/or redirection, the
same code that ran on lighttpd needs to run on nginx.....
To be sure your app will work no matter what redirection you use, use
always urls generated with URL() ....
ajax('{{=URL('echo')}}', etc etc etc)
Il giorno lunedì 13 maggio 2013 14:16:48 UTC+2, Jose ha scritto:
>
>
>
> El lunes, 13 de mayo de 2013 06:13:38 UTC-3, Michele Comitini escribió:
>>
>> Hi José,
>>
>> Please open an issue about this on https://code.google.com/p/web2py/
>> tnx
>> mic
>>
>>
> Hi Michele
>
> This is a problem of web2py or documentation [1] or deployment?
>
> ajax(url, [name1, name2, ...], target)
>
> Url is mentioned as an argument, but no examples.
>
> {{extend 'layout.html'}}
> <form>
> <input name="name" onkeyup="ajax('echo', ['name'], 'target')" />
> </form>
> <div id="target"></div>
>
> Before I had it running on Cherokee and worked fine when I switched to
> nginx, and that failed.
>
> José
>
> [1] http://www.web2py.com/books/default/chapter/29/11#The-ajax-function
>
--
---
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/groups/opt_out.
