Just a minor amendment to the above stuff. If you are running your livesearch on several pages (mine is on every page in my site) you might want to modify ./index.php … to /index.php …. and change the script call to /livesearch.js - that way it’ll always look from the root up and be able to find it. I had this problem momentarily on my individual entry pages since they call from the comments template.
Just fyi! =)
I am glad you brought it to my attention. With a fair bit of tweaking, this could be made into a much more general and powerful tool. Grabbing data and updating a page (without reloading the page) in real time…quite a few possibilities there. Shoutboxes…private messaging…link lists…Gmail checking…etc.
The only downside is the amount of backend work being done by using a template, but there might be ways to manage that that could be looked into.
Paul… it definitely wasn’t working on my individual pages which is why I had to go and change it. I guess because it was index.php/weblog/comments/title-of-post/ ? ./ would have been weblog no?
Changing it to / fixed it anyway - just something I had to do to make it work. =)
I think it would be fantastic if this kind of thing were eventually rolled into EE as options or whatever. Cutting edge stuff, very neat. =)
Hm, I wonder if the browser would not have seen the difference between the page and the query string, so you are likely right. My bad. A browser is not Apache after all, I suppose.
Yes, and now I have visions of wonderful JavaScript widgets available in EE. Focus! I must focus. Developer API first…
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.