search

artfulrobot / uk.artfulrobot.civicrm.gocardless

A CiviCRM extension providing GoCardless integration to handle UK Direct Debits.
GNU Affero General Public License v3.0
5 stars 18 forks source link

Membership since date is getting changed #27

Closed Upperholme closed 5 years ago

Upperholme commented 6 years ago

I'm using this extension to support membership sign-up and renewal on a client site (running 4.7.27). So far it all seems to be working largely as expected, however we've noticed one thing in our initial round of live tests:

For members who are renewing their existing membership by setting up a DD (they were previously paying by other means), we are seeing that the 'member since' date is being updated such that it is the same as the 'start date'. As far as I can tell, for all of the live tests we've done so far, the existing membership was still within the grace period, and in those circumstances the 'member since' date should not change.

I realise that the extension probably doesn't directly interact at all with memberships, and that maybe this is due to a different Civi issue, but wanted to post it here nonetheless in case anyone can cast any light.

artfulrobot commented 6 years ago

Yes, you're right, this extension does not interact with memberships. If you know that a different payment processor behaves differently I could take a look to see if I can do as they do.

Otherwise, I'm not sure your issue will get much attention on this issue queue. You could post question on https://civicrm.stackexchange.com/?

Upperholme commented 6 years ago

I've posted a question on the StackExchange site at https://civicrm.stackexchange.com/questions/22387/membership-dates-unexpected-behaviour

Upperholme commented 6 years ago

As you'll see from that I'm actually seeing two issues. One is the unwanted change to the "member since" date, and the other is that a membership appears to be created when the DD is set-up, despite the fact that no transaction has happened at that point. I'll create a new issue here for that to avoid confusion.

artfulrobot commented 5 years ago

We believe this issue is closed thanks to PR #44