-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #26: support recurring contributions. #37
base: master
Are you sure you want to change the base?
Conversation
Thanks! It looks good in principle. Tomorrow I'll test it out. |
I'm going to need a little more time on this. I'm testing with Stripe as the payment processor and running into a few difficulties. The first is an intermittent error when I just expose the recurring contribution option with monthly as the only choice. I sometimes get this error:
In addition, when I add the option to select frequency, I'm consistently getting an error in the javascript console (the code seems to be sending an OPTIONS request to the https://server.org/ address instead of https://server.org/civicrm/remoteform - so Drupal responds with an 403 un authorized error). These errors are accompanied by the following in the ConfigAndLog:
Stripe is a complicated payment processor, so I suspect the errors are related to that payment processor. |
Thanks for the feedback @jmcclelland . I didn't test with Stripe, so I'm glad you found that. Need to see if I can find time to put some thought into that. |
It looks like you pushed this to master but actually it's not there? I have an organization I'm working for that would like to support remote contributions with an interval... will this patch work? cc @jmcclelland |
@shaneonabike - no, I haven't yet incorporated this pull request into master. I haven't worked on it since my last comment unfortunately. Also, I wanted to flag that this extension will likely be deprecated soon once oembed functionality is added to CiviCRM: https://lab.civicrm.org/dev/core/-/issues/2994 Hopefully soon we will be able to use ombed to directly embed any form into a web site and not have to mess around with javascript. |
Yeah totally fair! I was aware they were working on it but I have a client who wanted to get this going now. Thanks for the quick response have a great day! |
Hi @jmcclelland This approach is functional, but I admit I'm not totally satisfied with all the manual HTML manipulation that's going on in the new
createRecurringFieldsDiv()
javascript function. This approach is meant to provide more control for the inline field layout that's commonly used for recurring-related fields (e.g.I want to contribute this amount every ____ [day(s)] for ___ installments), which breaks many assumptions about field layout for most fields in Remote Forms. I'm hoping this is useful as-is but of course that's up to you; I'm running out of client budget that might allow significant re-working of this approach. Toughts?