Title: Plugin broke after migration Last modified: November 4, 2025 --- # Plugin broke after migration * Resolved [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/) * We changed webhosts but nothing else changed as far as domain. * **WooCommerce Stripe Gateway** is broken * Under PAYMENTS, the plugin appears about 7 times, one showing active * If I try to save settings I get error saving settings or error retrieving keys * These show up as 404 in dev tools * wp-json/wc/v3/wc_stripe/settings?_locale=user wp-json/wc/v3/wc_stripe/account_keys? _locale=user * and finally the checkout page is all broken * Uncaught TypeError: o.extend is not a function at jquery.mask.min.js?ver=10.0.1: 1:6915at jquery.mask.min.js?ver=10.0.1:1:166at jquery.mask.min.js?ver=10.0.1: 1:174 * Any thoughts on what’s going on here? * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fplugin-broke-after-migration%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 15 replies - 1 through 15 (of 16 total) 1 [2](https://wordpress.org/support/topic/plugin-broke-after-migration/page/2/?output_format=md) [→](https://wordpress.org/support/topic/plugin-broke-after-migration/page/2/?output_format=md) * Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/) * (@frankremmy) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18707263) * Hello [@pwizard](https://wordpress.org/support/users/pwizard/), * Thank you for sharing these details following your web host change. It sounds like the Stripe plugin is encountering several issues, including: - Duplicate plugin entries under Payments - 404 errors on REST API endpoints - JavaScript errors breaking the checkout page * To help diagnose and resolve these problems, here are some steps you can follow: * 1. Stripe Gateway Appearing Multiple Times * This usually indicates plugin duplication or caching issues. - Check your `wp-content/plugins` directory via FTP or your hosting file manager to confirm there’s only one Stripe plugin folder - Clear any server-side caching (object cache, opcode cache) and your browser cache * 2. REST API 404 Errors * These suggest permalinks weren’t flushed or rewrite rules are missing post-migration. - Go to WordPress Admin → Settings → Permalinks, and click “Save Changes” without modifying anything - Confirm your `.htaccess` file (if using Apache) or server rewrite config allows URL rewriting - Ensure your Site URL and WordPress URL under Settings → General match your current domain * 3. JavaScript Error: `Uncaught TypeError: o.extend is not a function` * This typically points to a jQuery conflict or version mismatch. - Make sure the jQuery library loads before `jquery.mask.min.js` - Check that no scripts are dequeued or loading out of order - This may be related to how your new host handles script loading * 4. To isolate conflicts: - Deactivate all plugins except WooCommerce and Stripe Gateway - Clear caches and test again - If resolved, reactivate plugins one by one to identify the conflict * 5. Gather more insights: - Enable debug logging in `wp-config.php`: `define('WP_DEBUG', true); define(' WP_DEBUG_LOG', true);` - Check WooCommerce → Status → Logs for Stripe-related entries - Feel free to share relevant log snippets for further help * If the issue persists, I’d like to understand your site properly. Please share your System Status Report which you can find via `WooCommerce → Status`. Select` Get system report` and then `Copy for support`. Once you’ve done that, you can paste it into your reply here. You could copy and paste your reply here or paste it via [https://gist.github.com/](https://gist.github.com/) and send the link here. * Looking forward to your update so we can get Stripe Gateway back in working order! * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18707293) * Thanks for the reply. It may be possible CURL is not installed or misconfigured. I am waiting for support. In the meantime do you think that could a possiblity? * Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/) * (@frankremmy) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18707309) * Hi [@pwizard](https://wordpress.org/support/users/pwizard/), * Yes, the absence or misconfiguration of the cURL PHP extension can definitely cause problems with the Stripe gateway and other HTTPS requests in WordPress. Stripe relies on cURL to communicate securely with its servers. * While waiting for your host’s confirmation, you can check if cURL is enabled on your site by doing the following: - Go to WooCommerce → Status → System Status. - Scroll down to the “Server Environment” section and look for “cURL support.” It should say “enabled.”: [https://share.zight.com/X6uy4KQb](https://share.zight.com/X6uy4KQb). * If cURL is missing or disabled, you’ll need to ask your host to install or enable the PHP cURL extension. This is a common server requirement for payment integrations and many other plugins. * Additionally, ensuring your SSL certificates are correctly configured and your server can make outbound HTTPS calls will help prevent issues. * But before we jump to a conclusion, could you confirm if you followed those steps I shared? That way, we’ll narrow it down as much as possible. * Looking forward to your update! - This reply was modified 7 months ago by [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/). * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18707321) * Yes I followed the other steps * Interestingly a terminal bash shows 7.58.0. * The system status report shows NO verison next to Curl – it’s blank * I noticed this afternoon that I accicdently uploaded the entire wordpress folder into the plugin folder lol * I thought that was the problem and it would resolve when i deleted it all and reinstalled. Nope. * I’ll check back tomorrow after my host support gets back to confirm. Thanks. * Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/) * (@frankremmy) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18707339) * Hi [@pwizard](https://wordpress.org/support/users/pwizard/), * Thank you for the update and for confirming the steps you’ve already taken. The fact that the system status report shows no version next to cURL indicates that cURL may not be properly enabled or detected by your WordPress installation, even though the terminal shows version 7.58.0. This discrepancy often arises when the PHP cURL extension is missing or misconfigured on the server side, rather than the underlying system cURL binary. * Your accidental upload of the entire WordPress folder into the plugins directory is an understandable mistake, and deleting it to return to a clean state was a good move. Since that did not resolve the issue, focusing on the server environment, especially verifying PHP extensions, is the right approach. * The best next step is to follow up with your host to confirm that: - The server’s PHP configuration is correctly loading the cURL extension. - There are no permission or security restrictions blocking cURL usage. - The SSL certificates and outbound HTTPS requests are working without issues. * Once your host confirms this or applies fixes, it would be helpful to re-check WooCommerce → Status to see if the cURL version now appears correctly. * If cURL does get enabled and you continue to see issues, sharing your updated System Status Report could provide further clues. * I hope that helps. Let us know if you need anything else. * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18708013) * ```wp-block-code WordPress Environment

