View Issue Details

IDProjectCategoryView StatusLast Update
0001599OXID eShop (all versions)2. ----- eShop backend (admin) -----public2012-03-09 18:05
Reporterdainius.bigelis Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version4.2.0 revision 23610 
Summary0001599: Defined decimal separator is ignored in admin
DescriptionIn Admin area:
when price is inserted for product using comma as decimal separator, i.e. 7,5 - comma is replaced by default PHP decimal separator - a dot. So After price is saved, it is shown as 7.5 in admin area.
Decimal separator in the shop is defined for each currency:
EUR@ 1.00@ ,@ .@ €@ 2
GBP@ 0.68@ .@ @ £@ 2
...
So in this case decimal separator in frontend is ",", but in admin it is ".".
Decimal separator from default currency should be used not only in frontend, but also in Admin area, and if incorrect separator is inserted - it should be replaced by this one.

Please check all the places where this issue is possible (were input of decimal numbers is allowed), i.e. vouchers, VAT fields, etc.
Additional InformationThe priority is increased as we get lot of requests for this fix and this issue sometimes causes incorrect input from users (=incorrect prices in shop).
TagsNo tags attached.
Theme
BrowserAll
PHP Versionany
Database Versionany

Relationships

duplicate of 0001595 closeddainius.bigelis it's not possible to insert VAT with comma, only integers are accepted 
has duplicate 0001876 resolveddainius.bigelis wrong conversion of german number format in voucher discounts 
has duplicate 0001587 closed Voucher amount must not have comma instead of dot 

Activities

dainius.bigelis

2010-06-30 10:18

reporter   ~0003234

According to developers: implementing that would lead to even more confusion in case if these settings would be different with local Regional Settings on users PC.
Suggested solution: include example of numbers, how it should look like (with decimal separators) next to each such field.

dainius.bigelis

2012-03-09 18:05

reporter   ~0005943

For proper solution now would need to implement very complex handling of local/server side and default eshop settings, which would confuse more than would help.
Currently we close this issue and in long term we probably will think about implementing special functionality for handling these and more localization settings.