New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Critical: Broken CSS #456

Closed
passsy opened this Issue Dec 4, 2017 · 12 comments

Comments

Projects
None yet
3 participants
@passsy

passsy commented Dec 4, 2017

The website is currently unusable

screen shot 2017-12-04 at 22 39 46

@chalin chalin self-assigned this Dec 4, 2017

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 4, 2017

Collaborator

The site looks fine when I load it.
Can you empty your browser cache and reload to see if the problem persists?

Collaborator

chalin commented Dec 4, 2017

The site looks fine when I load it.
Can you empty your browser cache and reload to see if the problem persists?

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 4, 2017

Collaborator

Which browser and OS are you using?

Collaborator

chalin commented Dec 4, 2017

Which browser and OS are you using?

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 4, 2017

Collaborator

I'm not seeing the problems that you report. I've tried Safari and Chrome (on both desktop and mobile iOS and Android).

Collaborator

chalin commented Dec 4, 2017

I'm not seeing the problems that you report. I've tried Safari and Chrome (on both desktop and mobile iOS and Android).

@passsy

This comment has been minimized.

Show comment
Hide comment
@passsy

passsy Dec 4, 2017

Tried it in Chrome and Safari on macOS. Same on Android

media-20171204

passsy commented Dec 4, 2017

Tried it in Chrome and Safari on macOS. Same on Android

media-20171204

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 4, 2017

Collaborator

Thanks for checking.

At the bottom of site pages, you'll see a tool icon:

screen shot 2017-12-04 at 18 31 11

If you hover over the tool icon, what build info do you see? I see
Site built on 2017/12/04 19:18 UTC.

Collaborator

chalin commented Dec 4, 2017

Thanks for checking.

At the bottom of site pages, you'll see a tool icon:

screen shot 2017-12-04 at 18 31 11

If you hover over the tool icon, what build info do you see? I see
Site built on 2017/12/04 19:18 UTC.

@passsy

This comment has been minimized.

Show comment
Hide comment
@passsy

passsy Dec 4, 2017

It says Site built on 2017/12/04 19:18 UTC
xfd0favdeg

passsy commented Dec 4, 2017

It says Site built on 2017/12/04 19:18 UTC
xfd0favdeg

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 4, 2017

Collaborator

Wow, same build! How strange. I'll rebuild and redeploy to see if that helps.

cc @kwalrath @kevmoo

Collaborator

chalin commented Dec 4, 2017

Wow, same build! How strange. I'll rebuild and redeploy to see if that helps.

cc @kwalrath @kevmoo

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 4, 2017

Collaborator

@passsy, I've forced a rebuild and redeploy of the site. Could you please try reloading it again, and then let me know what the build information is? Thanks.

Collaborator

chalin commented Dec 4, 2017

@passsy, I've forced a rebuild and redeploy of the site. Could you please try reloading it again, and then let me know what the build information is? Thanks.

@passsy

This comment has been minimized.

Show comment
Hide comment
@passsy

passsy Dec 4, 2017

Chrome and Safari are working now with Site built on 2017/12/04 23:40 UTC.
I still get the error on Android in Chrome.

passsy commented Dec 4, 2017

Chrome and Safari are working now with Site built on 2017/12/04 23:40 UTC.
I still get the error on Android in Chrome.

@passsy

This comment has been minimized.

Show comment
Hide comment
@passsy

passsy Dec 4, 2017

Error is gone on Chrome in Android as well after attaching the inspector. This probably diabled the cache.

passsy commented Dec 4, 2017

Error is gone on Chrome in Android as well after attaching the inspector. This probably diabled the cache.

@passsy passsy closed this Dec 4, 2017

@chalin

This comment has been minimized.

Show comment
Hide comment
@chalin

chalin Dec 5, 2017

Collaborator

Thanks again for having reported this. We'll try to get to the root cause.

Collaborator

chalin commented Dec 5, 2017

Thanks again for having reported this. We'll try to get to the root cause.

@kwalrath

This comment has been minimized.

Show comment
Hide comment
@kwalrath

kwalrath Dec 18, 2017

Member

This seems to be a CDN issue. A workaround is to purge the URL in your region:

curl -X PURGE <URL you want>
Member

kwalrath commented Dec 18, 2017

This seems to be a CDN issue. A workaround is to purge the URL in your region:

curl -X PURGE <URL you want>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment