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 »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • For memberships inherited by relationship, status appears stuck on "New"
Pages: [1]

Author Topic: For memberships inherited by relationship, status appears stuck on "New"  (Read 795 times)

GinkgoFJG

  • I post frequently
  • ***
  • Posts: 135
  • Karma: 4
    • Ginkgo Street Labs
For memberships inherited by relationship, status appears stuck on "New"
February 06, 2013, 01:33:30 pm
Hello,

I have an interesting situation with CiviMember that I thought I'd put out here for ideas before banging my head against the wall. I have some members more than halfway through their memberships whose statuses are still showing as "New." I'm on Civi 3.4.6. I've confirmed that the Membership Status Rules for the New and Current statuses are set to their defaults, and I've run bin/UpdateMembershipRecord.php; still, these not-New memberships are still showing as "New."

Anyone seen this before or have any helpful suggestions?

Thanks!
-Frank
« Last Edit: February 06, 2013, 02:21:18 pm by GinkgoFJG »
Are you a CiviVolunteer user? Join the CiviVolunteer 2.0 Matching Grant effort to help the project win $15,000 in grant funding.

GinkgoFJG

  • I post frequently
  • ***
  • Posts: 135
  • Karma: 4
    • Ginkgo Street Labs
Re: For memberships inherited by relationship, status appears stuck on "New"
February 06, 2013, 02:16:16 pm
After looking at this more closely, it appears to be the case that only memberships by relationship are affected by this issue. For instance, for an Individual named Wile E. Coyote who has a "Director of" relationship to an Organization named Acme, Acme's membership status is accurate ("current" six months in), while the status for Coyote's inherited relationship is wrong (still set to "new" after six months).

Is this a known bug?
« Last Edit: February 06, 2013, 02:20:33 pm by GinkgoFJG »
Are you a CiviVolunteer user? Join the CiviVolunteer 2.0 Matching Grant effort to help the project win $15,000 in grant funding.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: For memberships inherited by relationship, status appears stuck on "New"
February 07, 2013, 11:31:32 am
I don't recall hearing about this bug, but there's been some changes to update membership status code since 3.4. Do you have a 4.2 test site where you can replicate the setup, and then run the 'process_membership' scheduled job?
Protect your investment in CiviCRM by  becoming a Member!

GinkgoFJG

  • I post frequently
  • ***
  • Posts: 135
  • Karma: 4
    • Ginkgo Street Labs
Re: For memberships inherited by relationship, status appears stuck on "New"
February 07, 2013, 11:56:07 am
Hi, Dave! I think it may be related to the bug in this other post. I'd be happy to try to replicate the issue on an updated instance, but I wasn't sure the best approach to take. Any better ideas than creating a membership with a relationship and waiting around for three months to see what happens?  ;D
Are you a CiviVolunteer user? Join the CiviVolunteer 2.0 Matching Grant effort to help the project win $15,000 in grant funding.

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: For memberships inherited by relationship, status appears stuck on "New"
February 07, 2013, 03:27:43 pm
How about artificially setting the wrong status for a membership and related membership(s) via MySQL, and then running the scheduled job. Example: create membership with start date last year sometime and add relationships to inherit. All should show up w/ status = Current. Then go into DB and change membership.status_id back to 1 (new) for both 'owner' and related memberships. Then run the scheduled job.

Did a quick look at the code, and I think the logic for updating related membership statuses is in CRM_Member_BAO_Membership::createRelatedMemberships() if you need to debug stuff.
Protect your investment in CiviCRM by  becoming a Member!

GinkgoFJG

  • I post frequently
  • ***
  • Posts: 135
  • Karma: 4
    • Ginkgo Street Labs
Re: For memberships inherited by relationship, status appears stuck on "New"
February 14, 2013, 10:48:14 am
Thanks for the suggestion, Dave. I tried this with both 4.2 and a fresh copy of 3.4.6. In both cases, the script behaved as one would expect, updating both records with the appropriate status.

I think this group had problems with their import, so I guess I'll take a look there and see if anything looks funky in the DB. Might as well check for core hacks too...

Thanks!
Are you a CiviVolunteer user? Join the CiviVolunteer 2.0 Matching Grant effort to help the project win $15,000 in grant funding.

GinkgoFJG

  • I post frequently
  • ***
  • Posts: 135
  • Karma: 4
    • Ginkgo Street Labs
Re: For memberships inherited by relationship, status appears stuck on "New"
February 14, 2013, 01:57:04 pm
I haven't gotten past superficial diffing, but it's clear that a previous dev did indeed hack on the core, and in particular on some of the files I'm interested in. Explains a lot.  :-[
Are you a CiviVolunteer user? Join the CiviVolunteer 2.0 Matching Grant effort to help the project win $15,000 in grant funding.
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • For memberships inherited by relationship, status appears stuck on "New"

This forum was archived on 2017-11-26.