WordPress address (URL): XXXXX
Site address (URL): https://xxxx.com
WC Version: 10.3.4
Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.
Action Scheduler Version: ✔ 3.9.3
Log Directory Writable: ✔
WP Version: 6.8.3
WP Multisite: –
WP Memory Limit: 2 GB
WP Debug Mode: ✔
WP Cron: –
Language: en_US
External object cache: ✔ Server Environment

Server Info: nginx/1.28.0
Server Architecture: Linux 4.15.0-135-generic x86_64
PHP Version: 8.3.27
PHP Post Max Size: 250 MB
PHP Time Limit: 120
PHP Max Input Vars: 1000
cURL Version: 7.58.0
OpenSSL/1.1.1

SUHOSIN Installed: –
MySQL Version: 10.11.5-MariaDB-1:10.11.5+maria~ubu1804
Max Upload Size: 200 MB
Default Timezone is UTC: ✔
fsockopen/cURL: ✔
SoapClient: ✔
DOMDocument: ✔
GZip: ✔
Multibyte String: ✔
Remote Post: ✔
Remote Get: ✔ Database

WC Database Version: 10.3.4
WC Database Prefix: FiAWTy_
Total Database Size: 44.28MB
Database Data Size: 34.56MB
Database Index Size: 9.72MB
FiAWTy_woocommerce_sessions: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
FiAWTy_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_woocommerce_downloadable_product_permissions: Data: 0.08MB + Index: 0.13MB + Engine InnoDB
FiAWTy_woocommerce_order_items: Data: 0.05MB + Index: 0.02MB + Engine InnoDB
FiAWTy_woocommerce_order_itemmeta: Data: 0.23MB + Index: 0.20MB + Engine InnoDB
FiAWTy_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
FiAWTy_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
FiAWTy_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB
FiAWTy_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
ahm_files: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
FiAWTy_actionscheduler_actions: Data: 0.31MB + Index: 0.80MB + Engine InnoDB
FiAWTy_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_actionscheduler_logs: Data: 0.20MB + Index: 0.14MB + Engine InnoDB
FiAWTy_commentmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
FiAWTy_comments: Data: 0.15MB + Index: 0.07MB + Engine MyISAM
FiAWTy_fsmpt_email_logs: Data: 1.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM
FiAWTy_litespeed_url: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_litespeed_url_file: Data: 0.02MB + Index: 0.08MB + Engine InnoDB
FiAWTy_newsletter: Data: 0.41MB + Index: 0.13MB + Engine InnoDB
FiAWTy_newsletter_emails: Data: 0.23MB + Index: 0.00MB + Engine InnoDB
FiAWTy_newsletter_logs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_newsletter_sent: Data: 0.47MB + Index: 0.34MB + Engine InnoDB
FiAWTy_newsletter_stats: Data: 0.39MB + Index: 0.20MB + Engine InnoDB
FiAWTy_newsletter_user_logs: Data: 0.08MB + Index: 0.00MB + Engine InnoDB
FiAWTy_newsletter_user_meta: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_options: Data: 2.74MB + Index: 0.13MB + Engine MyISAM
FiAWTy_postmeta: Data: 4.20MB + Index: 1.72MB + Engine MyISAM
FiAWTy_posts: Data: 3.90MB + Index: 0.40MB + Engine MyISAM
FiAWTy_post_smtp_logmeta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_post_smtp_logs: Data: 1.52MB + Index: 0.00MB + Engine InnoDB
FiAWTy_psk_s2msfb_downloads: Data: 1.10MB + Index: 0.11MB + Engine MyISAM
FiAWTy_psk_s2msfb_files: Data: 0.22MB + Index: 0.11MB + Engine MyISAM
FiAWTy_smush_dir_images: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_taxonomymeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_terms: Data: 0.00MB + Index: 0.02MB + Engine MyISAM
FiAWTy_term_relationships: Data: 0.12MB + Index: 0.26MB + Engine MyISAM
FiAWTy_term_taxonomy: Data: 0.01MB + Index: 0.01MB + Engine MyISAM
FiAWTy_usermeta: Data: 3.43MB + Index: 1.16MB + Engine MyISAM
FiAWTy_users: Data: 0.12MB + Index: 0.09MB + Engine MyISAM
FiAWTy_wc_admin_notes: Data: 0.14MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wc_admin_note_actions: Data: 0.08MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wc_customer_lookup: Data: 0.05MB + Index: 0.03MB + Engine InnoDB
FiAWTy_wc_download_log: Data: 0.06MB + Index: 0.03MB + Engine InnoDB
FiAWTy_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB
FiAWTy_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
FiAWTy_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_wc_order_product_lookup: Data: 0.06MB + Index: 0.11MB + Engine InnoDB
FiAWTy_wc_order_stats: Data: 0.06MB + Index: 0.05MB + Engine InnoDB
FiAWTy_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wc_product_meta_lookup: Data: 0.19MB + Index: 0.39MB + Engine InnoDB
FiAWTy_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wfauditevents: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfblockediplog: Data: 0.13MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfblocks7: Data: 0.25MB + Index: 0.20MB + Engine InnoDB
FiAWTy_wfconfig: Data: 1.52MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfcrawlers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wffilechanges: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wffilemods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfhits: Data: 1.52MB + Index: 0.17MB + Engine InnoDB
FiAWTy_wfhoover: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wfissues: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
FiAWTy_wfknownfilelist: Data: 5.52MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wflivetraffichuman: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wflocs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wflogins: Data: 0.52MB + Index: 0.16MB + Engine InnoDB
FiAWTy_wfls_2fa_secrets: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_wfls_role_counts: Data: 0.00MB + Index: 0.00MB + Engine MEMORY
FiAWTy_wfls_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfnotifications: Data: 0.05MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfpendingissues: Data: 0.02MB + Index: 0.06MB + Engine InnoDB
FiAWTy_wfreversecache: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfsecurityevents: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfsnipcache: Data: 0.16MB + Index: 0.17MB + Engine InnoDB
FiAWTy_wfstatus: Data: 0.25MB + Index: 0.13MB + Engine InnoDB
FiAWTy_wftrafficrates: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wfwaffailures: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_wpmem_plugin_history: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_xyz_ips_short_code: Data: 0.02MB + Index: 0.00MB + Engine InnoDB
FiAWTy_yoast_indexable: Data: 1.52MB + Index: 0.69MB + Engine InnoDB
FiAWTy_yoast_indexable_hierarchy: Data: 0.11MB + Index: 0.16MB + Engine InnoDB
FiAWTy_yoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB
FiAWTy_yoast_primary_term: Data: 0.02MB + Index: 0.03MB + Engine InnoDB
FiAWTy_yoast_seo_links: Data: 0.30MB + Index: 0.16MB + Engine InnoDB Post Type Counts

