CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Inherited memberships 'replaced' by one another
Pages: [1]

Author Topic: Inherited memberships 'replaced' by one another  (Read 1176 times)

Simon West

  • I’m new here
  • *
  • Posts: 19
  • Karma: 1
  • CiviCRM version: 44311
  • CMS version: Drupal 7
  • MySQL version: 5.5.9
  • PHP version: 5.3.6
Inherited memberships 'replaced' by one another
March 13, 2013, 04:06:55 am
Hi,

This is part of a complicated workflow, and only a small snippet of it, but memberships are set up as follows:

e.g.
  • Two membership types: A and B.
  • Memberships Type A is inherited by relationships for spouse and child 1 (there are separate relationships for each child)
  • Membership Type B is inherited by relationships for spouse and child 2
  • Two contribution pages, one for each membership type (price lists aren't applicable)
  • As a parent with relationships to one spouse and two children, I use a contribution page to sign up for membership A. This is correctly inherited by the spouse and child 1.
  • When I register for the second membership type, the first membership disappears from my contact record, the spouse and child 1. This is seemingly replaced with membership B, which now appears against my contact, the spouse and oddly, child 1 - not child 2, as defined against membership type B. However, both contributions still appear.

Any ideas? Is there a limitation here?

Thank you,
Simon


P.S. If interested, I can go into the reasoning behind this setup, but it mainly revolves around a parent having more than one active memberships of the same type for multiple children (which isn't possible), and using the child 1/2/3 relationship types as 'slots'; the foundation of locking access to register for various events, memberships, etc by child through Drupal Views.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: Inherited memberships 'replaced' by one another
March 13, 2013, 08:24:05 am
(pasting my post from IRC)
i think the behavior you're seeing is due to the membership 'upsell' feature that was added several versions ago. Basically the business rule / assumption is that a person will only have one current membership with a given membership org. Hence membership B is considered the 'upsell' replacement for membership A

You can modify this by having two different organization contacts (e.g. like departments or sections of your parent org) and then changing the 'owner organization contact' for membership B to be different from membership A
Protect your investment in CiviCRM by  becoming a Member!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Post-installation Setup and Configuration (Moderator: Dave Greenberg) »
  • Inherited memberships 'replaced' by one another

This forum was archived on 2017-11-26.