• Resolved michael1309

    (@michael1309)


    After the update to version 2.0.1 you can no longer log in to the customer account. When you enter your data, the customer account does not come, but a page with info about PHP 7.4.

    I first reset all plugins and played once again. Finally, only the Amazon plugin was left. Of course this is not great because we have not received any order for a few days, as customers could not log in.

    Nach dem zurücksetzen auf die Version 1.13.1 geht wieder alles. man muss dann nur beachten, sich wieder mit amazon zu verbinden.

Viewing 15 replies - 1 through 15 (of 17 total)
  • Yes same with our shop – no good! Reconnected shop with amazon – no success.

    Customer gets ‘There was an error while processing your payment. Your payment method was not charged. Please try again. If the error persists….’

    We will then switch back too, as michael1309 suggested.

    Plugin Support Christian

    (@christian1983)

    Hey @michael1309 @hdca,

    Hope you are doing well!

    try to check the following link conflict test on a Staging site, could be some plugin or even the Theme you are using. We need to isolate the problem first.

    If you can’t find the issue, please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.
    Please include a link to this forum thread, so that we can keep track of what’s already been done.
    We will be able to help you further there.

    Best,
    Christian

    Thread Starter michael1309

    (@michael1309)

    Hey Christian,

    our life site is: https://www.nolimitshoes.com

    I have tested the new version of the plugin on our test site. But i cannot make the test till the end, because i cannot connect to amazon because our testsite has an othe domain.

    But i am shure that the new version of the amazon plug makes this problem.

    if i make the update and go after to the login in our site, i see the info site from php 7.4 after i click on the button anmelden/login.

    Hi Christian, great to hear from you – thanks. In our case: Nothing has been changed with the configuration of the site – except of the Amazon Pay Update.

    Small Note by the way – in the newer Version I was not able to fill in the given (old) credentials and keys from MWS by hand – intended? I think it was quite handy to put them in the fields….

    Cheers, Philipp

    Thread Starter michael1309

    (@michael1309)

    I have tested the problem now serveral times. allways the same. customer loggin dont work.

    We dont use amazon pay in our site in the future.

    By

    Michael

    Plugin Support Christian

    (@christian1983)

    Hey @michael1309 @hdca ,

    You can check the following links, so you can manual transfer your keys and set up your Amazon Seller accounts.

    I am having the same problem. Since I moved to version 2.0.1 WordPress crashes due to problems.

    I contacted Amazon but they tell me the problem is with the plugin.

    If I disconnect the WordPress plugin it works normally again.

    Plugin Support Christian

    (@christian1983)

    Hey @angeldavo

    do you have any logs so we can check?

    Best,
    Christian

    Hi, I had to go back to the previous version as I could not have Amazon Pay disabled.

    Same issue here. Here is the fatal error in my logs:

    2021-05-25T19:48:05+00:00 CRITICAL Uncaught Error: Object of class WP_User could not be converted to string in html/wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/vendor/phpseclib/phpseclib/phpseclib/Crypt/RSA.php:480
    Stack trace:
    #0 html/wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/vendor/phpseclib/phpseclib/phpseclib/Crypt/RSA.php(480): phpinfo()
    #1 html/wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/vendor/amzn/amazon-pay-api-sdk-php/Amazon/Pay/API/Client.php(402): phpseclib\Crypt\RSA->__construct()
    #2 /html/wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/vendor/amzn/amazon-pay-api-sdk-php/Amazon/Pay/API/Client.php(379): Amazon\Pay\API\Client->setupRSA()
    #3 html/wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/includes/class-wc-amazon-payments-advanced-api.php(321): Amazon\Pay\API\Client->generate in /html/wp-content/plugins/woocommerce-gateway-amazon-payments-advanced/vendor/phpseclib/phpseclib/phpseclib/Crypt/RSA.php on line 480

    Also, I’m seeing an issue with the “Link Amazon Pay Account (optional)” checkbox wrapping funny in the last checkout page on my site before they complete the order.

    Plugin Support Christian

    (@christian1983)

    Hey @jsuppes,

    Which are the step to reproduce the issue?

    there is a new version 2.0.2 . might fix your problem.

    Let me know,
    Best,
    Christian

    Hi Chrisian,

    Thanks for the quick response. It happens as mentioned above. We created a new account and one of our team members was trying to log in on the my account page. Once they clicked login it brought them to our PHP info page. Oddly enough when I tried the same thing on my computer, with the same user, it brought me right into the account. Very odd behavior.

    I upgraded and we are still seeing the issue. We did some additional work on this today and we are realizing this is happening only when someone creates a new account from the checkout process. You then have to log off and then try to login through the my account page, then you see the PHP info page.

    Plugin Support Christian

    (@christian1983)

    Hey @jsuppes,

    Please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.
    Please include a link to this forum thread, so that we can keep track of what’s already been done.
    We will be able to help you further there.

    Best,
    Christian

    Woocommerce support sent me to this forum to ask about this issue but I will reach back out to them.

    For my part I have uninstalled the plugin and started from 0 and it seems to work now.

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Massive Problem after update to 2.0.1’ is closed to new replies.