Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No visual difference between Live and Sandbox mode for merchants. #6

Open
thomasjvu opened this issue Jul 25, 2024 · 1 comment
Open
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.

Comments

@thomasjvu
Copy link

Describe the Bug

When comparing the GoCardless Settings page while logged in to a live instance vs a sandbox instance, visually the two look identical which can cause confusion to users who may be unsure if they're connected to a live or sandbox instance of GoCardless.

In the video below, I show that you are unable to use test banking information on a live site as an error that the payment information "is reserved" will occur. This isn't that big of a problem, but its confusing when merchant's can't see anywhere whether or not they are currently connected to live or sandbox mode (as I thought I was already logged in via sandbox...)

To Reproduce

  1. Go to WooCommerce > Settings > Payments > GoCardless, and then login to GoCardless normally.
  2. Notice that there is no indicator of being on Live or Sandbox mode on the page and then disconnect.
  3. Log in to the Sandbox version of GoCardless and see that there is no indicator of being on Live or Sandbox mode.

Screenshots

GoCardless.sandbox.mov

Expected Behavior

I expect that there should be a notice when test mode is enabled, similar to WooPayments:

2ULWnE.png

Actual Behavior

In actuality, there is no difference visually when I am connected to Live or Sandbox mode, which is somewhat confusing.

Environment

  • WordPress Version. 6.6.1
  • WooCommerce Version. 9.1.3
  • Plugin Version: 2.7.1
  • Browser [e.g. Chrome, Safari] and Version: Chrome 126.0.6478.183
  • Any other plugins installed: N/A

Additional Details

Disclaimer: I'm not sure if this is more of a bug or feature request, but I discovered it while I was trying to troubleshoot Issue #344. I was in live mode and trying to use test bank information, causing my checkout not to go through.

I've seen other users who have a specific _live key, which could serve as an identifier, but that information is hidden under a dropdown. Also, mine doesn't have that even when I regenerate my key, so I'm unsure if that is still the standard.

In any case, I think it would be helpful to have some sort of identifier on the GoCardless settings page (or perhaps the checkout) that I am either in Live or Sandbox mode.

System Status Report
### WordPress Environment ###

WordPress address (URL): [Redacted]
Site address (URL): [Redacted]
WC Version: 9.1.3
Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.
Action Scheduler Version: ✔ 3.7.4
Log Directory Writable: ✔
WP Version: 6.6.1
WP Multisite: –
WP Memory Limit: 512 MB
WP Debug Mode: –
WP Cron: ✔
Language: en_US
External object cache: ✔

### Server Environment ###

Server Info: nginx
PHP Version: 8.2.21
PHP Post Max Size: 2 GB
PHP Time Limit: 1200
PHP Max Input Vars: 6144
cURL Version: 8.7.1
OpenSSL/1.1.1w

SUHOSIN Installed: –
MySQL Version: 10.6.15-MariaDB-log
Max Upload Size: 2 GB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔

### Database ###

[REDACTED]

### Post Type Counts ###

attachment: 1
page: 7
post: 1
product: 2
revision: 1
shop_order_placehold: 15
wp_global_styles: 1
wp_navigation: 1
wp_template: 2

### Security ###

Secure connection (HTTPS): ✔
Hide errors from visitors: ✔

### Active Plugins (2) ###

WooCommerce GoCardless Gateway: by WooCommerce – 2.7.1
WooCommerce: by Automattic – 9.1.3

### Inactive Plugins (5) ###

Akismet Anti-spam: Spam Protection: by Automattic - Anti-spam Team – 5.3.3
Jetpack: by Automattic – 13.7-a.5
Jetpack Protect: by Automattic - Jetpack Security team – 2.2.0
Pressable OnePress Login: by Pressable – 1.3.2
WooCommerce Subscriptions: by WooCommerce – 6.5.0

### Dropin Plugins () ###

advanced-cache.php: advanced-cache.php
object-cache.php: Memcached

### Settings ###

API Enabled: –
Force SSL: –
Currency: USD ($)
Currency Position: left
Thousand Separator: ,
Decimal Separator: .
Number of Decimals: 2
Taxonomies: Product Types: external (external)
grouped (grouped)
simple (simple)
subscription (subscription)
variable (variable)
variable subscription (variable-subscription)

Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)
exclude-from-search (exclude-from-search)
featured (featured)
outofstock (outofstock)
rated-1 (rated-1)
rated-2 (rated-2)
rated-3 (rated-3)
rated-4 (rated-4)
rated-5 (rated-5)

Connected to WooCommerce.com: –
Enforce Approved Product Download Directories: ✔
HPOS feature enabled: ✔
Order datastore: Automattic\WooCommerce\Internal\DataStores\Orders\OrdersTableDataStore
HPOS data sync enabled: –

### Logging ###

Enabled: ✔
Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2
Retention period: 30 days
Level threshold: –
Log directory size: 345 KB

### WC Pages ###

Shop base: #5 - /shop/
Cart: #6 - /cart/ -  Contains the woocommerce/cart block
Checkout: #7 - /checkout/ -  Contains the [woocommerce_checkout] shortcode
My account: #8 - /my-account/
Terms and conditions: ❌ Page not set

### Theme ###

Name: Twenty Twenty-Three
Version: 1.3 (update to version 1.5 is available)
Author URL: https://wordpress.org
Child Theme: ❌ – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme
WooCommerce Support: ✔

### Templates ###

Overrides: /wordpress/plugins/woocommerce/9.1.3/templates/block-notices/error.php
/wordpress/plugins/woocommerce/9.1.3/templates/block-notices/notice.php
/wordpress/plugins/woocommerce/9.1.3/templates/block-notices/success.php


### Admin ###

Enabled Features: activity-panels
analytics
product-block-editor
coupons
core-profiler
customize-store
customer-effort-score-tracks
import-products-task
experimental-fashion-sample-products
shipping-smart-defaults
shipping-setting-tour
homescreen
marketing
mobile-app-banner
navigation
onboarding
onboarding-tasks
product-custom-fields
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page
launch-your-store

Disabled Features: experimental-blocks
minified-js
pattern-toolkit-full-composability
product-pre-publish-modal
printful
settings
async-product-editor-category-field
product-editor-template-system

Daily Cron: ✔ Next scheduled: 2024-07-26 16:37:47 +00:00
Options: ✔
Notes: 86
Onboarding: -

### Action Scheduler ###

Complete: 119
Oldest: 2024-07-05 06:22:17 +0000
Newest: 2024-07-25 20:01:50 +0000

Failed: 1
Oldest: 2024-07-19 15:34:51 +0000
Newest: 2024-07-19 15:34:51 +0000

Pending: 2
Oldest: 2024-07-26 18:52:38 +0000
Newest: 2025-07-19 15:39:14 +0000


### Status report information ###

Generated at: 2024-07-25 20:08:27 +00:00
@thomasjvu thomasjvu added the type: bug The issue is a confirmed bug. label Jul 25, 2024
@vikrampm1 vikrampm1 added the priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. label Jul 26, 2024
@jeffpaul
Copy link
Collaborator

This is not a high priority nor a blocker, but I agree that some UI notice in the admin that the site is on the GoCardless sandbox/test mode would be ideal. Something like a non-dismissable admin notice or something akin to the WooPayments example noted above.

@diegocurbelo diegocurbelo transferred this issue from another repository Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. type: bug The issue is a confirmed bug.
Projects
None yet
Development

No branches or pull requests

3 participants