Recent Update, Conflict and Nag

  • Resolved ZoBabe

    (@zobabe)


    1 year, 3 months ago

    Our store is in a country with currency not supported by PayPal. I have a currency converter that works beautifully with PayPal for supported currencies, while allowing use to keep our base currency local.
    So, the “Your base currency is not supported by Paypal” nag is irrelevant to our setup, and I would like to disable it.
    Additionally, Paypal now conflicts with our gateway for local currency payments and causes a 500 error when enabled.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @zobabe

    Thank you for reaching out to us, we are here to help.

    If you are not able to press “x” on this notice, there is not much you can currently do to get rid of this notice. We already have an open issue for this notice issue and see that it is already in the test phase. If you want, you can find more details on this effort here on GitHub. This improvement will only show the notice in the PayPal payments settings pages, and the positioning is a bit different. We have added the requirement to correct the dismissible notice issue to this bug.

    This fix should be included in our next feature update (not the next update) that is expected at the end of September (we expect this to be release 2.3.0).

    Now, you also reported “PayPal now conflicts with our gateway for local currency payments and causes a 500 error when enabled.”, which is a bit unclear to us. Can you explain to us what occurs, what error you are seeing, and what the effects are of this situation? If needed, you can also open a private thread, in order to share logs or other details that you maybe don’t want to share via a public forum.

    Let me know how you want to proceed.

    Kind regards,
    Joost

    Plugin Support Syde Joost

    (@joostvandevijver)

    Hello @zobabe

    This bug was fixed, so it is planned to be included in the next (2.3.0) release that is currently being tested. I would expect this release to occur in 2 weeks, but that would be the timing if we don’t run into any issues.

    Please check this release when it becomes available or open a private thread if you want to test a testing package.

    If the issue is not resolved with the next release, feel free to open a new thread.

    Kind regards,
    Joost

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Recent Update, Conflict and Nag’ is closed to new replies.