CiviCRM Community Forums (archive)

I recently upgraded to 3.3.3, and am having a number of problems with my membership.

I have a number of memberships, fixed, yearly, starting Oct. 1.  A grace period is granted for 5 months.  As of Mar 1, all memberships that were in Grace should now be expired.  Despite manually running the UpdateMemberRecord.php cron, and receiving no errors, none of the statuses are changed.

So I tested:
If I manually edit a Grace membership, making no changes, I receive the following error: <code>Oops, it looks like there is no valid membership status available for the given membership dates. You can Configure Membership Status Rules. OR You can sign up by setting Status Override? to true.</code>.

I then attempted to edit old memberships as well as create new memberships.  After much experimenting and many errors, unless I set the "Member Since" field to a time within a normal member period (oct 1-Sep 30 of desired year), an status error is generated.  Further, the end date of the membership is set according to the "Member Since" Field.  For example, I can set "member since" to sometime in 2006.  Then, a membership which runs from Oct 1 2005 to Sep 30 2006 is created.  Note that if I ALSO set the start date to be 2010, the end date is STILL in 2006.  NONE of my member status settings utilize the 'member since' field.  All of them are based on start/end dates.

This is causing major problems as all memberships need to rollover now, and we need to be able to renew memberships.  Unless the 'member since' field is entered, an error is generated.  However, we do not use (nor frankly want) this field.  I am assuming that the reason the cron is not updating memberships is that it is basing the data on 'member since.'  I must fix this ASAP, so any help or ideas are welcome.

Please help!

My status settings:
Current - start date TO end date
Grace - End date TO end date + 5 mos.
Expired - end date + 6 mos TO ---
New - Admin assigned
New - admin assigned
Pending - admin assigned
Cancelled - admin assigned

I manually adjusted the weight in the db to ensure that this is their order of value.  I attempted to run the updatemembership.php, it ran, gave 'updated' on the screen, but no grace memberships were changed to expired.  No errors were generated by I am not sure where to look  and yes, debugging is currently on.

I also tried to manually edit a 'grace' membership, simply saving it.  In theory, this should have overridden 'grace' with 'expired.'  It did not do so, but gave the error 'member status  not found'. 

As for trying the demo site, I am sure the script works there.  There are no other complaints on the boards, and it was working fine on my site before the upgrade.  I need help figuring out what happend in my database (I also can't successfully run the drupal/civi member/role sync, but I don't know if it is related - I have a post out on that as well).

Oh my.  I think I misunderstood.  I assumed that if grace was for 5 months, it went from Sep 30 (end date of membereship) through Feb 28 (that is, 5 months later).  Then, 'expired' STARTS on Mar 1, which is the first day of the 6th month.  But that is wrong logic...yes?

Correct is that they both go FOR/through 5 months, not TO a 6th month. 

I did change expired to 5, renewed a single membership, and it saved without error.  I just want to make sure I understand the logic so that grace/expired are not overlapping. 

Thanks for the catch.  I feel a bit dumb.

maybe worth running your eye over some examples on demo