Loading Profile...
Yipes, missing stylesheet?
It appears that the CSS isn't loading on any of the # pages. I've attached a screengrab from what may appear obvious to the team at this time. Hope this helps.
I’m flabbergasted
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Scott, This seems to be indeed related to the stylesheets not loading. Did you try to shift reload? I do not run into the same problem. Are you able to load: http://s3.feedly.com/production/1.2.9...? Are you able to access http://s3.feedly.com?
-
Inappropriate?It appears I can now - that was such a weird hiccup.
I should have noted earlier that I did indeed clear the cache with a shift return, but at the time to luck. Thanks for the S3 URLs, at least I can check to see if those are live before escalating - thanks!
I’m relieved
1 Comment
Add a comment
This answers the question
-
Scott. Thanks for the heads up. Escalating is fine. It allows use to know that the service we are using to serve static content is down and allows us to follow up with them. -
Inappropriate?I observed this behavior earlier as well (and took a screenshot, see below). I then restarted my browser. I don't know if it is related, but after restarting that problem was gone and I noticed that the version number was now 1.2.94 (build 2154). When the problem occurred earlier the version was 1.2.95 (as in Scott's screenshot).
However, with the "new" 1.2.94, the minibar formatting is messed up a bit. Unfortunately the fireshot plugin doesn't capture the minibar when I take a screenshot, so I can't post it.
2 Comments Add a comment
This answers the question
-
Thanks Phil. I am not sure why you are running 1.2.94. You should have been automatically patched to 1.2.95. I think that the problem described here is related to the service we use for static content having a kick up today.
-
I've restarted and am back to 1.2.95. Seems fixed now.
-
Inappropriate?Update: we increase our internal server capacity and moved the static content back inside our farm land. The initial load should be tiny bit slower but we now control the end-to-end experience and we should no longer see any CSS problem going forward.
EMPLOYEE
EMPLOYEE