attachment: 2184
boxes: 3
catablog-items: 484
custom_css: 4
customize_changeset: 3
dlm_download_version: 1
download: 13
edd_log: 15
edd_payment: 8
et_footer_layout: 1
et_pb_layout: 27
et_pb_layout_stashed: 9
follow_up_email: 1
grid_products: 1
layout: 2
ms_song: 2
nav_menu_item: 46
oembed_cache: 4
options: 1
page: 54
post: 217
product: 1643
revision: 5
rpt_pricing_table: 1
shop_coupon: 6
shop_order: 298
shop_order_refund: 5
wp_font_face: 36
wp_font_family: 12
wp_global_styles: 2
wp_navigation: 1 Security

Secure connection (HTTPS): ✔
Hide errors from visitors: ✔ Active Plugins (20)

Responsive Pricing Table: by WP Darko – 5.1.12
FluentSMTP: by FluentSMTP & WPManageNinja Team – 2.2.92
Insert PHP Code Snippet: by xyzscripts.com – 1.4.4
Loco Translate: by Tim Whitlock – 2.8.0
Nav Menu Roles: by Kathy Darling – 2.1.2
Newsletter - Addons Manager and Support: by The Newsletter Team – 1.3.9
Newsletter - WP Users Addon: by The Newsletter Team – 1.4.6
Newsletter: by Stefano Lissa & The Newsletter Team – 9.0.7
Redis Object Cache: by Till Krüss – 2.7.0
s2Member Pro: by WP Sharks – 251005
s2member Secure File Browser: by Potsky – 0.4.19
s2Member Framework: by WP Sharks – 251005
Scriptless Social Sharing: by Robin Cornett – 3.3.1
UpdraftPlus - Backup/Restore: by TeamUpdraft
DavidAnderson – 1.25.8

