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) »
  • CiviMember uses Admin status at Membership Create
Pages: [1]

Author Topic: CiviMember uses Admin status at Membership Create  (Read 2039 times)

FatherShawn

  • Ask me questions
  • ****
  • Posts: 372
  • Karma: 25
    • C3 Design
  • CiviCRM version: 4.2.11
  • CMS version: Drupal 7.23
  • MySQL version: 5.5.32
  • PHP version: 5.3.10
CiviMember uses Admin status at Membership Create
October 16, 2008, 03:56:32 am
I am migrating our production site to v2.1.  Because of another issue, I happened to create a membership for a member in the new installation.  The rules referenced in the post below (which was about importing memberships) are in force.  The new membership used these dates:
Join: May 27, 2007
Start: Jan. 1, 2008

CiviMember should have selected Communicant but it selected Good Standing which is marked "Admin Only".  This is similar behavior to that fixed in the issue CRM-3570 except that issue was on import rather than creating the membership from the contact's membership tab.

Is anyone else having similar issues?  Should I file one?

Quote from: FatherShawn on September 18, 2008, 07:23:55 am
StatusStart EventStart Event Adj.End EventEnd Event Adj.Current Membership?Admin Only?WeightDefault?Enabled
Newjoin datejoin date
1 year
X
1
X
Good Standingstart datestart date
1 year
X
X
2
X
Communicantstart datestart date
1 year
X
3
X
X
Deceasedstart dateend date
X
4
X
Inactivestart date
X
5
X
Pendingjoin datejoin date
6
X
Cancelledend dateend date
X
7
X
Lead Developer, C3 Design.
Twitter: @FatherShawn

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: CiviMember uses Admin status at Membership Create
October 17, 2008, 04:55:38 pm
Thanks Shawn. We filed an issue here - http://issues.civicrm.org/jira/browse/CRM-3724
« Last Edit: October 17, 2008, 05:09:03 pm by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

davej

  • Ask me questions
  • ****
  • Posts: 404
  • Karma: 21
Re: CiviMember uses Admin status at Membership Create
March 20, 2013, 12:43:11 pm
Hi,

I know this is a very old issue but I believe I've tracked down a bug in 4.2.8 with a similar cause. I'll post details but I thought I'd ask this question first...

For CRM-3570, a new param was added to CRM_Member_BAO_MembershipStatus::getMembershipStatusByDate(): $excludeIsAdmin = FALSE .

This left bug CRM-3724, mentioned in this topic.

What I'm wondering is: are there ANY circumstances where getMembershipStatusByDate() should include statuses with is_admin = 1 ? The help text for the "Administrator Only?" field on membership status edit form (/civicrm/admin/member/membershipStatus?action=update&id=N&reset=1) says:

"Check this box if this status is for use by administrative staff only. If checked, this status is never automatically assigned by CiviMember. It is assigned to a contact's Membership by checking the Status Override flag when adding or editing the Membership record. Start and End Event settings are ignored for Administrator statuses. EXAMPLE: This setting can be useful for special case statuses like 'Non-expiring', 'Barred' or 'Expelled', etc."

This suggests to me that a status with is_admin = 1 should never be returned by getMembershipStatusByDate().

Is that right?

If so, seems to me the $excludeIsAdmin isn't needed and getMembershipStatusByDate() should always exclude is_admin = 1, which I think will solve the other bug I've encountered.

Dave J

davej

  • Ask me questions
  • ****
  • Posts: 404
  • Karma: 21
Re: CiviMember uses Admin status at Membership Create
March 21, 2013, 06:07:25 am
Hi again,

I've found an issue similar to the new one I encountered, with the same cause:
http://issues.civicrm.org/jira/browse/CRM-11741

I've posted details of my issue there and confirmed that it affects 4.2.8 but not 4.3.beta3 .

A fix was committed for this in trunk, 25 Jan 2013:
https://fisheye2.atlassian.com/changelog/CiviCRM?cs=45146
 - just sets param $excludeIsAdmin to TRUE when calling CRM_Member_BAO_MembershipStatus::getMembershipStatusByDate().

I'd still be interested to know why getMembershipStatusByDate() should ever include is_admin = 1.

Cheers,

Dave J

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMember (Moderator: Deepak Srivastava) »
  • CiviMember uses Admin status at Membership Create

This forum was archived on 2017-11-26.