Plugin broke after migration

(@frankremmy)

Hello @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/ and send the link here.

Looking forward to your update so we can get Stripe Gateway back in working order!

Thread Starter

(@pwizard)

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

(@frankremmy)

Hi @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.

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 5 months, 1 week ago by Frank Remmy (woo-hc).

Thread Starter

(@pwizard)

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

(@frankremmy)

Hi @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)

WordPress Environment<br><br>WordPress address (URL): XXXXX<br>Site address (URL): https://xxxx.com<br>WC Version: 10.3.4<br>Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.<br>Action Scheduler Version: ✔ 3.9.3<br>Log Directory Writable: ✔<br>WP Version: 6.8.3<br>WP Multisite: –<br>WP Memory Limit: 2 GB<br>WP Debug Mode: ✔<br>WP Cron: –<br>Language: en_US<br>External object cache: ✔ Server Environment<br><br>Server Info: nginx/1.28.0<br>Server Architecture: Linux 4.15.0-135-generic x86_64<br>PHP Version: 8.3.27<br>PHP Post Max Size: 250 MB<br>PHP Time Limit: 120<br>PHP Max Input Vars: 1000<br>cURL Version: 7.58.0<br>OpenSSL/1.1.1<br><br>SUHOSIN Installed: –<br>MySQL Version: 10.11.5-MariaDB-1:10.11.5+maria~ubu1804<br>Max Upload Size: 200 MB<br>Default Timezone is UTC: ✔<br>fsockopen/cURL: ✔<br>SoapClient: ✔<br>DOMDocument: ✔<br>GZip: ✔<br>Multibyte String: ✔<br>Remote Post: ✔<br>Remote Get: ✔ Database<br><br>WC Database Version: 10.3.4<br>WC Database Prefix: FiAWTy_<br>Total Database Size: 44.28MB<br>Database Data Size: 34.56MB<br>Database Index Size: 9.72MB<br>FiAWTy_woocommerce_sessions: Data: 0.05MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_woocommerce_downloadable_product_permissions: Data: 0.08MB + Index: 0.13MB + Engine InnoDB<br>FiAWTy_woocommerce_order_items: Data: 0.05MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_woocommerce_order_itemmeta: Data: 0.23MB + Index: 0.20MB + Engine InnoDB<br>FiAWTy_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>FiAWTy_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>FiAWTy_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>FiAWTy_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>ahm_files: Data: 0.00MB + Index: 0.00MB + Engine MyISAM<br>FiAWTy_actionscheduler_actions: Data: 0.31MB + Index: 0.80MB + Engine InnoDB<br>FiAWTy_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_actionscheduler_logs: Data: 0.20MB + Index: 0.14MB + Engine InnoDB<br>FiAWTy_commentmeta: Data: 0.00MB + Index: 0.00MB + Engine MyISAM<br>FiAWTy_comments: Data: 0.15MB + Index: 0.07MB + Engine MyISAM<br>FiAWTy_fsmpt_email_logs: Data: 1.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_links: Data: 0.00MB + Index: 0.00MB + Engine MyISAM<br>FiAWTy_litespeed_url: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_litespeed_url_file: Data: 0.02MB + Index: 0.08MB + Engine InnoDB<br>FiAWTy_newsletter: Data: 0.41MB + Index: 0.13MB + Engine InnoDB<br>FiAWTy_newsletter_emails: Data: 0.23MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_newsletter_logs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_newsletter_sent: Data: 0.47MB + Index: 0.34MB + Engine InnoDB<br>FiAWTy_newsletter_stats: Data: 0.39MB + Index: 0.20MB + Engine InnoDB<br>FiAWTy_newsletter_user_logs: Data: 0.08MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_newsletter_user_meta: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_options: Data: 2.74MB + Index: 0.13MB + Engine MyISAM<br>FiAWTy_postmeta: Data: 4.20MB + Index: 1.72MB + Engine MyISAM<br>FiAWTy_posts: Data: 3.90MB + Index: 0.40MB + Engine MyISAM<br>FiAWTy_post_smtp_logmeta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_post_smtp_logs: Data: 1.52MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_psk_s2msfb_downloads: Data: 1.10MB + Index: 0.11MB + Engine MyISAM<br>FiAWTy_psk_s2msfb_files: Data: 0.22MB + Index: 0.11MB + Engine MyISAM<br>FiAWTy_smush_dir_images: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_taxonomymeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_terms: Data: 0.00MB + Index: 0.02MB + Engine MyISAM<br>FiAWTy_term_relationships: Data: 0.12MB + Index: 0.26MB + Engine MyISAM<br>FiAWTy_term_taxonomy: Data: 0.01MB + Index: 0.01MB + Engine MyISAM<br>FiAWTy_usermeta: Data: 3.43MB + Index: 1.16MB + Engine MyISAM<br>FiAWTy_users: Data: 0.12MB + Index: 0.09MB + Engine MyISAM<br>FiAWTy_wc_admin_notes: Data: 0.14MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wc_admin_note_actions: Data: 0.08MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wc_customer_lookup: Data: 0.05MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_wc_download_log: Data: 0.06MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>FiAWTy_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>FiAWTy_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_wc_order_product_lookup: Data: 0.06MB + Index: 0.11MB + Engine InnoDB<br>FiAWTy_wc_order_stats: Data: 0.06MB + Index: 0.05MB + Engine InnoDB<br>FiAWTy_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wc_product_meta_lookup: Data: 0.19MB + Index: 0.39MB + Engine InnoDB<br>FiAWTy_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wfauditevents: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfblockediplog: Data: 0.13MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfblocks7: Data: 0.25MB + Index: 0.20MB + Engine InnoDB<br>FiAWTy_wfconfig: Data: 1.52MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfcrawlers: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wffilechanges: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wffilemods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfhits: Data: 1.52MB + Index: 0.17MB + Engine InnoDB<br>FiAWTy_wfhoover: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wfissues: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>FiAWTy_wfknownfilelist: Data: 5.52MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wflivetraffichuman: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wflocs: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wflogins: Data: 0.52MB + Index: 0.16MB + Engine InnoDB<br>FiAWTy_wfls_2fa_secrets: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_wfls_role_counts: Data: 0.00MB + Index: 0.00MB + Engine MEMORY<br>FiAWTy_wfls_settings: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfnotifications: Data: 0.05MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfpendingissues: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>FiAWTy_wfreversecache: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfsecurityevents: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfsnipcache: Data: 0.16MB + Index: 0.17MB + Engine InnoDB<br>FiAWTy_wfstatus: Data: 0.25MB + Index: 0.13MB + Engine InnoDB<br>FiAWTy_wftrafficrates: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wfwaffailures: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_wpmem_plugin_history: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_xyz_ips_short_code: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>FiAWTy_yoast_indexable: Data: 1.52MB + Index: 0.69MB + Engine InnoDB<br>FiAWTy_yoast_indexable_hierarchy: Data: 0.11MB + Index: 0.16MB + Engine InnoDB<br>FiAWTy_yoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>FiAWTy_yoast_primary_term: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>FiAWTy_yoast_seo_links: Data: 0.30MB + Index: 0.16MB + Engine InnoDB Post Type Counts<br><br>attachment: 2184<br>boxes: 3<br>catablog-items: 484<br>custom_css: 4<br>customize_changeset: 3<br>dlm_download_version: 1<br>download: 13<br>edd_log: 15<br>edd_payment: 8<br>et_footer_layout: 1<br>et_pb_layout: 27<br>et_pb_layout_stashed: 9<br>follow_up_email: 1<br>grid_products: 1<br>layout: 2<br>ms_song: 2<br>nav_menu_item: 46<br>oembed_cache: 4<br>options: 1<br>page: 54<br>post: 217<br>product: 1643<br>revision: 5<br>rpt_pricing_table: 1<br>shop_coupon: 6<br>shop_order: 298<br>shop_order_refund: 5<br>wp_font_face: 36<br>wp_font_family: 12<br>wp_global_styles: 2<br>wp_navigation: 1 Security<br><br>Secure connection (HTTPS): ✔<br>Hide errors from visitors: ✔ Active Plugins (20)<br><br>Responsive Pricing Table: by WP Darko – 5.1.12<br>FluentSMTP: by FluentSMTP & WPManageNinja Team – 2.2.92<br>Insert PHP Code Snippet: by xyzscripts.com – 1.4.4<br>Loco Translate: by Tim Whitlock – 2.8.0<br>Nav Menu Roles: by Kathy Darling – 2.1.2<br>Newsletter - Addons Manager and Support: by The Newsletter Team – 1.3.9<br>Newsletter - WP Users Addon: by The Newsletter Team – 1.4.6<br>Newsletter: by Stefano Lissa & The Newsletter Team – 9.0.7<br>Redis Object Cache: by Till Krüss – 2.7.0<br>s2Member Pro: by WP Sharks – 251005<br>s2member Secure File Browser: by Potsky – 0.4.19<br>s2Member Framework: by WP Sharks – 251005<br>Scriptless Social Sharing: by Robin Cornett – 3.3.1<br>UpdraftPlus - Backup/Restore: by TeamUpdraft<br>DavidAnderson – 1.25.8<br><br>WooCommerce.com Update Manager: by Automattic – 1.0.3<br>WooCommerce Stripe Gateway: by Stripe – 10.0.1<br>WooCommerce PayPal Payments: by PayPal – 3.3.0<br>WooCommerce: by Automattic – 10.3.4<br>Yoast SEO: by Team Yoast – 26.3<br>Asset CleanUp: Page Speed Booster: by Gabe Livan – 1.4.0.3 Inactive Plugins (7)<br><br>AAA Option Optimizer: by Joost de Valk – 1.5.1<br>Classic Widgets: by WordPress Contributors – 0.3<br>Elegant Themes Updater: by Elegant Themes – 1.2<br>Flying Scripts: by WP Speed Matters – 1.2.4<br>Smush: by WPMU DEV – 3.22.1<br>WooCommerce Legacy REST API: by WooCommerce – 1.0.5<br>WP Super Cache: by Automattic – 3.0.2 Dropin Plugins ()<br><br>object-cache.php: Redis Object Cache Drop-In Settings<br><br>Legacy API Enabled: –<br>Force SSL: –<br>Currency: USD ($)<br>Currency Position: left<br>Thousand Separator: ,<br>Decimal Separator: .<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable)<br><br>Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5)<br><br>Connected to WooCommerce.com: ✔<br>Enforce Approved Product Download Directories: –<br>HPOS feature enabled: –<br>Order datastore: WC_Order_Data_Store_CPT<br>HPOS data sync enabled: –<br>Enabled Features: analytics<br>marketplace<br>order_attribution<br>site_visibility_badge<br>remote_logging<br>email_improvements<br>blueprint<br>point_of_sale Logging<br><br>Enabled: ✔<br>Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2<br>Retention period: 30 days<br>Level threshold: –<br>Log directory size: 593 KB WC Pages<br><br>Shop base: #1551 - /catalog/<br>Cart: #928 - /cart/ - Contains the &#091;woocommerce_cart] shortcode<br>Checkout: ❌ Page does not contain the &#091;woocommerce_checkout] shortcode or the woocommerce/checkout block.<br>My account: #930 - /my-cybermidi/ - Contains the &#091;woocommerce_my_account] shortcode<br>Terms and conditions: #106 - /terms-of-service/ Theme<br><br>Name: Cybermidi<br>Version: 1.0<br>Author URL: https://divicake.com/<br>Child Theme: ✔<br>Parent Theme Name: Divi<br>Parent Theme Version: 4.27.4<br>Parent Theme Author URL: http://www.elegantthemes.com<br>Theme type: Classic theme<br>WooCommerce Support: ✔ Templates<br><br>Overrides: – WooCommerce Stripe Payment Gateway<br><br>Version: 10.0.1<br>Account ID:<br>Account Email: Unknown<br>Test Mode Enabled: ✔<br>No<br>OAuth Connected: No<br>Sync Enabled: No<br>Legacy Checkout Experience: ✔<br>No<br>Optimized Checkout Enabled: ✔<br>Yes<br>Enabled Payment Methods: card<br>Express Checkout: ✔<br>Enabled (product,cart,checkout)<br>Auth and Capture: ✔<br>Yes<br>Logging: No WooCommerce PayPal Payments<br><br>Onboarded: ✔<br>Branded only: –<br>New UI active: –<br>Shop country code: US<br>WooCommerce currency supported: ✔<br>Advanced Card Processing available in country: ✔<br>Pay Later messaging available in country: ✔<br>Webhook status: –<br>PayPal Vault enabled: –<br>ACDC Vault enabled: –<br>Logging enabled: –<br>Reference Transactions: –<br>Used PayPal Checkout plugin: –<br>Subscriptions Mode: Disabled<br>PayPal Shipping Callback: ✔<br>Apple Pay: –<br>Google Pay: –<br>Fastlane: – Admin<br><br>Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customize-store<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>onboarding<br>onboarding-tasks<br>pattern-toolkit-full-composability<br>product-custom-fields<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>printful<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page<br>launch-your-store<br><br>Disabled Features: product-data-views<br>experimental-blocks<br>experimental-iapi-mini-cart<br>experimental-iapi-runtime<br>coming-soon-newsletter-template<br>minified-js<br>product-pre-publish-modal<br>settings<br>async-product-editor-category-field<br>product-editor-template-system<br>use-wp-horizon<br>rest-api-v4<br><br>Daily Cron: ❌ Not scheduled<br>Options: ✔<br>Notes: 264<br>Onboarding: completed Action Scheduler<br><br>Canceled: 1<br>Oldest: 2025-11-05 04:03:43 +0000<br>Newest: 2025-11-05 04:03:43 +0000<br><br>Complete: 900<br>Oldest: 2025-10-10 00:52:01 +0000<br>Newest: 2025-11-05 13:34:05 +0000<br><br>Failed: 58<br>Oldest: 2025-07-05 21:08:20 +0000<br>Newest: 2025-11-04 13:47:04 +0000<br><br>Pending: 12<br>Oldest: 2025-11-05 14:29:21 +0000<br>Newest: 2025-11-20 03:33:41 +0000 Status report information<br><br>Generated at: 2025-11-05 08:52:01 -05:00<br>

Thread Starter

(@pwizard)

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.

error logs
[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
[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 5 months, 1 week ago by pwizard.

Plugin Support

shahzeen(woo-hc)

(@shahzeenfarooq)

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:

Go to Dashboard → Updates and click “Update Translations” to refresh language files.
If you’re not using the Portuguese (pt_BR) language, you can safely ignore the warning.
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/

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/

Let us know what you find.

Thread Starter

(@pwizard)

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

(@frankremmy)

Hi @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:


  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)

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.

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)

(@mosesmedh)

Hi @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.

If that doesn’t resolve the issue, deactivate and delete the Stripe for WooCommerce plugin. Then, visit the WooCommerce Stripe Gateway page, 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)

Thanks for tyring to help. Nothing worked. I have moved on to another plugin

Thanks anyway

Plugin Support

LovingBro (woo-hc)

(@lovingbro)

Hi @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