Settings & Tools

Overview

This article covers global controls, maintenance tools, and WP-CLI commands for managing BoostPro from the command line.

Killswitch

The killswitch is a master toggle that disables all frontend optimizations instantly. It is available as a sidebar widget in the BoostPro admin for quick access.

When enabled:

• All frontend optimizations are disabled for all visitors
• Individual settings are preserved (not reset)
• Re-enabling the killswitch restores all previous optimizations

Use this when you need to quickly diagnose whether BoostPro is causing an issue without changing individual settings one at a time.

You can also disable BoostPro via wp-config.php by adding:

define('BOOST_DISABLE', true);

Note that the BOOST_DISABLE constant is separate from the admin killswitch toggle. Either method disables all optimizations.

Source code comment

The source_comment setting (enabled by default) adds an "Optimized by BoostPro" HTML comment at the end of your page source code. Toggle it off to remove the comment.

Per-page disable controls

You can disable specific BoostPro features on individual pages via the Resource Manager panel:

• Delay JavaScript
• Defer JavaScript
• Remove Unused CSS
• CSS Minification
• JS Minification
• Page Caching

These are stored as _boost_disable post meta. See the Resource Manager article for details.

Export settings

Downloads your current settings as a JSON file (boostpro-settings.json). This includes all optimization settings and can be used for backup or migrating your configuration to another site.

Import settings

Upload a previously exported JSON file to restore settings. BoostPro validates the file structure before applying and merges the imported settings without affecting non-settings data like converted images or cache files.

Reset to defaults

Restores all settings to factory defaults. This does not delete converted images, cache files, or deactivate your license.

WP-CLI commands

BoostPro includes WP-CLI commands for managing caches from the command line. These require WP-CLI to be installed and BoostPro to be activated.

Common use cases

• Deployment scripts: add wp boostpro purge after deploying code changes to ensure fresh caches
• Scheduled maintenance: use cron to schedule periodic cache clears if needed

Cache storage locations