Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.6
-
Fix Version/s: 4.7
-
Component/s: CiviContribute
-
Labels:
-
Documentation Required?:None
-
Funding Source:Core Team Funds
Description
I've noticed customers running into problems with the payment processor 'name' field. If they name it to be meaningful to them the customer sees a name that doesn't make sense on the contribution page. But if they call them all 'Credit card' then it presents them with no way to distinguish in the contribution page config.- see attached pic
An easy fix seems to me to be to display the description in small text below the name on the contribution config page..
Attachments
Activity
Yea we kinda painted ourselves into a corner by making pseudoconstants always be a flat associative array. EntityRef + getlist do it better (with room for title, description, prefix, suffix, icon, data, etc.) but come with a little ajax overhead.
Here's a pr that improves PaymentProcessors api and getlist api to work nicely together:
https://github.com/civicrm/civicrm-core/pull/5777
Changing the field to use EntityRef looks real nice. Here's a start: https://github.com/civicrm/civicrm-core/compare/master...colemanw:CRM-16204-b
If you like it, we'd have to do a little more refactoring of the form to make the postProcess understand it's getting input from an EntityRef and not from checkboxes.
I've looked at the code (rather than the UI) & it definitely looks like the right direction!
The original was pitched at 4.6 & I can see this is not a 4.6 solution. I don't think in this particular customer case it will be a killer if it is not in 4.6 - although it would be generally 'nice' - I was prepared to patch during testing & let the patch drop away in the live phase.
Eileen McNaughton, I've done this PR for the manageEvent form: https://github.com/civicrm/civicrm-core/pull/6348
If that's all you need you can close this issue. If you want to make the same modification to the contribution page config form, it'll be very similar but with a bit of funky js to contend with.
I meant to run this past you at the sprint
https://github.com/civicrm/civicrm-core/pull/5653/files
Do you have a recommendation for how to best do this. I want to get a 'backoffice' version of the payment processor list on 2 config forms - ie. their front end label tends to always be 'credit card' to make it make sense to the punters, but back office they want to see which account it is.
Feels like an-almost-pseudoconstant-almost-get-list thing.