Details
-
Type:
Improvement
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.6.10
-
Component/s: CiviCampaign
-
Labels:
-
Documentation Required?:User and Admin Doc
-
Funding Source:Contributed Code
Description
Petitions are really just surveys from the perspective of the database (and the API). Custom fields are available for surveys, and while you can set and retrieve values for those fields on petitions using the API, you can't do so through the main UI.
This simply displays the fields on the Petition add/edit form just like they do on the Survey add/edit form.
Attachments
Issue Links
Activity
Maybe the easiest way to do so would be to hold off on pulling the PR until after 4.7.0 is released and 4.6 stops getting merged to master.
Per Eileen's comments on the PR, looks like the LTS team would be willing to merge it into 4.6 LTS given a bit of testing.
But before they do it needs to be in 4.7. Andrew Hunt can you provide a pr against master?
Finally got a PR done against master. As it turns out, there was no way to edit custom fields on a survey in 4.7 either, so I handled that.
Coleman Watts I think the test failure on https://github.com/civicrm/civicrm-core/pull/7883 is unrelated--let me know if something needs to be fixed.
https://github.com/civicrm/civicrm-core/pull/7275
Nearly everything is lifted from the survey add/edit form.
Did it against 4.6 because it's a pretty small/innocuous change (you might even call it a bug, considering the API does this with no problem). Also, a client needs this sooner rather than later.