When you install web2py from the zip, there is a file called web2py/NEWINSTALL. When this file is found (even if empty), web2py rebuilds welcome.w2p.
On Sunday, 6 May 2012 09:02:36 UTC-5, Alan Etkin wrote: > > Well, here's the thing: > The timing options *are* in the web2py.js file in hg trunk, inside > applications/welcome, it's just that they are not updated in my local > welcome.w2p file. So, if admin uses this .w2p file when creating a new app, > I will have an outdated version of the scaffolding application (is this > correct?). How should I fix this issue. > > On Saturday, May 5, 2012 11:11:52 PM UTC-3, Massimo Di Pierro wrote: >> >> Please do. >> >> >> On Saturday, 5 May 2012 19:34:02 UTC-5, Alan Etkin wrote: >>> >>> I've found something on the subject. web2py.js function web2py_component >>> time and times arguments and the code related with js timing were not >>> included in the last version of the script. I think this should be fixed >>> for backwards compatibility (LOAD at compileapp.py builds web2py_component >>> commands with those arguments). Should I submit a patch for this?. >>> >>> On Saturday, May 5, 2012 8:23:26 PM UTC-3, Alan Etkin wrote: >>>> >>>> I am having trouble using the LOAD timing features i.e: >>>> >>>> LOAD(f="action.load", timeout=1000, times="infinity", ajax=True) >>>> >>>> The component is loaded just the first time and it should keep >>>> reloading it on each second. >>>> >>>> I've tried the command with the last trunk hg version. Anyone with the >>>> same issue? >>>> >>>> The system info: >>>> web2py Version 1.99.7 (2012-05-05 09:00:54) dev (with rocket web server) >>>> Browser: Firefox 10.0 >>>> OS: Mandriva GNU/Linux 2010.2 >>>> >>>>
