Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.4
-
Fix Version/s: 4.7.11
-
Component/s: None
-
Labels:
-
Documentation Required?:None
-
Funding Source:Contributed Code
Description
Coleman - I guess this is as a result of switching to an new select field type with options filtered for contribution searching...
Attachments
Issue Links
Activity
Yeah, I don't know if one exists already but that makes sense - ie. the contribution_status list is filtered depending on your entity - some might argue we should just have separate option groups!
I stopped short of separating the option groups because I concluded the calls to get the values from Pseudoconstants::contributionStatus all needed to be swapped out at first. I swapped out a good chunk of them but could not cover them all this time around
Coleman is out for a couple weeks, but this issue is high on Eileen's wishlist for 4.7.11. Monish, could you take a look when you get back? https://github.com/civicrm/civicrm-core/pull/8793
Tested the PR, forced search do have some issues as mentioned by Eileen on the PR. So https://github.com/civicrm/civicrm-core/pull/8793 can be merged as it fixes this issue.
Eileen McNaughton - so should it be fetching a different pseudoconstant?