[web2py] Re: Appadmin on 2.9.4
the core chapter is long, but full of gems : http://web2py.com/books/default/chapter/29/04/the-core#Static-asset-management On Saturday, March 15, 2014 9:58:10 PM UTC+1, SimonD wrote: Hi LightDot, Thanks for the info. I have a well thumbed printed 5th edition book and to be honest, this is not too well documented in there. A quick look at the 6th edition didn't help. But I will probe the 5th edition again. The reference I did find appears related to nginx, rather than Apache (I did try to get nginx running but that's another tale...). To answer your questions. I took the lead from Massimo who proposed that Chrome might highlight the non-found JS and CSS. I simply saw the missing directories as referred to in the Chrome diags and populated those that appeared missing. You rightly say that I maybe could have come to a different conclusion about the actual cause of the issue. Sorry, I didn't - oops. I simply thought the folders were missing. response.static_version never came into my mind because I simply didn't know about it (and I have been using web2py for quite a time, although I confess to being more towards the noob end of the expertise spectrum). I had installed web2py using the script supplied. It worked right out of the box, and so I thought that maybe the script had not created those directories for some reason (like permissions). Now that I know of response.static_version, I will endeavour to learn about it and deploy it properly. In summary, I really appreciate your, and all, information and hope that I can find out about response.static_version. If there are specific pointer, links or additional information you can supply, I will be, as always, very grateful. Simon On Saturday, March 15, 2014 7:35:29 PM UTC, LightDot wrote: Btw, this seems to be one of the more elusive features of web2py, when it comes to finding information about it... @simonD, can I ask what did you first think when you saw _2.9.4 in the path, but no corresponding folder? Did you assume anything else besides a missing folder? Did you search the group for answers and if so, what keywords did you use? I'm trying to figure out how should web2py it's documentation convey the information about this feature better... Regards On Saturday, March 15, 2014 8:12:22 PM UTC+1, LightDot wrote: 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
Re: [web2py] Re: Appadmin on 2.9.4
On Friday, March 14, 2014 11:19:56 PM UTC+1, Dewes wrote: Maybe in apache2, on default config you have this line: AliasMatch ^/([^/]+)/static/(.*) /var/www/web2py/applications/$1/static/$2 Change it to: AliasMatch ^/([^/]+)/static/(?:_[\d]+.[\d]+.[\d]+/)?(.*) /var/www/web2py/applications/$1/static/$2 At least that solved my problem. This makes apache ignore statics with versioning. ignore here means serving the correct file :P -- 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.
[web2py] Re: Appadmin on 2.9.4
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, shapova...@gmail.com 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) -
[web2py] Re: Appadmin on 2.9.4
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, shapova...@gmail.com 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
[web2py] Re: Appadmin on 2.9.4
Btw, this seems to be one of the more elusive features of web2py, when it comes to finding information about it... @simonD, can I ask what did you first think when you saw _2.9.4 in the path, but no corresponding folder? Did you assume anything else besides a missing folder? Did you search the group for answers and if so, what keywords did you use? I'm trying to figure out how should web2py it's documentation convey the information about this feature better... Regards On Saturday, March 15, 2014 8:12:22 PM UTC+1, LightDot wrote: 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, shapova...@gmail.com 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.
[web2py] Re: Appadmin on 2.9.4
Hi LightDot, Thanks for the info. I have a well thumbed printed 5th edition book and to be honest, this is not too well documented in there. A quick look at the 6th edition didn't help. But I will probe the 5th edition again. The reference I did find appears related to nginx, rather than Apache (I did try to get nginx running but that's another tale...). To answer your questions. I took the lead from Massimo who proposed that Chrome might highlight the non-found JS and CSS. I simply saw the missing directories as referred to in the Chrome diags and populated those that appeared missing. You rightly say that I maybe could have come to a different conclusion about the actual cause of the issue. Sorry, I didn't - oops. I simply thought the folders were missing. response.static_version never came into my mind because I simply didn't know about it (and I have been using web2py for quite a time, although I confess to being more towards the noob end of the expertise spectrum). I had installed web2py using the script supplied. It worked right out of the box, and so I thought that maybe the script had not created those directories for some reason (like permissions). Now that I know of response.static_version, I will endeavour to learn about it and deploy it properly. In summary, I really appreciate your, and all, information and hope that I can find out about response.static_version. If there are specific pointer, links or additional information you can supply, I will be, as always, very grateful. Simon On Saturday, March 15, 2014 7:35:29 PM UTC, LightDot wrote: Btw, this seems to be one of the more elusive features of web2py, when it comes to finding information about it... @simonD, can I ask what did you first think when you saw _2.9.4 in the path, but no corresponding folder? Did you assume anything else besides a missing folder? Did you search the group for answers and if so, what keywords did you use? I'm trying to figure out how should web2py it's documentation convey the information about this feature better... Regards On Saturday, March 15, 2014 8:12:22 PM UTC+1, LightDot wrote: 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,
[web2py] Re: Appadmin on 2.9.4
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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[web2py] Re: Appadmin on 2.9.4
I remember see something 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[web2py] Re: Appadmin on 2.9.4
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, shapova...@gmail.com 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [web2py] Re: Appadmin on 2.9.4
Massimo has a problem when we use the script, web2py not posing on localhost port. Ovidio Marinho Falcao Neto ITJP.NET.BR ovidio...@gmail.com itjp.net...@gmail.com Brasil 2014-03-14 11:27 GMT-03:00 Massimo Di Pierro massimo.dipie...@gmail.com: 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- 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.
[web2py] Re: Appadmin on 2.9.4
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, shapova...@gmail.com 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [web2py] Re: Appadmin on 2.9.4
Sorry I do not understand. On Friday, 14 March 2014 11:30:04 UTC-5, Ovidio Marinho wrote: Massimo has a problem when we use the script, web2py not posing on localhost port. Ovidio Marinho Falcao Neto ITJP.NET.BR ovid...@gmail.com javascript: itjp@gmail.com javascript: Brasil 2014-03-14 11:27 GMT-03:00 Massimo Di Pierro massimo@gmail.comjavascript: : 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 web2py+un...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- 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.
Re: [web2py] Re: Appadmin on 2.9.4
me neither but it may be related to static_version. A simple screenshot from firebug or chrome developers tools will tell us. On Friday, March 14, 2014 5:43:41 PM UTC+1, Massimo Di Pierro wrote: Sorry I do not understand. -- 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.
Re: [web2py] Re: Appadmin on 2.9.4
Maybe in apache2, on default config you have this line: AliasMatch ^/([^/]+)/static/(.*) /var/www/web2py/applications/$1/static/$2 Change it to: AliasMatch ^/([^/]+)/static/(?:_[\d]+.[\d]+.[\d]+/)?(.*) /var/www/web2py/applications/$1/static/$2 At least that solved my problem. This makes apache ignore statics with versioning. Em sexta-feira, 14 de março de 2014 18h11min50s UTC-3, Niphlod escreveu: me neither but it may be related to static_version. A simple screenshot from firebug or chrome developers tools will tell us. On Friday, March 14, 2014 5:43:41 PM UTC+1, Massimo Di Pierro wrote: Sorry I do not understand. -- 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.
