View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000813 | OXID eShop (all versions) | 4.07. Source code, Test | public | 2009-04-20 16:17 | 2012-12-10 13:45 |
| Reporter | dainius.bigelis | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | won't fix | ||
| Product Version | 4.1.0 revision 17976 | ||||
| Fixed in Version | 4.1.1 revision 18442 | ||||
| Summary | 0000813: non-ASCII chars are not supported in non-UTF8 shop | ||||
| Description | In case when shop is not UTF8, the non-ASCII chars are not supported. When non-ASCII char (i.e. any letter from cyrillic alphabet) is inserted into any options in Admin area (i.e. character mapping in SEO tab) - it will be corrupted after the Save clicked. The problem exists only when shop is not UTF8. | ||||
| Tags | No tags attached. | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | 5.2.6 | ||||
| Database Version | 5.0.33 | ||||
|
|
In general we see no nice solution to fix this problem (except moving to full UTF in shop).. Imagine you have non UTF shop with two admin languages - german and russian. You login to admin by selecting russian language, thus all UI translations goes russian. You choose to load list items in german and you see that umlauts are broken due to different charset encoding...and so on. We could encode/recode output/input into/from utf-8, but still this could lead to many problems + performence loss and this solution would not look nice. So as we implemented UTF support, prepared migration description - correct way is to mograte shop to utf and forgot about such problems. |