WooCommerce.com Update Manager: by Automattic – 1.0.3
WooCommerce Stripe Gateway: by Stripe – 10.0.1
WooCommerce PayPal Payments: by PayPal – 3.3.0
WooCommerce: by Automattic – 10.3.4
Yoast SEO: by Team Yoast – 26.3
Asset CleanUp: Page Speed Booster: by Gabe Livan – 1.4.0.3 Inactive Plugins (7)

AAA Option Optimizer: by Joost de Valk – 1.5.1
Classic Widgets: by WordPress Contributors – 0.3
Elegant Themes Updater: by Elegant Themes – 1.2
Flying Scripts: by WP Speed Matters – 1.2.4
Smush: by WPMU DEV – 3.22.1
WooCommerce Legacy REST API: by WooCommerce – 1.0.5
WP Super Cache: by Automattic – 3.0.2 Dropin Plugins ()

object-cache.php: Redis Object Cache Drop-In Settings

Legacy 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)
variable (variable)

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: WC_Order_Data_Store_CPT
HPOS data sync enabled: –
Enabled Features: analytics
marketplace
order_attribution
site_visibility_badge
remote_logging
email_improvements
blueprint
point_of_sale Logging

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

Shop base: #1551 - /catalog/
Cart: #928 - /cart/ - Contains the [woocommerce_cart] shortcode
Checkout: ❌ Page does not contain the [woocommerce_checkout] shortcode or the woocommerce/checkout block.
My account: #930 - /my-cybermidi/ - Contains the [woocommerce_my_account] shortcode
Terms and conditions: #106 - /terms-of-service/ Theme

