#7028 severely stunted landing page html after vagrant install
closed
General
2015-08-20
2014-01-06
Anonymous
No
Originally created by: tuinstra
Followed the instructions on "Install and Run Allura - Vagrant" page. All steps appeared to work, and I was able to connect to localhost:8080, but what was there was extremely incomplete. See attached "All Neighborhoods.html" ... that's all there was.
The HTML contents here are correct (there's not a lot of content) but I'm guessing it was all unstyled? The CSS wasn't working? That is an issue we've seen before. The CSS files send the wrong content-type on the very first request and then the browser refuses to use the CSS since it's not "text/css". If you clear your browser cache or use a different browser, it should work okay from then on.
It's not a simple fix for the root bug, unfortunately. A bit more info about the bug at: http://mail-archives.apache.org/mod_mbox/incubator-allura-dev/201308.mbox/%3CCAFKJ1Ww9qgmyozHmxXw-MMZjK7mhaw0Y7xA7Fqty3dOj9P5f1Q%40mail.gmail.com%3E
Originally by: tuinstra
Thanks, Dave, that was it. I finally got the page after clearing the cache in Chromium, but neither clearing the cache nor private browsing worked in IceWeasel/Firefox.
This should probably be documented in the "Install and Run Allura - Vagrant" page, at the end of the "Connect to the VM and start Allura" section. Perhaps "If you see a page that looks like it's lacking CSS formatting, try clearing your browser cache and reloading the page, or using a different browser (more information on this problem here)." ... with the last word linked to the bug you cite. Not knowing this cost me about a day.
I wonder if the race condition gets triggered by the low latency when hosting Allura in a VM on a local machine. Perhaps artificially inducing some latency somewhere might be a (grotesque but useful) workaround.
Commit in branch db/7028 to add an informative message when this happens