It's on purpose that it removes the link to the user when you delete. It was added years ago here: https://github.com/civicrm/civicrm-svn/commit/3d9843c5912cb9d77e557b4a8cd4ef711f2cdcbb
and seems related to deduping https://issues.civicrm.org/jira/browse/CRM-6861
But yes Civi will reattach them once you do something that triggers the matching which is ...
Yes, the price fields are independent, and the design limits you to putting all the membership types/flavours into one price field if you need to force only one.
A simple alternative is to create separate contribution/membership pages for ...
After testing, here is how it works.
If we use again my example with twice the same event date 3rd of April:
Status 1: from membership date to start date
Status 2: from start date to end date.
Status 1 will change by the end of the 3rd of April which means start date from the previous status is "Master" and start date lasts 24 hours. Status 2 will appear ...
For anyone else that stumbles across this because they are facing something similar:
I got a response on mattermost from Matt @ MJW consulting pointing me to this issue - https://lab.civicrm.org/dev/membership/issues/18
Other people have come across this, there is a patch, but it hasn't been progressed yet.
Thank you for supporting CiviCRM! You can use this ESR form for members to request a download key.
There is more information in the FAQ on the ESR page.
When we launched Extended Security Releases (ESR) as a service, we were not sure how many people would sign up, so we started handling the requests manually. It seems like it's here to stay, so we are ...
This is how we solved this problem for a client that has teachers as their constituents who all belong to a School Board/District. We're using the autocomplete functionality that webform_civicrm module provides to force teachers to select rather than to type. You can only imagine how many ways one could type "Grande Prairie Roman Catholic Separate School ...
I have seen the same behaviour on a membership site which is also using GoCardless. So, yes, I think it is the expected behaviour.
I believe a membership can only be in the 'pending' state when it is first set up. There is a logic to it staying as 'expired' even after payment has been received but not cleared so I don't think it would make sense for all ...
You may need to look at your Membership Status rules. Having a membership start off as Pending can be set using these rules, but i suspect they can only run off the 'member since' date which only happens on the first sign up
Membership stuff can be tricky, but I believe once the pending Contribution is actually received, the new Membership will update to Current. I'm assuming you have set up the new payment processor in Civi.
This appears to have been implemented as a deliberate 'feature' to prevent users from making changes to memberships linked to recurring payments. See this related question for details:
How can you edit the end date for an auto-renew membership?
A fix has been merged into CiviCRM core (PR #15540) that fixes this issue for the end date field. This fix should ...
I think this is a "context" thing meaning that when you are emailing, even from "Find Memberships", you are emailing to CONTACTS and so are in the contact context, whereas for example if you do a "Find Memberships" and then from the actions menu choose "Print/Merge Document", you are in MEMBERSHIP context and can choose tokens like Membership Fee.
I recommend taking a look at the Caldera Forms CiviCRM plugin. This will allow you to use conditions within a caldera form to show and hide fields (and make them required) based on the type of membership selected. The plugin contains multiple processors to allow you to add contacts, memberships, etc. in CiviCRM.
The plugin is available in the WordPress ...
I am not really familiar with CiviCRM and Wordpress. But one direction of looking for a solution is that use Contribution Pages for membership signup and renewals and then use a different contribution page for different membership types.
SyntaxError: expected expression, got '<' on civicrm:1