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

dev/core#3782 Remove rule that stops signing up for a membership if matched contact already has a cancelled on of that type #24159

Merged
merged 2 commits into from
Oct 11, 2022

Conversation

mattwire
Copy link
Contributor

@mattwire mattwire commented Aug 5, 2022

Overview

A client had intermittent reports from people not being able to sign-up (for a membership) and being redirected to civicrm%2Fcontribute%2Ftransact instead of to the payment processor (though it turns out the same thing happens whatever payment processor you use).

After a lot of work troubleshooting and adding debug I finally tracked it down to the following error:
Your %1 membership was previously cancelled and can not be renewed online. Please contact the site administrator for assistance.
But that error was not being reported back to the client and I had to log the contents of $this->_errors in CRM_Core_Form::validate() to find out what was going on.

I don't really understand why #3531 ever got merged given that it seems no-one was in favour of restricting memberships in this way: https://issues.civicrm.org/jira/browse/CRM-14645

Proposal: Just remove the code. If anyone actually needs it they could easily add it via a validateForm hook.

Before

Cannot signup for a membership via contribution page if matched contact has a cancelled membership of that type.

After

Can signup for a membership via contribution page if matched contact has a cancelled membership of that type.

Technical Details

Comments

@civibot
Copy link

civibot bot commented Aug 5, 2022

(Standard links)

@civibot civibot bot added the master label Aug 5, 2022
@agileware-justin
Copy link
Contributor

agileware-justin commented Oct 7, 2022

Agree with this PR.

Will need CIviCRM documentation updates as well, when merged.

@demeritcowboy
Copy link
Contributor

jenkins retest this please

@demeritcowboy
Copy link
Contributor

This seems ok just that the scenario 1 in the original ticket now results in a membership of type A being converted to a membership of type B, e.g. if you have the below situation, and then the person renews online and picks Student, the General now becomes Student. But that's maybe ok, just might not be what the person really intended and they were just confused about what they currently had and what they were renewing.

In the scenario in the PR here I (as the member) did get notified on screen about the error (without the PR applied) but maybe there are some setups where the error is hidden.

Untitled3

@demeritcowboy demeritcowboy added the merge ready PR will be merged after a few days if there are no objections label Oct 8, 2022
@demeritcowboy demeritcowboy merged commit b3e4de5 into civicrm:master Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
master merge ready PR will be merged after a few days if there are no objections
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants