Establishing a working sandbox testing environment on another URL

  • Resolved RalfS2

    (@ralfs2)


    1 year, 11 months ago

    Dear Inpsyde Team,

    meanwhile I have successfully set up my testing environment with this plugin.
    I took a look in the backend of PayPal (developer.paypal.com) what the plugin is doing during “Onboarding”.
    Obviously it creates more then only SECRET KEYs etc. It even writes down the complete URL of my testshop in a webhook.

    My common process when testing changes in our shop is, to use “All in one WordPress migration” plugin to create a backup of this shop and unpack it in my testing environment. Means, I have 2 different URLs.
    For example:
    a) myliveshop.com
    b) mytestshop.com

    How do have to setup my Live and Sandbox credentials when going online???
    My process would be the following, to have a working shop AND testshop:

    1. Set WordPress in maintenance mode
    2. Deactivate the “old” PayPal Plus plugin for WooCommerce from Inpsyde
    3. Install the new pluging “WooCommerce PayPal Payments” and activate it.
    4. Use the wizard of the plugin to connect to the productive PayPal account.
    5. I digged out the four neccessary informations for the sandbox mode from my test environment already
    and enter it in the “manual setup” section for the sandbox (Do not use the wizard for it!)
    6. When copying my shop to the testing environment, I need to enable the “sandbox mode” hook only.

    Can you confirm this process?

    In my opinion it will lead to problems if I use both wizards (Live and Sandbox) of your plugin in the productive environment and copying it afterwards to another URL for testing and sandbox mode. Sandbox mode will not work in this case. Right?

    Best regards
    Ralf

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi @ralfs2,

    In my opinion it will lead to problems if I use both wizards (Live and Sandbox) of your plugin in the productive environment and copying it afterwards to another URL for testing and sandbox mode. Sandbox mode will not work in this case.

    I’m not sure why sandbox mode wouldn’t work then? Can you elaborate further?
    When the site URL changes after the webhooks were registered, then the webhooks must be resubscribed.

    You can connect the API credentials manually, but the onboarding wizard is the recommended way, as reusing API credentials can lead to issues.
    Every onboarding attempt creates a new REST App, enables tracking & Vaulting and also subscribes to the webhooks.

    When you manually connect the API credentials, the webhooks must be manually subscribed.
    And you may also need to remove webhooks from the App when you are reusing the same API credentials, e.g. after copying the site to a different domain.
    So in the end, everything only gets more complicated when using manual credential input, and it should only be used if all else fails.

    When the site URL changed after the setup, the best practice would be to reconnect the account to ensure a new REST App is created and configured correctly.

    Kind regards,
    Niklas

    Thread Starter RalfS2

    (@ralfs2)

    Hi Niklas,
    Ok, brilliant background informations!
    Understanding the backgrounds means that I now what I am doing ;)) and will not be surprised about “strange” results.
    Thanks a lot!

    Now I know what for my environment will be the best process:
    I need to go through the process of the wizard twice.
    Once in my productive URL, and once in my testing environment URL.
    And thats it. As long as I do not change the URL for a third time, everything is all right then.

    I think you can close this issue now.

    Best regards
    Ralf

    Plugin Support Syde Niklas

    (@niklasinpsyde)

    Hi Ralf,

    I need to go through the process of the wizard twice.
    Once in my productive URL, and once in my testing environment URL.

    That’s the best way to ensure the account connection is established properly.
    Since the webhook registration happens per app, conflicting webhooks events could potentially cause problems with orders when the same API credentials are reused.

    But if you still encounter any questions along the way, don’t hesitate to let us know.
    Thanks!

    Kind regards,
    Niklas

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Establishing a working sandbox testing environment on another URL’ is closed to new replies.