Skip to content

[TRACKER] Known Bugs & Limitations #402

@anktd

Description

@anktd
  1. Payment Method Discount: This config has multiple edge cases where it doesn't work as intended, particularly with payment method switching and UI/backend synchronization. Known problems:

a) Order Details Page: Discount applied through the configuration doesn't show up on the WooCommerce order details page as an applied discount (as seen in the order screenshot showing $75.87 paid but no discount line item visible).

Image

b) Inconsistent checkout display:
Sometimes the discount appears in the order summary, other times it doesn't. Display behavior depends on whether Blockonomics is selected at page load or if AJAX update is triggered when payment method changes

c) Payment method switching issues:

Blockonomics → Others: Discount line doesn't get removed from the bill when switching from Bitcoin to another payment method
Others → Blockonomics: Discount line doesn't show up and the final amount seems incorrect at checkout

  1. Test Setup - it has multiple limitations and can show false positives.
    Known problems:
    a) False positive on gap limit: Test Setup shows success even when wallet has hit gap limit, not accurately reflecting the actual state

b) Manual update requirement: Must manually hit "Test Setup" button to:
(i) Add or remove cryptocurrencies supported on the store
(ii) Reflect store name updates in settings
(iii) Generally sync any configuration changes

c) Incomplete validation: Current test setup flow looks good but needs minimal code/automation to check stores/set callback. User must manually copy/paste callback URL in stores UI. Once server-side responses improve, extra code can be removed from test setup.

Already added as issue #382

  1. Web3 Wallet disconnection: Plugin doesn't provide a way to disconnect the wallet once connected to a Store.
    Users must navigate to wallet settings manually > Go to "All permissions" > Choose website to disconnect the wallet
    No in-plugin disconnect option available

  2. API Timeout Error Handling - API timeouts display error template along with timeout message, creating poor UX.
    Already added as issue API Timeout displays error template #392

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions