• Resolved Henry

    (@henrybaum)


    The new UI keeps spinning. When clicking “Payments” in settings, there’s a popup saying “Error retrieving payment details.” The Payments page loads, but the Manage page isn’t loading, or taking a very long time and then not loading when switching to a new tab.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @henrybaum

    First, please check if you have any plugin enabled that disables or modifies the new WooCommerce UI (for example something like “Disable the new UI” or similar). If so, please disable it temporarily and test again.

    Additionally, to properly investigate this on our side, we’ll need your system report. Please follow these steps to share it with us:

    1. Navigate to WooCommerce → Status in your admin panel.
    2. Click on “Get system report”, then “Copy for support”.
    3. Paste the report into: http://privatebin.syde.com/
    4. Share the generated link here so we can review it.

    We are waiting for your system report to proceed with further analysis.

    Kind Regards
    Krystian

    Thread Starter Henry

    (@henrybaum)

    The disable UI plugin doesn’t seem to be working anymore – it’s now disabled. If it helps, getting “Failed to load ApplePay dependencies: Timeout while waiting for widgetBuilder.paypal” Also GooglePay dependencies.

    https://privatebin.syde.com/?47aeeb035a3fe21a#3jLCyPGoyuq21cNy8z2sJdWHCQbBtuf9obnYSJceHHYE

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @henrybaum

    The “Failed to load dependencies” indicates that something is interfering with the PayPal script initialization. Please temporarily disable all other plugins, especially any that add custom snippets or inject scripts. Also, make sure to disable any caching layers (plugin-based caching, server-side cache, CDN if applicable).

    These types of issues are very often caused by caching or script interference preventing proper loading order.

    Once done, test again and see if UI page loads correctly.

    Kind Regards
    Krystian

    Thread Starter Henry

    (@henrybaum)

    I turned Code Snippets off and on and it seems to be working so far. The only snippets related to the Woocommerce back end are one for editing orders and custom order meta.

    Thread Starter Henry

    (@henrybaum)

    This is still an issue on a live site – Overview loads, but not Payment Methods or Settings. On Overview there’s this error:

    Failed to load ApplePay dependencies: Timeout while waiting for widgetBuilder.paypal ppcp-applepay-js-boot-admin.js:1:24477

    [ApplePay | preview-manager] configuration object cannot be retrieved from PayPal ppcp-applepay-js-boot-admin.js:1:9980

    Failed to load GooglePay dependencies: Timeout while waiting for widgetBuilder.paypal ppcp-googlepay-js-boot-admin.js:1:24477

    [GooglePay | preview-manager] configuration object cannot be retrieved from PayPal ppcp-googlepay-js-boot-admin.js:1:9980

    I can’t disable each snippet to see if there’s a conflict.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @henrybaum

    I can’t disable each snippet to see if there’s a conflict.

    Why? Its the only reasonable way to find which snippet is contributing to the issue.

    Kind regards,
    Krystian

    Thread Starter Henry

    (@henrybaum)

    I have 40 snippets and it’s a live site. There may be a conflict with two or three of them, so it may not be possible to check. Is there a type of snippet that’s usually a problem? Most running are for the front end.

    Plugin Support Krystian Syde

    (@inpsydekrystian)

    Hello @henrybaum

    With that number of snippets, the potential scope is quite broad, so it’s difficult to point to a single “type” that would typically cause the issue. In practice, conflicts can come from various areas depending on what the snippets modify. The most reliable way to narrow it down is testing:

    • First, temporarily disable all snippets and check if the issue still occurs
    • If it’s resolved, then it confirms a snippet conflict
    • After that, re-enable them in batches (e.g. 4–5 at a time) until the issue reappears

    This is usually the fastest way to isolate the problematic one.

    Kind Regards,
    Krystian

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

You must be logged in to reply to this topic.