Timeline for Frequency is ignored for auto renewable memberships
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 18, 2022 at 15:33 | comment | added | Jay Edgar | Created lab.civicrm.org/dev/core/-/issues/3810 | |
| Aug 18, 2022 at 14:45 | comment | added | Jay Edgar | This seems to be a rather major bug. Even if the work around would be to use a rolling year membership it would not allow for something like a 6 month membership. I'm going to open a new issue because although 3344 is similar it is (perhaps) not the same issue. | |
| Aug 18, 2022 at 14:41 | comment | added | Jay Edgar | Just tried it. We have memberships that end on the last day of the month and start on the first. If you choose 12 months and fixed, it then lets you pick 1 to 31 for the start date. If you choose 1 year and fixed then you can only pick a month and day (e.g. Jan 01). So for a fixed membership start date by month that is the only option that works. | |
| Aug 18, 2022 at 14:37 | comment | added | Jay Edgar | We used to have one year, but I don't recall why it was a problem. Maybe I will try that again. | |
| Aug 17, 2022 at 19:47 | comment | added | petednz - fuzion♦ | concur i can see this behaviour. silly question, but why not choose '1 year' instead of '12 months'? | |
| Aug 17, 2022 at 16:49 | comment | added | Jay Edgar | I should add that this started sometime around version 5.49 or 5.50. Prior to upgrading this was working fine. | |
| Aug 17, 2022 at 15:53 | history | asked | Jay Edgar | CC BY-SA 4.0 |