Name: Cybermidi
Version: 1.0
Author URL: https://divicake.com/
Child Theme: ✔
Parent Theme Name: Divi
Parent Theme Version: 4.27.4
Parent Theme Author URL: http://www.elegantthemes.com
Theme type: Classic theme
WooCommerce Support: ✔ Templates

Overrides: – WooCommerce Stripe Payment Gateway

Version: 10.0.1
Account ID:
Account Email: Unknown
Test Mode Enabled: ✔
No
OAuth Connected: No
Sync Enabled: No
Legacy Checkout Experience: ✔
No
Optimized Checkout Enabled: ✔
Yes
Enabled Payment Methods: card
Express Checkout: ✔
Enabled (product,cart,checkout)
Auth and Capture: ✔
Yes
Logging: No WooCommerce PayPal Payments

Onboarded: ✔
Branded only: –
New UI active: –
Shop country code: US
WooCommerce currency supported: ✔
Advanced Card Processing available in country: ✔
Pay Later messaging available in country: ✔
Webhook status: –
PayPal Vault enabled: –
ACDC Vault enabled: –
Logging enabled: –
Reference Transactions: –
Used PayPal Checkout plugin: –
Subscriptions Mode: Disabled
PayPal Shipping Callback: ✔
Apple Pay: –
Google Pay: –
Fastlane: – 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
onboarding
onboarding-tasks
pattern-toolkit-full-composability
product-custom-fields
remote-inbox-notifications
remote-free-extensions
payment-gateway-suggestions
printful
shipping-label-banner
subscriptions
store-alerts
transient-notices
woo-mobile-welcome
wc-pay-promotion
wc-pay-welcome-page
launch-your-store

Disabled Features: product-data-views
experimental-blocks
experimental-iapi-mini-cart
experimental-iapi-runtime
coming-soon-newsletter-template
minified-js
product-pre-publish-modal
settings
async-product-editor-category-field
product-editor-template-system
use-wp-horizon
rest-api-v4

Daily Cron: ❌ Not scheduled
Options: ✔
Notes: 264
Onboarding: completed Action Scheduler

Canceled: 1
Oldest: 2025-11-05 04:03:43 +0000
Newest: 2025-11-05 04:03:43 +0000

Complete: 900
Oldest: 2025-10-10 00:52:01 +0000
Newest: 2025-11-05 13:34:05 +0000

Failed: 58
Oldest: 2025-07-05 21:08:20 +0000
Newest: 2025-11-04 13:47:04 +0000

Pending: 12
Oldest: 2025-11-05 14:29:21 +0000
Newest: 2025-11-20 03:33:41 +0000 Status report information

