Details
-
Type:
Bug
-
Status: Open
-
Priority:
Important
-
Resolution: Unresolved
-
Affects Version/s: 4.7.21, 4.7.20, 4.7.22
-
Fix Version/s: None
-
Component/s: CiviMember
-
Labels:None
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
-
Overview:When a Membership Type with a Fixed Month period is created, the calculated end date adds an additional month.
-
How it works currently:Fixed Period with 1 month duration adds additional month to calculated end date.
-
How it should work:Fixed Period with 1 month duration should have an end date exactly 1 month from the start date.
Description
I tested and verified this issue in the sandbox within Drupal. When a Membership Type with a Fixed Month period is created, the calculated end date adds an additional month.
For example (using a fixed period of 1 month duration), if the start date is January 2nd, the end date will be set as March 1st. This is a huge deal, especially if an org is charging monthly for memberships.
I am not sure when this bug was introduced. It would make sense to automatically correct all fixed period (month) to set the correct end date. However, I am not sure if we can determine if the end date was manually entered or calculated. Hence the reason I marked this as important. This is a major issue IMHO.