I'm not sure if you're agreeing or disagreeing with me ;^) but I have largely done away with the web2py base.css and built my own from scratch, so if the old web2py_ajax.html was tied to the base.css, that might explain why my ajax calls weren't working. With my newly installed web2py_ajax.html, I've now got everything working, including some things I've been waiting years to do, and I'm pleased as punch.
On Oct 11, 3:27 am, Iceberg <iceb...@21cn.com> wrote: > On Oct11, 12:24pm, weheh <richard_gor...@verizon.net> wrote: > > > > > So caveat emptor: if you're working on ajax, make sure your views > > folder has an updated version of web2py_ajax.html. > > > In general, this may be an issue about releasing newer versions of > > web2py because the apps aren't updated automatically. Perhaps the ajax > > include should be one level up from apps? > > Perhaps not. An old app works with old web2py_ajax.html (and its > corresponding style.css etc.), but not necessarily with the latest > web2py_ajax.html (and its corresponding base.css etc). > > In other word, web2py_ajax.html and those css and js files are within > app level, which means a good thing - they can evolute without > affecting old apps, and a bad thing - you need to migrate to latest > web2py_ajax.html manually. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
