Massimo, maybe I didn't write clearly. I don't think there's much more to explain. Essentially, I followed exactly the ajax search technique in Chapter 3 of the book.
The view of search was the simplest (as shown above). The controller function for search was taken from the book. The ajax function (bg_find) was simply modified to get search the correct field in my database, but it is also taken from the book. So I think the error has to do with web2py. Here are two pictures of http://mydomain.com/search/ (note the backslash "/") 1. This picture shows the search page using the default template: http://i.imgur.com/Sy3rH.png 2. This picture shows the outcome after I started typing something in the search box. http://i.imgur.com/KMZOP.png It seems what gets displayed is not the return of the ajax function (bg_find), but rather the same page. I got the error with http://mydomain.com/search/ or with passing in arguments like this http://mydomain.com/search/abc I think it's the exact bug as reported in this topic: http://www.google.com/url?sa=D&q=http://groups.google.com/group/web2py/browse_thread/thread/9707f3d66d859893/5785831e673afd2b%3Flnk%3Dgst%26q%3Dajax%2Bsearch%235785831e673afd2b&usg=AFQjCNFTj0Hph4zaLwY0_jVOS6BJwcoj6w On Dec 25, 1:33 pm, mdipierro <[email protected]> wrote: > please explain more. > > On Dec 25, 12:07 pm, VP <[email protected]> wrote: > > > of course, layout.html is web2py's base template, unmodified. I think > > this is a bug. > >
