On Monday, September 11, 2017 at 5:31:32 PM UTC-7, [email protected] wrote: > > Today I came across some unusual behaviour in web2py when I tried to > install a compiled web2py application. Coming home I decided to see if I > could replicate the same problem on my Mac (running macos Sierra) and found > some equally unusual behaviour. > > *The problem can be easily demonstrated:* > > [skipping to the end] > 5. The original uncompiled ‘welcome’ application still works but the > compiled version of the same application gives: > > invalid view (default/index.html) > > Obviously all of this is done on the same (i.e. one) machine with the same > web2py version, Python etc and yet the compiled version will not work but > the uncompiled version will. > > Am I missing something obvious? > > My first thought is that a file got skipped in packaging.
In the new (or re-born) application , the newapp/views/default directory should include "index.html", and it seems that for some reason it doesn't. If you copy that one file from "welcome" to "newapp", does it fix the app? The packed version is just a zip file, AIUI, with a different extension. If the file copy fixed the broken app, then it should be possible to see if the file made it into the zip. If it did not, that suggests a packer problem. If it did, perhaps an unpacking problem. Dave /dps -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
