search

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

Many pages of the website are unavailable #2906

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Many pages of the website show "We're sorry but that page could not be found." 
when accessing them:
http://fritzing.org/developer/setting-your-build-envirnoment/
http://fritzing.org/shop/donations/
http://fritzing.org/parts/
http://fritzing.org/learning/
http://fritzing.org/services/
http://fritzing.org/support-us/
http://fritzing.org/forum/thread/413/?page=all
http://fritzing.org/about/
http://fritzing.org/about/publications
http://fritzing.org/fritzing-creatorkit/

This happens both when logged in or logged out of the website.

These pages may be available to some people as this comment suggests:
http://code.google.com/p/fritzing/issues/detail?id=2905#c5

Original issue reported on code.google.com by kipla...@gmail.com on 29 Jan 2014 at 1:46

GoogleCodeExporter commented 9 years ago 
This may be already fixed, but not yet deployed on the live site.

Original comment by irasc...@gmail.com on 29 Jan 2014 at 5:43

GoogleCodeExporter commented 9 years ago 
I have tested loading http://fritzing.org/support-us/ on a Mac with different 
applications and the problem appears to be a schrödinbug.

Firefox 26.0: OK
Chrome 32: OK
Safari 7.0.1: "We're sorry but that page could not be found."
wget 1.15: 404 NOT FOUND
curl 7.30.0: "We're sorry but that page could not be found."

Original comment by kipla...@gmail.com on 30 Jan 2014 at 12:19

GoogleCodeExporter commented 9 years ago 
I found it! There seems to be a bug in your website if the browser send an 
Accept-Language header which doesn't include english.

curl http://fritzing.org/support-us/ -s -o /dev/null -v
-> HTTP/1.1 404 NOT FOUND

curl http://fritzing.org/support-us/ -s -o /dev/null -v -H "Accept-Language: en"
-> HTTP/1.1 200 OK

Original comment by kipla...@gmail.com on 31 Jan 2014 at 5:54

GoogleCodeExporter commented 9 years ago 
Could the website maintainer have a look at this issue?

Original comment by kipla...@gmail.com on 11 Feb 2014 at 7:46

GoogleCodeExporter commented 9 years ago 
Hi kiplantt, thanks a lot for tracking this down!
It seems that this is related to the django-page-cms module, which is serving 
these pages (https://github.com/batiste/django-page-cms/). 
I applied an update which you can try out at 
http://blue.fritzing.org/support-us/ etc. But it's still showing the same error 
(although I'm getting a 500 instead of a 404).
Would you have any idea from where to tackle this issue?

Original comment by andre.knoerig@gmail.com on 14 Feb 2014 at 3:32

GoogleCodeExporter commented 9 years ago 
In settings.py, do you have "LANGUAGE_CODE = 'en-us'"? That could be the 
problem. Otherwise, I could have a look at your installation if you send me the 
access to blue.fritzing.org privately by e-mail.

Original comment by kipla...@gmail.com on 14 Feb 2014 at 4:14

GoogleCodeExporter commented 9 years ago 
Yes, that's what we have set. But as far as I can tell that's the default & 
recommended setting.
From reading the docs at 
https://docs.djangoproject.com/en/1.5/topics/i18n/translation/#how-django-discov
ers-language-preference it looks as if everything is set up correctly.
On the other hand, 
http://pythonhosted.org/django-page-cms/settings-list.html#page-language-mapping
 prefers 'en-us' instead of just 'en', which we currently have set.
I will continue tomorrow, but any pointer would be appreciated. :) Login is a 
bit tricky...

Original comment by andre.knoerig@gmail.com on 14 Feb 2014 at 5:23

GoogleCodeExporter commented 9 years ago 
Could you have a look again? Or upload the code somewhere?

Original comment by kipla...@gmail.com on 1 Mar 2014 at 11:35

GoogleCodeExporter commented 9 years ago 
Couldn't find out anything new.. I will contact you privately for exchanging 
config files.

Original comment by andre.knoerig@gmail.com on 4 Mar 2014 at 4:33

GoogleCodeExporter commented 9 years ago 
I could finally reproduce the issue and applied a fix that works for me. Please 
give it a try and let me know if it also works for you.

Original comment by orgfritz...@gmail.com on 25 May 2014 at 7:21

GoogleCodeExporter commented 9 years ago 
It also works for me in Safari, wget and curl. Great!

Could you explain the fix in case someone reading this has the same problem?

Original comment by kipla...@gmail.com on 25 May 2014 at 8:22

GoogleCodeExporter commented 9 years ago 
Great, thanks for verifying!

I changed
LANGUAGE_CODE = 'en-us'
to
LANGUAGE_CODE = 'en'.

Not sure why this worked, really, maybe because this setting is used for the 
fallback language and 'en-us' pages don't exist, but 'en'.

Original comment by andre.knoerig@gmail.com on 2 Jun 2014 at 3:21