ChiliProject is not maintained anymore. Please be advised that there will be no more updates.
We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.
Non ASCII character broken on www.chiliproject.org (Bug #1254)
| Status: | Open | Start date: | 2013-03-20 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: |  Holger Just |
% Done: | 0% |
| Category: | chiliproject.org Website | ||
| Target version: | - | ||
| Remote issue URL: | Affected version: |
Description
History
Updated by Holger Just at 2013-03-20 04:16 pm
Thanks for the notification. It seems we had a non-proper encoding in our database in the past. I have re-added the git repo and now everything looks fine for me.
- Status changed from Open to Closed
- Assignee set to Holger Just
Updated by Toshi MARUYAMA at 2013-03-20 06:14 pm
Still have problem.
- Status changed from Closed to Open
- File user7.png added
Updated by Holger Just at 2013-03-20 06:55 pm
Meh. It seems we have some encoding issue when using mysql2 on ree (as we started to do). If we continue with mysql everything is fine.
I have reverted to using mysql for now and am going to investigate and fix the root cause later. Thanks for your pointer, Toshi.
Updated by Toshi MARUYAMA at 2013-05-31 04:20 am
- File 2013-05-31.png added
Updated by Holger Just at 2013-06-05 08:08 pm
Yeah, we had to update the system due to a half-automatic OS upgrade. That means we are now on Ruby 1.9. I suspect, something was odd with the database encoding in our Ruby 1.8 phase. I'll investigate and probably clean the database by hand if nothing substantial comes up.
Anyway, thanks for noticing.
Updated by Toshi MARUYAMA at 2013-06-19 05:35 am
Related #1273.