Er... creating folders is NOT the solution. You don't have any folders missing.
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. Search the book and this group for response.static_version, it's been explained several times. Regards On Saturday, March 15, 2014 7:12:18 PM UTC+1, SimonD wrote: > > Thanks to all other contributors. > Massimo nailed it, I think, with the proposal to use Chromes diagnostics. > I must get properly acquainted with Chrome... > > The core problem was: a folder missing under admin/static (called _2.9.4). > Although I think the other Apache config solution may have worked, creating > the missing folder seemed the best course of action. > > For interest, this is the content of the missing folder. > _2.9.4: > css > js > plugin_multiselect > plugin_statebutton > > _2.9.4/css: > bootstrap_essentials.css > bootstrap.min.css > bootstrap-responsive.min.css > calendar.css > > _2.9.4/js: > calendar.js > jquery.js > web2py.js > > _2.9.4/plugin_multiselect: > jquery.multi-select.js > multi-select.css > start.js > > _2.9.4/plugin_statebutton/css: > bootstrap-switch.css > > _2.9.4/plugin_statebutton/js: > bootstrap-switch.js > > Again, thanks to all. > > > > On Friday, March 14, 2014 4:28:51 PM UTC, Massimo Di Pierro wrote: >> >> Can you open the page with chrome? In the javascript console (under >> network activity) it will tell you which files return a 404 error (if any). >> Then you can check if the files are there or not. >> >> On Friday, 14 March 2014 11:06:09 UTC-5, SimonD wrote: >>> >>> Thanks, >>> The vhost configs (I assuming that we are talking about >>> sites-available/default ?), is as per the setup script as kindly included >>> in web2py. It is unchanged apart from the installation directory (i.e. >>> other than www-data). I have changed all references of www-data to a new >>> directory name. I guess these all resolve OK, because the server works as >>> expected in every other respect. I am pretty sure it is not a permission >>> issue as they are the same across the whole directory. >>> It just looks like there is a missing CSS or JS or similar. The only >>> 'vhost' reference is in apache2.conf but thats just a log file name. >>> Actually, the Welcome Hello World screen looks fine at >>> welcome/default/index. But clicking through to admin/default/index is where >>> the issue starts presenting. Note the top black navbar is not showing >>> (although there seems to be a navbar reference in the page source), so >>> maybe part of the layout include is not being served. Does admin require >>> different includes? >>> is there anything specific I should I look for in the conf files? (I am >>> not an apache expert) >>> Thanks >>> >>> >>> On Friday, March 14, 2014 2:34:15 PM UTC, [email protected] wrote: >>>> >>>> I remember seeing something similar on previous version, IIRC the thing >>>> was in apache's vhost config. >>>> >>>> On Friday, March 14, 2014 4:27:04 PM UTC+2, Massimo Di Pierro wrote: >>>>> >>>>> Anybody else experiencing this? >>>>> >>>>> On Friday, 14 March 2014 06:39:08 UTC-5, SimonD wrote: >>>>>> >>>>>> Hello, I have seen a previous post on an apparently broken Admin >>>>>> screen, but I think this is a different issue (or just a noobie >>>>>> question). >>>>>> I have done my app development on 2.3.2 (on Ubuntu 10.04 LTS). >>>>>> I have setup a new local server (test production) on my LAN, with a >>>>>> clean/fresh install of Ubuntu 12.04 LTS. I downloaded 2.9.4 and used the >>>>>> 'setup-web2py-ubuntu.sh' script for Apache2. I copied my app over (it is >>>>>> still using SQLite for now), and updated web2py.js, appadmin.py and >>>>>> appadmin.htms as per the release notes. My actual web-application seems >>>>>> to >>>>>> work fine on the server. >>>>>> >>>>>> But, from my 10.04 machine, when I access the 12.04 server's appadmin >>>>>> (over the LAN) via SSL, the layout/design of the screens is lost. See >>>>>> the >>>>>> example screenshot. The "admin login", "installed applications", and >>>>>> "edit" >>>>>> screens are broken. >>>>>> Although not consistently, this also breaks the appadmin on my local >>>>>> 10.04 machine. Clearing history/cache etc etc in Firefox usually >>>>>> corrects >>>>>> the issue. >>>>>> >>>>>> However, I has also upgraded my 10.04LTS development environment to >>>>>> 2.9.4 and although the app admin screens were not broken in the same >>>>>> way, >>>>>> the "Manage" buttons were not working (i.e. the dropdown "edit, about, >>>>>> etc" >>>>>> options don't show). Again usually clearing the firefox history/cache >>>>>> corrects that. But restarts were required on 2 occasions. OK, its not a >>>>>> biggie, but there is something underlying that is worrying. >>>>>> >>>>>> For now, I have reverted to 2.3.2 (on 10.04 LTS) to continue >>>>>> development (although I prefer the newer appadmin environment). >>>>>> >>>>>> Actually, I don't intend to use Appadmin on the production server (as >>>>>> per the recommendations). My concern is that the appears to be an HTML, >>>>>> CSS, Boostrap or JS issue around 2.9.4 - and am concerned it might >>>>>> impact >>>>>> the production server for users. >>>>>> I am afraid I don't have the depth of expertise to nail it, so am >>>>>> looking for pointers, please. >>>>>> >>>>>> As a side note, I saw a similar "loss of appadmin layout" when using >>>>>> pythonanywhere about 9 months ago, so I am guessing (hoping) this is a >>>>>> known gotcha. >>>>>> >>>>>> Any ideas on what is causing these appadmin layout issue? >>>>>> >>>>>> BTW - I have firefox 20.0 >>>>>> Many thanks, as always. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- 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.
