As I just wrote in another thread: the _2.9.4 comes from *virtual* static asset management. This number will change now and then, as static files get updated, so please don't go creating actual folders for this.
This feature is defined with response.static_version, it's in the book and the troubleshooting in regards to it has been addressed several times in the group. This seems to be one of those features that users have most problems finding information about... Regards On Saturday, March 15, 2014 6:18:50 PM UTC+1, horridohobbyist wrote: > > Sorry, I spoke too soon. While the visual rendering is okay, the menus > don't work. So I can't create the _2.9.4 folder. Damn. > > > On Saturday, 15 March 2014 13:08:36 UTC-4, horridohobbyist wrote: >> >> Okay, I solved the other piece of the mystery. The Administrative >> Interface view is now referencing its CSS, JS, and plugins in a folder one >> level deeper called "_2.9.4". So I simply created a _2.9.4 folder and moved >> css, js, plugin_multiselect and plugin_statebutton into it. Everything is >> now okay. >> >> But this begs the question: Why wasn't my test VM doing the same thing >> with respect to the _2.9.4 folder?? >> >> >> On Saturday, 15 March 2014 12:48:33 UTC-4, horridohobbyist wrote: >>> >>> Okay, I figured out what happened. During the "One step production >>> deployment", *for some reason*, the wsgihandler.py file did NOT get >>> copied to the web2py parent folder. Don't ask me why. (In my test VM, the >>> wsgihandler.py file did get copied, in fact, moved. Go figure.) >>> >>> Now, I'm finding that the Administrative Interface cannot locate the CSS >>> for proper rendering. Any ideas? >>> >>> (Why is "One step production deployment" going so wrong???) >>> >>> >>> On Saturday, 15 March 2014 07:57:59 UTC-4, horridohobbyist wrote: >>>> >>>> I'm trying to reinstall web2py on my Linux server. I'm trying to start >>>> from a clean slate... >>>> >>>> First, I've updated my server to Ubuntu Server 12.04. I've restored the >>>> original *httpd.conf* (empty file) and *sites-available/default* files >>>> for Apache2. So, for all intents and purposes, web2py is gone from my >>>> system. >>>> >>>> Then, I removed all things web2py from the */home/www-data* folder. So >>>> I have a clean slate, right? >>>> >>>> Finally, I followed the "One step production deployment" recipe. So, >>>> the thing should just work, right? >>>> >>>> Except, it doesn't. Visit http://67.213.70.250/welcome and you get >>>> nothing, /welcome Not Found. >>>> >>>> Um, what's wrong? >>>> >>>> This worked just fine in my Linux VM, so I am puzzled. >>>> >>> -- 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.
