O > The issue isn't simply whether there have been changes in the file but >> whether there have been changes in the file that are directly linked to >> changes in the core framework. web2py.js includes code that depends on >> particular HTML classes and data-* attributes generated by web2py HTML >> helpers and widgets, so sometimes changes in the core framework are coupled >> with changes in web2py.js and the two must therefore be upgraded in tandem. >> This is less likely to be the case with other app-specific files. For >> example, you can upgrade appadmin.py and appadmin.html, but the old >> versions should generally continue to work with new versions of the >> framework. It's probably worth upgrading web2py_ajax.html as well. >> > > This just reinforces my point... Perhaps these files (and any others?) > should be managed as part of the framework, and not as part of an > application. >
I agree. It's just a matter of figuring out a good mechanism. It's tricky with static assets, as often we want to bundle them. > Ok. I see. However, in a production environment I do not exactly want to > have the welcome app enabled... Which means that this kind of link should > actually NOT work... > Good point. I suppose you could use your web server or routes.py to redirect all "welcome" requests (except those to /static). Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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/d/optout.
