niphold, what do you mean when you say opening directly the URL that fails?
On Thursday, January 31, 2013 1:10:18 AM UTC-8, Niphlod wrote: > > did you try opening directly the url that is failing through ajax ? that > 404 could be originated by an incorrect/mispelled url. > > On Thursday, January 31, 2013 12:36:56 AM UTC+1, [email protected] wrote: >> >> We just started using web2py where I work. We created our 1st webpage >> and it uses JSON calls: One to retrieve database info and the second to >> status the selected info. We created a 2nd screen using the 1st as a >> template. On the 2nd screen, our JSON call to retrieve database info >> works. However, the 2nd JSON call to perform the status won't work. It >> returns the following: >> >> *errMsg =Requested page not found. [404]* >> *status =error* >> *errorThrown =NOT FOUND* >> *xhr.status= 404* >> >> The HTML, jQuery and Python code are very similar to the working screen. >> The one difference is that we are using an *.ajax* call instead of a * >> .post* because I couldn't figure out how to write the error handling for >> the .post statement. Also, I read somewhere that *.post* calls *.ajax*so it >> really shouldn't matter >> >> What else should we look at besides the error code and text? >> >> Is there an example .html and .py file with JSON calls that we can look >> at? >> >> I've searched the web for Javascript, web2py, jQuery and JSON examples >> and tried dozens of example but we can't figure out why this call won't >> work. >> >> Is there something else we should be looking at? >> > -- --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
