Closed (fixed)
Project:
iDEAL advanced
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
29 Aug 2015 at 15:32 UTC
Updated:
1 Sep 2015 at 14:52 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
neograph734Comment #3
neograph734I had to add a computed (pseudo) field to the list so we can show the amount in Euro's in the admin overview page.
Comment #4
neograph734Forgot about translating the statuses, this should be the final patch.
Comment #5
mvdve commentedThanks for the patch!
Two things:
- The purchase_id can also be defined by the user via hook_ideal_advanced_commerce_transaction_alter. It may be better to define it as a text field instead of integer to give them more freedom.
- The ideal statuses are already defined in the ideal connector wrapper. My suggestion would be to move the statuses to the ideal_advanced module file. This way they are more generic and can be used everywhere, without calling the whole wrapper class.
Please review the updated patch.
Comment #6
mvdve commentedIntroduced a bug. New patch with moved statuses and updated purchase_id type.
Comment #7
neograph734Just read through the patch and is seemed ok. We might make it even better by changing the config_id type to the actual configuration entity type (I believe that did some entity relation magic). I'll give that a try this afternoon and let you know the outcome.
Comment #8
neograph734Implemented the proposed change of #7.
By having the type of the transaction config_id set to `ideal_advanced_config` rather then `integer`, the configuration entity is now connected to the transaction.
This is visible as a Views relation and with Entity Metadata Wrappers, where both entities can be chained together.
Apart from that one little change, your patch has remained unchanged and is ready to be committed.
Comment #10
mvdve commentedExcellent work! Thanks for the contribution. The patch is committed.