ERROR 500
ERROR 500: javax.servlet.jsp.JspException: ServletException in '/common/layout3col.jspx': Can't insert page '/pages/solr/explore_body.jsp' : ISO-8859-10 I get this error even when i try to read a bug report forum post about same error. So i have to make a new one, sorry ... When i wasnt logged in i could read the post, when i log in to post in that post, then theres error. And i get same error also on many (50%-75%) instructables. Even on some instructable list pages. Its drivin me nuts. I get it on Opera and Konqueror browsers on Debian.
Discussions
10 years ago
This has been fixed.
Reply 10 years ago
Considering how many topics there are on the subject, might someone post a topic that explains the problem and how it was fixed?
L
Reply 10 years ago
There are some pieces of our code that use the language set of the browser to determine how to format a number or a date. Java does not support the Nordic character set ISO-8859-10, so we needed to force it to use one that it did support. I don't think it warrants it's own forum topic.
Reply 10 years ago
As far as I understand there are two solutions to this - global and local, I mean serverside and clientside.
1. On server make errorhandler in java to just ignore the error. Because, I wouldn't care if some date or number gets not shown at all. Unless its important to decide what posts should be shown.
OR
2. Install some language sets for Opera, Konqueror, I mean browsers on my own PC. But I have no idea how that would look like.
Reply 10 years ago
Well if it's fixed perhaps not. However, you've satisfied my curiosity, if all these forum topic were related to Nordic-script (not being able to see things I wouldn't know) an explanation is nice to have.
L
Reply 10 years ago
Not sure. Maybe at that place. But when I go other places, I often get same error message. Example
https://www.instructables.com/tag/type-id/?sort=RECENT&layout=text&offset=
This is my usual starting page. There I never get errors. But when I press 2 or next at the bottom, I get same error almost allways. And some posts from the list give same error too. Using Opera. And strange, on Iceweasel (Firefox) I dont have such errors.
Reply 10 years ago
Looks like I missed the fix in a couple of places. We'll have a bug fix release out later today which should fix it for good.