Generated at: 2025-11-05 08:52:01 -05:00
``` * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18708017) * Can you read that Frank? * Notes: * There WAS a problem with CURL but it is now showing as webhost rolled me back to php 8.3 while they fix the server problem * It shows checkout shortcode missing but i am using DIVI shortcodes. The checkout page IS showing * Not sure what it says about daily cron as I run cron jobs outside of wordpress. 1. error logs 2. [05-Nov-2025 13:59:36 UTC] PHP Warning: include(/mnt/plesk_vhosts/vhosts/xxx. com/httpdocs/wp-content/languages/plugins/woocommerce-gateway-stripe-pt_BR.l10n. php): Failed to open stream: No such file or directory in /mnt/plesk_vhosts/ vhosts/x.com/httpdocs/wp-includes/l10n.php on line 1608 3. [05-Nov-2025 13:59:36 UTC] PHP Warning: include(): Failed opening ‘/mnt/plesk_vhosts/ vhosts/xxxx.com/httpdocs/wp-content/languages/plugins/woocommerce-gateway-stripe- pt_BR.l10n.php’ for inclusion (include_path=’.:/opt/plesk/php/8.0/share/pear’) in /mnt/plesk_vhosts/vhosts/xxxx.com/httpdocs/wp-includes/l10n.php on line 1608 * - This reply was modified 7 months ago by [pwizard](https://wordpress.org/support/users/pwizard/). * Plugin Support [shahzeen(woo-hc)](https://wordpress.org/support/users/shahzeenfarooq/) * (@shahzeenfarooq) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18708419) * Hi there Thanks for the update, and I’m glad to hear the cURL issue is now resolved after the PHP version rollback. * Regarding the “Checkout shortcode missing” notice — since you’re using Divi’s custom checkout module instead of the default WooCommerce checkout shortcode, that message can usually be ignored. * > About the log warnings related to the Stripe translation file: PHP Warning: > include(…woocommerce-gateway-stripe-pt_BR.l10n.php): Failed to open stream * This generally happens when WooCommerce or the Stripe plugin is trying to load a translation file that doesn’t exist. It’s not a critical error, but you can try the following: 1. Go to **Dashboard → Updates** and click **“Update Translations”** to refresh language files. 2. If you’re not using the Portuguese (pt_BR) language, you can safely ignore the warning. 3. Make sure you’re using the latest version of the WooCommerce Stripe plugin. * However, I checked the System Status report and I can see that the Stripe plugin is not configured yet. Since you mentioned that the Stripe plugin stopped working after the migration, could you please delete the current Stripe plugin completely and reinstall the latest version from here: [https://wordpress.org/plugins/woocommerce-gateway-stripe/](https://wordpress.org/plugins/woocommerce-gateway-stripe/) * After reinstalling, check if the issue still occurs. * I would also suggest creating a staging site, then deactivate all plugins except WooCommerce, and reinstall the Stripe gateway there first. If it works correctly on the staging site, you can safely apply the fix on the live site. * You can use the following plugin to create a staging site: [https://wordpress.org/plugins/wp-staging/](https://wordpress.org/plugins/wp-staging/) * Let us know what you find. * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18708526) * I can’t configure the settings, I getting error retrieving data (or something like that) * I created the stage but no difference. * Still waiting for host to respond. Can it be a database issue? * Plugin Support [Frank Remmy (woo-hc)](https://wordpress.org/support/users/frankremmy/) * (@frankremmy) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18708677) * Hi [@pwizard](https://wordpress.org/support/users/pwizard/), * Thank you for the update and for trying the staging site to isolate the issue. The “error retrieving data” message often points to communication issues between your site and Stripe’s servers, which can be related to server environment settings or transient data problems rather than directly a database issue. * Since you are still waiting on your host, here are a few steps you can take in the meantime to help narrow down the cause: - Ensure that necessary PHP extensions such as cURL, OpenSSL, and JSON are enabled and functioning correctly, as Stripe requires these for API communication. We’re good with that. - Sometimes, firewall rules or security modules on the server block outbound API requests. Confirm with your host that your server can make outbound HTTPS requests to Stripe endpoints. - Double-check file and folder permissions on your server, especially for plugin directories and language files. - Check WooCommerce → Status → Logs and filter for Stripe-related entries around the time you attempt to save settings. Any error messages there can be very helpful. - Though less common, ensure your database is not corrupted. You can check and repair tables via tools like phpMyAdmin or command line with: * ```wp-block-code CHECK TABLE wp_options; REPAIR TABLE wp_options; ``` * (Replace `wp_` with your actual database prefix.) - If you haven’t already, completely delete the Stripe plugin and install a fresh copy to rule out plugin file corruption. * Since your staging site shows the same behavior, it’s less likely caused by conflicting plugins or themes, which is useful info. When your host responds, sharing these points with them might expedite troubleshooting API connectivity. * Looking forward to your update! * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18709780) * This is my host response. Sounds like a plugin issue, not us * Thank you for your patience.  * We have thoroughly investigated this issue, and the problem appears to stem from the new versions of the WooCommerce Stripe plugin. Other users have reported similar problems on the WooCommerce Stripe support forum, although this is the first time we have encountered it directly. * We can also confirm that the site itself is able to connect to Stripe using cURL. We verified this using a custom script at [stripe-connect-check.php](https://cybermidi.com/stripe-connect-check.php). * **Stripe WooCommerce Migration issue:**The main cause seems to be that the WooCommerce plugin does not properly remove legacy entries from the database. While we could attempt to manually clear these, that approach is risky and not guaranteed to work – the plugin itself should be handling this cleanup.We have attached the WooCommerce plugin logs showing that the migration to their new system is failing. While it might be possible to work around this by connecting manually, that option has been disabled in the latest version of the plugin. * [Moses M. (woo-hc)](https://wordpress.org/support/users/mosesmedh/) * (@mosesmedh) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18710857) * Hi [@pwizard](https://wordpress.org/support/users/pwizard/), * Thank you for getting back to us and sharing your host’s response. * To move forward with resolving this, please try rolling back your Stripe plugin to a previous version. You can easily do this using a plugin such as [WP Rollback](https://wordpress.org/plugins/wp-rollback/). * If that doesn’t resolve the issue, deactivate and delete the Stripe for WooCommerce plugin. Then, visit the [WooCommerce Stripe Gateway page](https://wordpress.org/plugins/woocommerce-gateway-stripe/), scroll to the right side and click **Advanced View**, then scroll down to **Previous Versions**. Download an earlier version, upload it via FTP to the **wp-content/ plugins** folder, extract it, activate it from your dashboard, reconnect Stripe, and let us know if the issue persists. * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18711373) * Thanks for tyring to help. Nothing worked. I have moved on to another plugin * Thanks anyway * [LovingBro (woo-hc)](https://wordpress.org/support/users/lovingbro/) * (@lovingbro) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18711400) * Hi [@pwizard](https://wordpress.org/support/users/pwizard/), * We appreciate your update, and it’s sad to hear that you’ve decided to move on to another plugin after all the troubleshooting efforts. * If you ever decide to use the WooCommerce Stripe Payment Gateway again, we’ll be here to help guide you through getting it up and running smoothly on your site. * Wishing you the best with your current setup, and don’t hesitate to reach out if you’d like to revisit Stripe in the future. * Thread Starter [pwizard](https://wordpress.org/support/users/pwizard/) * (@pwizard) * [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/#post-18711756) * I appreciate your efforts, however being down for a days I was losing sales so had to make a decision * Thanks Viewing 15 replies - 1 through 15 (of 16 total) 1 [2](https://wordpress.org/support/topic/plugin-broke-after-migration/page/2/?output_format=md) [→](https://wordpress.org/support/topic/plugin-broke-after-migration/page/2/?output_format=md) The topic ‘Plugin broke after migration’ is closed to new replies. * ![](https://ps.w.org/woocommerce-gateway-stripe/assets/icon-256x256.png?rev=3177277) * [WooCommerce Stripe Payment Gateway](https://wordpress.org/plugins/woocommerce-gateway-stripe/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-gateway-stripe/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce-gateway-stripe/reviews/) * 16 replies * 5 participants * Last reply from: [LovingBro (woo-hc)](https://wordpress.org/support/users/lovingbro/) * Last activity: [7 months ago](https://wordpress.org/support/topic/plugin-broke-after-migration/page/2/#post-18711794) * Status: resolved