Failed Payment Method doesn’t work

  • Resolved gabrbowie

    (@gabrbowie)


    3 years, 3 months ago

    Hello!

    We are experiencing an strange issue since january 23th, when we switched to PHP 8.0.
    Subscriptions that have a payment failure (for whatever reason) are no longer automatically suspended, they are now still active and with access to the content. 
    So, since then we have had to manually block access every access with failed payment, as this fundamental function of the plugin (Failed Payment Method) has stopped working.  

    First we noticed that in the Payment History there were no more records with “Fail” status, and they always appeared.
    That is, the log only shows Success and Cancelled, and it shows nothing for cases where we are sure that there was a payment problem with the person’s subscription. We thought it was just a detail of the log not registering, but it seems to be related with this issue, because in addition to not registering as Fail, it also no longer automatically suspends the person’s plan (for any user). 

    What can we do to resolve?  

    Or maybe someone can help to show a direction on how to discover where is the problem, maybe a code or a log we can test/try. By the way, we checked the database directly and noticed that the Fail records aren’t being stored at all (and just for the “Fail” ones).


    Maybe it could be some incompatibility with PHP 8.0? We are sure the problems started the day we changed the version of PHP (and can’t go back now because our hosting doesn’t allow previous versions). 

    We have already checked and it does not seem to be interference from another plugin, so we need to know what could be done, as we need this primary function of the plugin to work correctly.

    Thank you for your attention!  

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author reputeinfosystems

    (@reputeinfosystems)

    3 years, 3 months ago

    Hello,

    I understood your concern and please note that if the failed payment does not happen then first confirm that the WordPress Scheduler Cron job is working you can check with available plugins like Crontrol at ww.wp.xz.cn and you can run the scheduler manually using this plugin too.
    If still issue persists then, kindly check the error log which may be stored on the server if the issue is causing so, kindly provide that error message from the error log, and after that, I can check and assist you further.

    Thanks

    Thread Starter gabrbowie

    (@gabrbowie)

    3 years, 3 months ago

    Hi! First of all, thank you for your support.

    I installed the Crontrol plugin, and I noticed here 2 crons which I believe are related to this:
    arm_handle_failed_payment_for_manual_subscription and arm_handle_failed_payment_for_auto_subscription.
    Are these the ones we should be paying attention? I assumed it is because of the name.
    It appears they are scheduled, but there’s one detail: in Action column, it shows None (“Nenhum”, in portuguese).
    Is this the expected value for these 2 crons? Or it should have something in Action column, like for the other armember crons?

    Take a look at the cron events for armember:

    I found this a big coincidence, because the one function that isn’t working is appearing like this in the cron events tab. If this is related somehow, what could we do to solve this?

    Thanks!

    Thread Starter gabrbowie

    (@gabrbowie)

    3 years, 3 months ago

    Hi! thanks in advance

    We took a closer look and checked the server logs, the cron is running as expected.
    We tried to run it manually too, directly through the server and through Crontrol, but the plans are still not suspended.

    Could you please check these two questions for me?

    1) Are those crons (in my question above) the ones responsible for managing payment failures?
    in my post I questioned why they were empty in the “Action” column, but I took a brief look at the code and I think I understand. In a recent update, it was changed from

    • arm_handle_failed_payment_for_auto_subscription
    • arm_handle_failed_payment_for_manual_subscription

    to

    • arm_handle_failed_payment_for_subscription_plan (action: ARM_crons->arm_handle_failed_payment_for_subscription_plan_func())

    can you confirm this information?

    2) Also, could it be not related to cron?
    And is this cron responsible for adding the Failed records to the database table, where it is recorded the payment logs? Because as I said, the logs for Failed are still not appearing directly in the database (Completed and Canceled appear normal). It is strange that only Failed ones are not appearing.

    Please tell me if is this the clue we should be looking for.

    Plugin Author reputeinfosystems

    (@reputeinfosystems)

    3 years, 2 months ago

    Hello,

    I understand your concern about “arm_handle_failed_payment_for_subscription_plan” cron showing the function but other hooks not. But please note that, this cron hook available in ARmember pro plugin only so, if you are using ARMember pro plugin then, kindly open support ticket from https://support.arpluginshop.com and after that, ARMember support staff will assist you further.

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Failed Payment Method doesn’t work’ is closed to new replies.