Skip to content
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

Wording for cancelling a recurring contrib. is very confusing #23

Closed
sgladstone opened this issue Aug 17, 2014 · 5 comments
Closed

Wording for cancelling a recurring contrib. is very confusing #23

sgladstone opened this issue Aug 17, 2014 · 5 comments

Comments

@sgladstone
Copy link
Contributor

When clicking the "cancel" link for a automated recurring contribution schedule ( ie at the very bottom of the Contribution Tab on a contact) the wording in the pop-up dialog window is very confusing and inaccurate. The current wording is:

"Are you sure you want to mark this recurring contribution as cancelled?

WARNING - This action sets the CiviCRM recurring contribution status to Cancelled, but does NOT send a cancellation request to the payment processor. You will need to ensure that this recurring payment (subscription) is cancelled by the payment processor. "

@sgladstone
Copy link
Contributor Author

FYI: This message was observed in extension version 1.2.9

@KarinG
Copy link
Contributor

KarinG commented Aug 17, 2014

That bubble is produced by Core [for PayPal/Authorize.net] - I thought Alan
looked at stripping that. I'll have a look later.

-- Karin

On Sun, Aug 17, 2014 at 3:34 PM, Sarah Gladstone notifications@github.com
wrote:

FYI: This message was observed in extension version 1.2.9


Reply to this email directly or view it on GitHub
#23 (comment)
.

@adixon
Copy link
Contributor

adixon commented Aug 18, 2014

It's an ajaxy message, part of core, but it shouldn't have been triggered. I suspect it's a js caching issue - try clearing some caches and try again.

If it's still happening - tell me if it's the cc or ach/eft processor.

@adixon
Copy link
Contributor

adixon commented Aug 24, 2014

I just discovered that the patch that fixed this issue didn't actually make it into the 1.2.9 release, sorry for that.

Next release ...

@adixon
Copy link
Contributor

adixon commented Sep 4, 2014

Fixed in 1.2.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants