0
Fixed

German message when trying to enter Theme code that already exists

Martin Georgiev 12 years ago updated by Matthew O'Riordan (Founder) 12 years ago 4
After trying to change the MAA code to SBF I got the following message. 

Image 7

Answer

Answer
Fixed
Hi Martin

Sorry this has taken so long, but it's been a difficult bug to track down.  It turns out that with the particular web server that we use in production, there is an issue whereby the locale is persisted across sessions.  On our dev and testing servers, this is not an issue.

Thanks for pointing out the issue, and I believe it should be fixed now.

Matt
Hi Martin

That is very very odd as you the locale for your account is set to GB.  May I ask, can you replicate that problem, or is it a one off.  If it's replicable it will certainly be easier to diagnose.

Thanks,
Matt
Hi Matt,

I can't replicate it. I tried again and I got the correct message. It could be a problem because it goes through a proxy which kicks me out from time to time. 

Martin
Ok,  will look into this.  The problem is very odd though because I would expect either all localisation to be German (and the headings in the Backlog would be in German), or no localisation to be German.  Oddly you have a mix of the two.  I'll route around and see if I can find the cause of it.
Hi Martin

I've tried so many things, and I just cannot replicate this error.  I am really sorry, but I'm not sure how to fix a problem I can't recreate locally.

When you are able to recreate this issue again, would you mind checking in developer tools what headers are being sent to the server in the main HTTP request, and copying them in here. Perhaps I can identify the issue from that.

Matt
Answer
Fixed
Hi Martin

Sorry this has taken so long, but it's been a difficult bug to track down.  It turns out that with the particular web server that we use in production, there is an issue whereby the locale is persisted across sessions.  On our dev and testing servers, this is not an issue.

Thanks for pointing out the issue, and I believe it should be fixed now.

Matt