Subscription duration generates varying period

Discussion in 'Integration' started by davidshade, Nov 10, 2010.

  1. davidshade

    davidshade New Member

    Joined:
    May 6, 2008
    Messages:
    1
    Hey guys,

    I'm having a bit of a strange problem with my setup. I've got Amember running with 1ShoppingCart.

    I have a subscription product with a set Duration of 1 month.

    On the one hand most of the subscriptions come in without issues, on the other, sometimes customers have a set period of 60 days, some have 28 days, some have 0 days, etc... I also sometimes get a period that says "LIFETIME - 11/10/2010" (the date would represent 'today's date.


    Example of a "LIFETIME", 30 (normal), and 0 day timeframes
    http://screencast.com/t/70kXM3kRLDD

    One with a weird 15 day timeframe
    http://screencast.com/t/Shx3Oqie


    Especially weird is that all of these are marked as paid. I don't want my customers to come back fuming, or worse yet, leave all together.


    I'd love some input on this... maybe narrowing down what the problem actually is, figuring out what I can do to fix it, and *gasp* even fixing the problem altogether.


    Thanks in advance
  2. davidm1

    davidm1 aMember User & Partner

    Joined:
    May 16, 2006
    Messages:
    4,437
    Sounds like some strange bug- contact tech support.

    David
  3. menspsy

    menspsy New Member

    Joined:
    Aug 4, 2010
    Messages:
    24
    I have the same issue, although I am not able to reproduce this at will.
    Some customers' subscription are set for a wrong time periods (60 days instead of 14 days). They are paying customers (1Shoppingcart).

    Have you been able to find the bug?
  4. alexander

    alexander Administrator Staff Member

    Joined:
    Jan 8, 2003
    Messages:
    6,279
    Please contact us in helpdesk.
    There are some strange things happen with 1SC notifications in past days. Sometimes notifications have correct nextrebillingdate variable and sometimes not.
    aMember use that var as expiration date for next payment, so if 1SC send incorrect value here, aMember will create incorrect payment.

Share This Page