I am investigating this, but seems like I cannot reproduce the bug. Mind to try again with a bummer account and see if it was just an isolated case?
I did some testing with this and was able to figure out how to duplicate this bug - at least on my forum.
if you manually subscribe a user to a user group that they're not already a part of, it doesn't seem to duplicate the payment history entry, but it does seem to be an issue if you revoke their subscription and then reapply the subscription again with the same settings. it seems to me that the revoke feature might need some tweaking.
what rules are followed when a payment is revoked? to me, it seems like if an expiry user group is set for a subscription, then if a payment is revoked for a user in said subscription, it should follow the expiry settings.
I'm not exactly sure how I managed to get it to subscribe a user who was not selected before in my OP, though maybe I did add that user by mistake and didn't notice.... :/
I cannot reproduce this one still.
I cannot reproduce this one still.
is there code in a template that might be causing this? perhaps it's just something on my board..
bumping this as it's still an issue. just upgraded from beta 9 to beta 10 and it placed 2 users in a 3-year subscription on its own. I revoked both of those. when I went to resubscribe a user to the 1-year subscription, which is where his account should of been, it the duplicated it again....quite annoying.
I am in the process of releasing beta 11, will take some days to live test. The new version sports a revamped subscribe users process, I believe I couldn't reproduce this as I have inadvertently fixed the issue while recoding the page. Let me know if you are available for some tests on your side.
I didn't notice any new duplication bugs when upgrading from beta 10 to beta 11, but it does list some coinbase payments in my payment history when I don't even use coinbase whatsoever... I sent you a screenshot on discord.