(FIXED) PH Logo not working

(FIXED) PH Logo not working

Author
Discussion

jammy-git

Original Poster:

29,778 posts

213 months

Monday 19th August 2019
quotequote all
Just last week I was thinking that updates to the forum had been happening little by little and more importantly, successfully (though the smiley and quote parsing code still sucks).

But now the logo doesn't load, results in a 500 error: https://www.pistonheads.com/static/images/logo-smi....

Haltamer

2,457 posts

81 months

Tuesday 20th August 2019
quotequote all
I've been getting that; Looks like someone has knocked the logo file?

Jack Mansfield

3,256 posts

91 months

PH TEAM

Tuesday 20th August 2019
quotequote all
Sorry, I'm not 100% sure what you mean!

What are you trying to load up and from where? The link you've posted seems to be working okay for me (ie loading the logo)...

jammy-git

Original Poster:

29,778 posts

213 months

Tuesday 20th August 2019
quotequote all
Not trying to upload anything. The PH logo doesn't load....


In Chrome (76.0.3809.100) and Windows 10 with uBlock Origin turned off.

Haltamer

2,457 posts

81 months

Tuesday 20th August 2019
quotequote all


And when attempting to open the image link in a new tab



I've tried tinkering with extensions, but doesn't seem to have much impact.



And in the browser's dev tools.. (Opera)

Jack Mansfield

3,256 posts

91 months

Tuesday 20th August 2019
quotequote all
Ah I see! Thanks, I'll let the dev team know.

jammy-git

Original Poster:

29,778 posts

213 months

Tuesday 20th August 2019
quotequote all
Just tried in Firefox and the logo loads fine. So maybe an issue specific to Chrome.

mr_spock

3,341 posts

216 months

Tuesday 20th August 2019
quotequote all
Me too, broken in Chrome, works in Safari. ABP and Ghostery off, problem persists. 500 error on that URL.

Haltamer

2,457 posts

81 months

Tuesday 20th August 2019
quotequote all
Seems to be the most recent versions of chromium based browsers, as the above was from Opera on a laptop; Having the same on Chrome on a different PC.

Intrestingly, an ancient version of Chromium itself is working.

tirolo_

199 posts

110 months

PH TEAM

Wednesday 21st August 2019
quotequote all
Thanks for the feedback guys!

Apparently I'm the only one able to reproduce this in the team and it stops when I logout, if I login with another account works fine... pretty weird and still trying to figure what's the cause. Will keep you posted!

Kewy

1,462 posts

95 months

Wednesday 21st August 2019
quotequote all
Mines broken too.

Stuck it on my car but it doesn't seem to be going any faster confused

tirolo_

199 posts

110 months

Wednesday 21st August 2019
quotequote all
Kewy said:
Mines broken too.

Stuck it on my car but it doesn't seem to be going any faster confused
make sure to match it with double white stripes to increase the chances of an extra boost!

tirolo_

199 posts

110 months

PH TEAM

Wednesday 21st August 2019
quotequote all
ok I think I got it... can you guys do a hard refresh and check if it's all back to normal now please?

jammy-git

Original Poster:

29,778 posts

213 months

Wednesday 21st August 2019
quotequote all
Yup, fixed for me.

What was the issue?

tirolo_

199 posts

110 months

Wednesday 21st August 2019
quotequote all
jammy-git said:
Yup, fixed for me.

What was the issue?
we are making some major changes on the backend to open the path for further changes coming up in the near future, as one can imagine it ain't easy to change the flooring and ceiling of an old house while people are still living in it but we are trying to keep the disruption to a minimum! biggrin

jammy-git

Original Poster:

29,778 posts

213 months

Wednesday 21st August 2019
quotequote all
As a developer I was just curious to know what the specific technical reason was for the SVG path not working in Chrome but working in other browsers, especially as it was giving a 500 error rather than just not being interpreted correctly.

tirolo_

199 posts

110 months

Thursday 22nd August 2019
quotequote all
jammy-git said:
As a developer I was just curious to know what the specific technical reason was for the SVG path not working in Chrome but working in other browsers, especially as it was giving a 500 error rather than just not being interpreted correctly.
uh got it! so there's a fairly complex, multi-layered path that request has to go through in order for it to be served.... some of these layers will try to cache the response based on a variety of things (cookies, payload, headers, etc)... that said my best guess is that during deployment some of us got that response cached as an error making every subsequent request were the caching criteria would match (combination of values in the request as mentioned above) hence invalidating the cache for that resource seems to have got it fixed!

is this kind of answer you were looking for?

jammy-git

Original Poster:

29,778 posts

213 months

Thursday 22nd August 2019
quotequote all
Yup! Fantastic thanks