CRM-15945 Membership Auto-Renew fails to create recurring contribution

    Details

    • Type: Bug
    • Status: Done/Fixed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 4.5.5, 4.5.6
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Documentation Required?:
      None

      Description

      Defined membership types with "Auto-renew required" specified do not generate a recurring contribution. This occurred on a live instance of 4.5.5, as well as in the 4.5.6 sandbox.

      1) Create new Membership Type in CiviMember. Attributes: Rolling, 1 Month, Required.

      2) Created Contribution Page specifying newly created Membership Type. (And turning on Payment Processor.)

      3) Submitting new membership using new contribution page.

      A review of the resulting transaction does not show a recurring contribution as expected.

        Attachments

          Activity

          [CRM-15945] Membership Auto-Renew fails to create recurring contribution
          David Greenberg added a comment -

          David -

          • Which payment processors(s)?
          • Have you checked webserver and CiviCRM logs for any clues?
          • How are you replicating on the 4.5.6 sandbox (live payment processor transactions w/ recurring aren't able to be submitted AFAIK on the CiviCRM demos)?
          David Doligalski added a comment -

          The problem on the live 4.5.5 site, is using authorize.net.

          I did check both the watchdog log as well as the civicrm log and did not note any hints of the problem.

          On the sandbox, we simply used the dummy processor. It does work properly on the 4.4 sandbox with the dummy payment processor.

          Note also: The recurring payments on memberships did work prior to upgrading from 4.4.x to 4.5.5. We tried recreating the contribution page, but that too did not work.

          -Dave

          David Greenberg added a comment -

          David - Can you check w/ some other folks on the IRC channel who's clients use Auth.net + recurring? I think there may have been some changes from 4.4 to 4.5 such that the recurring contribution record isn't created until the processor confirms, but not sure about that. Are you seeing evidence of confirmation from Auth.net on creation of the 'subscription' for the live site transactions ??

          It's possible that this flow is completely broken in 4.5 - but that seems less likely than a configuration issue or ??

          Eileen McNaughton added a comment -

          I think this relates

          https://issues.civicrm.org/jira/browse/CRM-15527

          This patch went into 4.4 & I had thought it went into 4.5 but I'm less sure looking at the ticket.

          The patch & tests were originally written against master so 4.6 should be fine.

          From memory the important part of the patch is this line

          https://github.com/civicrm/civicrm-core/commit/6fa0515e143d992018a52245c5d8acf564e03651#diff-7a5b0e2d131dabc49178460fc63328c0L240

          Kurund Jalmi added a comment -

          CRM-15527 is fixed for 4.6 and not 4.5

          David Doligalski added a comment -

          CRM-15527 is definitely in 4.5.5.

          With these patches applied there remains an issue. Recurring memberships are still having an issue. It appears that the proper transaction is occurring on the first instance of the day (anecdotally) but then fails to properly post on subsequent transactions.

          David Greenberg added a comment -

          David - I don't think it's possible for us to work on this w/o more debugging info. I'd suggest adding some debugging statements which write to the Civi log file to try and get a handle on this. If you need help figuring out where to add debug statements - probably best to jump on IRC.

            People

            • Assignee:
              Unassigned
              Reporter:
              David Doligalski

              Dates

              • Created:
                Updated:
                Resolved: