Skip to content

Twingle API 1.2
Compare
Choose a tag to compare
@jensschuppe jensschuppe released this 10 Nov 11:37
· 232 commits to master since this release
1.2
6786af0

This release makes recurring contributions actually work, i.e. connecting individual payments with the original recurring contribution and not treating them as new single contributions. Also, it is now possible to trigger a user-defined callback for performing additional tasks with newly created memberships in your own extension. Moreover, the campaign can now be assigned to more than just the contribution entity. With these enhancements, you can now use Twingle forms as membership signup forms.

Changes since Twingle API 1.1

  • [#19] Custom post process call for newly created memberships - by @bjendres
  • [#20] Alternative to blocking cancelling/ending recurring contributions - by @bjendres
  • [#23] Correctly differentiate initial recurring and subsequent contributions and link them - by @jensschuppe
  • [#24] Option to use CiviSEPA's own mandate reference rather than Twingle's - by @bjendres
  • [#25] Custom fields mapping not working - unnecessary json_decode() - by @jensschuppe, @MarcMichalsky
  • [#26], [#27] More flexibility on where to put the campaign information - by @bjendres
  • [#29] Copying profile overwrites existing or default profile - by @bjendres, @jensschuppe
  • [#31] Create memberships only on initial recurring contribution, not every installment - by @bjendres
  • [#33] fix custom_field_mapping - by @MarcMichalsky
Assets 4
Loading