Prevent +order from changing members level #54
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* BUG FIX/ENHANCEMENT: Prevent +order logic from changing the user's membership level.
|
I think it'd be nice to have a field option when in the |
|
Thank you for this update. This solves a headache we were experiencing with adding mailed-in check payments and triggering a level change that was reported as a cancelation to reports, which caused a lot of confusion for the client. I know the +order feature doesn't support membership expiration fields, but It would be great to see that happen at some point in the future if possible. It would save a lot of back and for when we add in batches of check payments at a time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: #49