Jump to content

Al Brookbanks

Staff
  • Posts

    6,638
  • Joined

  • Last visited

  • Days Won

    123

Posts posted by Al Brookbanks

  1. 50 minutes ago, foz1234 said:

    Due to SemperFIWebServices no longer being around and supporting my plugins, my CC is pretty much stuck on 6.2.5 and PHP 7.2

    Just wondering if I can create a new temporary CC store in say https://mydomain/test folder, then upload a back from my main store, no need for customer details, I just want to see at what point/CC version my plugins break if indeed they do, trying to avoid killing my online store and needing to restore it. 

    SemperFIWebServices plugin's currently running:

    SFWS Custom Foundation 5 Skin V3.3.0

    SFWS Special Content Boxes V4.1.0

    SFWS Homepage Featured Products V4.0.0

    Site Messages v4.0.0

     

    Asking to assess if this will actually work?

    Your thoughts appreciated. 

     

    Absolutely you can. Are the plugins encoded? If so then you are stuck. If not the code can be updated to work with PHP8.

  2. 7 minutes ago, Debyink said:

    Al, I'm still having this problem and still loosing money due to the no refundable fees.

    I believe you but I need clues at minimum. Have any customers mentioned faults or unexpected behaviour?

    We found a problem caused by hitting "Pay Now" more than once. This has been patched. It's incredibly disappointing to see issues persists especially without any information as to how. 

  3. This issue is incredibly infuriating. I've spent hours trying to reproduce this on various devices coving as many scenarios as I can think of. It doesn't seem to affect that many merchants and those it does aren't able to reproduce it either.

    If I can reproduce this I can fix it. I'm desperate to get to the bottom of it as you are.

    Are there any errors in the request log with the order number in the body?

  4. authenticationReason: ERROR is the clue.

    This means your customer has failed the security challenge set by their bank (not PayPal) and your PayPal Commerce settings are set to reject this scenario. 

    Check your 3D Secure Scenarios in the module extension config page. In particular "Buyer may have failed the challenge or the device was not verified."

  5. 33 minutes ago, Debyink said:

    How do I check these
     

    Just done a quick view page source on my checkout screens (whether as a guest, logged in or just using the Paypal button) on my site found these on all so is this ok:

    method="post" enctype="multipart/form-data" class="autosubmit" id="checkout_form"

    button type="submit" name="proceed" id="checkout_proceed"

     

     

    You should be good based on that. It's quite easy to reproduce on an iPad.

    Pay with the shortcut yellow button. If you hit the pay now button twice it then goes to a new payment screen instead of going to the processing page. This disables the button so it can only be clicked once.

×
×
  • Create New...