First let me say that I really like the new aMember v4. There is a lot that is still quite baffling. I'm hoping somebody can explain just what is going on in this screen shot!! Here's the sequence of events: 1. user signs up for subscription on 1/26 at 7:35am. 2. I cancel recurring payment and test out refund function on 1/26 at 7:51am. 3. I add user back to product manually later on 1/26 to test 'add access manually' and time is logged wrong. Seems like the sequence of payments in the table on the right is out of order. Also, I can't understand how a subscription can end earlier than it starts (see green arrows). Can anybody make sense of this?
1. In regards to access record that have expire date earlier then begin date. This is correct. In order to revoke access(when you refund payment for example), aMember finds user's latest access record for that product and change it expiration date to yesterday. In your tests, you hse product with one day period, so access record's expiration date was set to yesterday's date even if it begin date is today.This is done to remove access immediately. 2. In regards to manual payment's access record.There was a bug in access record start date calculation. This bug was fixed in version control system and will be available in next version release. aMember used to calculate access record's start date depends on previous records expiration dates. So, it took all access records that user had for that product, found last expiration date and that date was used as start date for new access record. That's why next access record have yesterday as start date(see number 1). Now, if last expiration date is in the past, aMember will take current date as start date for new access record.