payment_price is stored as a float in the dibs_transaction table. This causes problems when the value exceeds 1 000 000, it will then be returned in exponential form (1.125e+06 for 1 125 000 for example). This will of course cause all sorts of problems. Personally I think the value should be stored as an integer, but I guess this would not be as serious an issue if one would get the value as a normal float in PHP.

I have not had time yet to prepare a patch, but will do so as soon as I can.

This issue applies to both 1.x and 2.x branches of the module, but in the 1.x branch it will surface only when payment-amounts exceeds 1 000 000 SEK for example, since the value in db is divided by 100.

Comments

gnucifer’s picture

gnucifer commented
Priority: Major » Normal

This is now fixed in my github branch: https://github.com/david-xelera/dibs/commit/482f83e38e9da38e28023c3c6f3a...

Because of time-limitations I have not written a update-hook for the change. The update would also have to migrate current values to the new field by for example creating a temporary field, so it's would be a bit tricky to achieve.