New answers tagged

0

If you are using latest version of stripe extension there’s a option to disable billing block. Go to Administer >> CiviContribute >> Stripe Settings


4

You need to enable it in Display Preferences. Navigate to CiviCRM >> Administer >> Customize Data and Screens >> Display Preferences. Check the contribution option under 'Contact Search' field.


1

I'd answer this in a slightly different way, the question was tagging contributions and not contacts, my assumption is that there is a need to hold metadata against a contribution. We have a similar requirement in the UK for knowing if a specific contribution can have gift aid tax claims made against it or if the contribution already has been claimed etc. So ...


3

Yes you can tag contacts from the search. Find Contribution list all the contributions and its not possible in current system to tag contribution, so action option would be available from Find contribution to tag the results. As said by Andy and Pete, you will need to Advance search to the the contacts based on the criteria and choose the 'Tag - Add to ...


1

The fields listed above (first name, last name, street address, city, state/province, postal code, country) MUST be marked as required on the profile otherwise the "My Billing Address is the same as above" checkbox will not appear. In addition, on the Fees page "Billing address required" must be unchecked (or the user will be required to ...


1

I have upgraded the extension 1.6.2 to 1.7.4. During upgraded extension upgrade function were not ruined upgrade_1_7_002 and upgrade_1_7_003. After manually run the SQL Queries issue is resolved.


0

If I understood your question correctly... Profiles that are assigned to Contributions display on the New Contribution input page but they are collapsed by default. We have a custom Profile "Other Details". My first screenshot shows it collapsed and the second one shows it opened. If you do not see it there, then go into your Profile setting and ...


2

The retry attempt on REJ response is dependent on the type of failure. Card Reported Lost or Stolen e.g. will be bumped to next month - whereas other failures will attempt next day. Note that you can always catchup or hit Process (if using iATS Legacy) after e.g. updating a Lost or Stolen card so you don't need to wait until next month to capture the monies.


3

This works in core! There is an activity created of type Update Recurring Contribution Billing Details when a contact updates their details through the form. And then you can add a CiviRule to send an email when this activity is created. That will also capture back office updates and ideally it wouldn't but this is bearable. A back office update will have a ...


Top 50 recent answers are included