More generally, we should probably make it more clear that web2py.js is properly a part of the framework and must be upgraded whenever the framework is upgraded (this could be mentioned here<http://web2py.com/books/default/chapter/29/14#Upgrading>, and maybe a reminder message could be shown in admin when its upgrade button is used).
Anthony On Wednesday, June 26, 2013 7:36:07 AM UTC-4, viniciusban wrote: > > I think this is a note that must be highlighted before releasing as > stable, right? > > On Wed, Jun 26, 2013 at 7:14 AM, Massimo DiPierro > <mdip...@cs.depaul.edu <javascript:>> wrote: > > There is a major change upcoming in web2py 2.6 (which can be tested in > trunk). > > > > The change involves a better rewrite of web2py.js agreed upon the > developers and implemented by Niphlod. > > > > Because of this change applications which use components will break > unless you upgrade the old web2py.js with the new one. > > > > Anyway, try the latest trunk, check it out, and send us comments. > > > > Massimo > > > > > > -- > > > > --- > > 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+un...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- --- 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/groups/opt_out.