Description: Wrong amount shown at the confirmation page. I primarily entered 5000.55 €. The amount after the comma has been dropped.
Browser: Chrome 62
Browser window width: 1024
Browser window height: 768
Screenshots :
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T177929 Integrate new layout | |||
| Resolved | None | T177933 become member - Integrate new layout | |||
| Resolved | None | T182302 Wrong amount shown at the confirmation page - comma |
Event Timeline
Comment Actions
The membership_fee field in the database is of type INT(11), which means the decimal amount will be silently dropped. Since changing the amount type might have also effects on the export, I'd say we postpone the feature "allow decimal membership fees" (or ditch it) and adapt the UI for the time being, meaning disallowing decimal points. Do you agree, @kai.nissen?
Comment Actions
I suspect the export dumping the amount as an integer as well. I do agree to disallow decimal points (and I don't think, we should add this feature at all).
Comment Actions
I do agree to disallow decimal points (and I don't think, we should add this feature at all).
Yes. It it is OK to not make it possible to give non-integers if it rejects them right when people do the input (so it does not take . or , )