CiviCRM Community Forums (archive)

For tracking purpose: http://issues.civicrm.org/jira/browse/CRM-7392

Kurund

I'm also running into this issue. Will applying the bug fix for 3.3.3 be OK for 3.3.5?

Audrey, my work-around (until the issue is resolved) is to temporarily change the roll-over date to Dec 31. This change makes new sign-ups have the correct start and end dates, so at least you don't have to manually change the dates.

Fixed membership
Start: 1 April
Duration 1 year
Rollover: 1 March

New membership since 1 March 2011 is showing:
Join date: 3 March 2011
Start: 1 April 2012
End: 31 March 2013

Expecting:
Join date: 3 March 2011
Start: 1 April 2011
End: 31 March 2012

Cheryl / Audrey - Clearly the current behavior is wrong, but I'm a bit surprised at the "Expected" result above. If someone signs up during the rollover period I would the expected behavior is that the membership is active NOW but duration is extended to end of next fixed period. The "expected" scenario above with Start: 1 April 2011 means that this person is not considered a member until April 1, 2011. Wouldn't this result make more sense? ..

Expecting:
Join date: 3 March 2011
Start: 1 April 2010 (beginning of current fixed membership period) OR perhaps 3 March 2011
End: 31 March 2012

Cheryl / Audrey - Clearly the current behavior is wrong, but I'm a bit surprised at the "Expected" result above. If someone signs up during the rollover period I would the expected behavior is that the membership is active NOW but duration is extended to end of next fixed period. The "expected" scenario above with Start: 1 April 2011 means that this person is not considered a member until April 1, 2011. Wouldn't this result make more sense? ..

Thanks so much for the followup on this issue. Although the "Expected" behavior that Cheryl described has the start date listed as the beginning of the next membership term -- a date in the future -- CiviCRM still considers those memberships active. In other words, they come up when I search for new and current members, and they sync appropriately with CiviMember Roles Sync in Drupal.

1. Membership start date ALWAYS is equal to current fixed period's beginning date (membership start date should NEVER be set to a future date).

I can take this next comment to the issue tracker report, but I'm not sure about this. If the next membership start date is April 1, 2011, and someone signs up on March 30, 2011, I don't think I want CiviCRM to record them with a membership that started April 1, 2010. It's like adding a whole year to their member history, instead of a day. For myself, I'd prefer a March 30, 2011 start date, or even the previously "expected" April 1, 2011 start date, as long as "future members" are counted and privileged properly. I don't know what works best for anyone else...

Hi,

I applied the patches from CRM-7825 (33440 + 33452) to 3.3.5, tested and found a problem.

Membership type has:

duration_unit: year
duration_interval: 1
period_type: fixed
fixed_period_start_day: 401 (Apr 01)
fixed_period_rollover_day: 101 (Jan 01)

I created a new membership today (Apr 01) with the following results.

With vanilla 3.3.5:
----------------------
join_date: 2011-04-01
start_date: 2012-04-01 (should be 2011-04-01)
end_date: 2013-03-31 (should be 2012-03-31)


With 3.3.5 + 33440 + 33452:
------------------------------------
join_date: 2011-04-01
start_date: 2011-04-01 (correct)
end_date: 2013-03-31 (should be 2012-03-31)

With sandbox.civicrm.org r33484:
----------------------------------------

join_date: 2011-04-01
start_date: 2011-04-01 (correct)
end_date: 2013-03-31 (should be 2012-03-31)

Maybe this is an edge case when signing up on the fixed period start date? That will be quite a common edge case.

Dave J

Dave - Thx for retesting this. I've reopened the issue and requested that the team make sure these conditions are covered in the associated webtest:

join date = fixed period start date
join date is after fixed period start date and prior to rollover date