Plugin Support
Kush
(@kushnamdev)
Hey @scotto1121,
Could you please check your error log and share it with us?
Best regards
Fatal error: Uncaught Stripe\Exception\InvalidArgumentException: api_key cannot contain whitespace in /var/www/wptbox/wp-content/plugins/otter-blocks/vendor/stripe/stripe-php/lib/BaseStripeClient.php:276 Stack trace: #0 /var/www/wptbox/wp-content/plugins/otter-blocks/vendor/stripe/stripe-php/lib/BaseStripeClient.php(73): Stripe\BaseStripeClient->validateConfig() #1 /var/www/wptbox/wp-content/plugins/otter-blocks/inc/plugins/class-stripe-api.php(49): Stripe\BaseStripeClient->__construct() #2 /var/www/wptbox/wp-content/plugins/otter-blocks/inc/class-main.php(95): ThemeIsle\GutenbergBlocks\Plugins\Stripe_API->__construct() #3 /var/www/wptbox/wp-includes/class-wp-hook.php(341): ThemeIsle\GutenbergBlocks\Main->autoload_classes() #4 /var/www/wptbox/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters() #5 /var/www/wptbox/wp-includes/plugin.php(522): WP_Hook->do_action() #6 /var/www/wptbox/wp-settings.php(742): do_action() #7 /var/www/wptbox/wp-config.php(115): require_once(‘…’) #8 /var/www/wptbox/wp-load.php(50): require_once(‘…’) #9 /var/www/wptbox/wp-admin/admin.php(35): require_once(‘…’) #10 /var/www/wptbox/wp-admin/plugins.php(10): require_once(‘…’) #11 {main} thrown in /var/www/wptbox/wp-content/plugins/otter-blocks/vendor/stripe/stripe-php/lib/BaseStripeClient.php on line 276
Hi there,
Thank you for providing that error log! It helps immensely.
The error api_key cannot contain whitespace indicates that when the Stripe API key was saved, an extra space was likely included (either at the beginning or the end). Because the plugin tries to validate this key as soon as it loads, it is triggering the “Critical Error” before you can access the settings page to fix it.
To get your site back up and running safely, please follow these steps:
1. Deactivate the plugin via FTP
- Log in to your site files using FTP or your hosting File Manager.
- Navigate to
/wp-content/plugins/.
- Find the folder named
otter-blocks and rename it to otter-blocks-temp.
- This will force WordPress to deactivate the plugin, and your dashboard should load again immediately.
2. Clear the incorrect API key
Even with the plugin deactivated, the “bad” key is still saved in your database. To ensure the site doesn’t crash again when you reactivate the plugin, I recommend the following:
- Contact your hosting support: Share the error log you provided here and ask them to remove the Otter Blocks entries from your
wp_options table. This is the safest way to reset the plugin settings without risk to your site.
3. Reactivate and Re-enter
Once the database entry is cleared, you can rename the folder back to otter-blocks in FTP, reactivate the plugin in your dashboard, and carefully re-paste the API key (ensuring no extra spaces are included).
Hope this helps.
Make sure you also backup your site before, just in case.
