WP Ghost and Hummingbird Cache Plugin Setup

WP Ghost is fully compatible with Hummingbird by WPMU DEV. When you use both plugins together, you need to do two things to keep WP Ghost’s path security working: change Hummingbird’s default cache directory away from the predictable /wp-content/cache/hummingbird/ location, and enable WP Ghost’s Change Paths in Cache Files option so the cached HTML, CSS, and JS files reference your custom paths instead of the WordPress defaults. This guide walks through the complete configuration in 4 steps.

Why Hummingbird Needs WP Ghost Configuration

Step 1: Enable Hummingbird Caching

If you haven’t already enabled Hummingbird’s caching:

1. Go to Hummingbird > Caching.
2. Activate Page Caching if it’s not already enabled.
3. Configure your caching preferences (page types to cache, cache lifespan, etc.).
4. Save the settings.

Hummingbird will start saving cached versions of your pages. By default, these are stored in /wp-content/cache/hummingbird/.

Step 2: Enable Asset Minification

Hummingbird’s Asset Optimization minifies and combines CSS and JS files for faster page loads. This creates additional cached files that WP Ghost also needs to know about.

1. Go to Hummingbird > Asset Optimization.
2. Enable Minification in the Basic Options section.
3. Configure which files to minify and combine (use the recommended settings or customize per your needs).
4. Save the settings.

Hummingbird now generates minified and combined CSS/JS files in addition to cached HTML pages. Both need WP Ghost’s path coordination.

Step 3: Change the Hummingbird Cache Directory

This is the most important step for security. The default Hummingbird cache directory /wp-content/cache/hummingbird/ is predictable and can reveal that you’re using Hummingbird (and WordPress) to anyone who probes that path. Change it to a non-obvious directory.

1. Go to Hummingbird > Asset Optimization > Settings.
2. Find the File Location or custom cache directory option.
3. Change the path from /wp-content/cache/hummingbird/ to something non-obvious like /wp-content/cache/optimization/ or /wp-content/cache/assets/.
4. Save the settings.

Tip: Pick a directory name that doesn’t reference Hummingbird, WPMU DEV, or any cache-related terminology. /wp-content/cache/static/, /wp-content/cache/build/, or /wp-content/cache/dist/ all work well. The goal is to make the directory look like a generic asset folder rather than a fingerprintable cache plugin location.

Step 4: Enable Change Paths in Cache Files in WP Ghost

Now tell WP Ghost to rewrite the paths inside Hummingbird’s cached files. Without this step, your cached HTML still references the original WordPress paths even though WP Ghost has changed them on the live site.

1. Go to WP Ghost > Advanced > Tweaks.
2. Find Change Paths in Cache Files.
3. Toggle it ON.
4. Click Save.

For complete configuration details, see Change Paths in Cached Files.

Important: After enabling this option, clear the Hummingbird cache so the next page generation creates fresh cached files with the updated paths. Go to Hummingbird > Caching > Clear Cache and also clear the Asset Optimization cache. Without clearing, your old cached files will continue serving the original paths until they expire.

Verify the Setup

1. Visit your site in an incognito/private browser window so you get a freshly cached version.
2. Right-click and select View Page Source.
3. Search for wp-content/plugins and wp-content/themes in the source. They should NOT appear – you should see your custom WP Ghost paths instead.
4. Search for hummingbird in the source. It should NOT appear if you renamed the cache directory in Step 3.
5. Run a Security Check in WP Ghost to confirm all settings are applied.

Troubleshooting

Cached pages still show wp-content/plugins paths

The Hummingbird cache hasn’t been cleared since enabling Change Paths in Cache Files in WP Ghost. Go to Hummingbird > Caching > Clear Cache, then also clear the Asset Optimization cache. Visit a few pages while logged out to regenerate the cache with the updated paths.

Site looks broken after enabling minification

This isn’t a WP Ghost issue – it’s a common Hummingbird minification problem when JS/CSS files have dependencies that get combined out of order. In Hummingbird Asset Optimization, exclude the problematic files from minification or use the “Don’t combine” option for files that break when combined. Test which files cause the issue by enabling them one at a time.

Custom cache directory keeps reverting to /hummingbird/

Make sure the new cache directory is writable by the web server. Hummingbird falls back to the default location if it can’t write to your custom path. Check folder permissions: the directory should be owned by your web server user (usually www-data on Ubuntu/Debian or nginx on CentOS) with permissions 755.

Locked out after configuration

Use the Safe URL parameter to bypass WP Ghost temporarily. If that doesn’t work, see the Emergency Disable guide to recover access via FTP.

Frequently Asked Questions

Which plugin should I install first – WP Ghost or Hummingbird?

Either order works, but the recommended sequence is: install Hummingbird first, configure caching and minification, then install WP Ghost and enable Change Paths in Cache Files. This ensures Hummingbird’s settings are stable before WP Ghost starts processing cached files.

Do I need to clear Hummingbird cache every time I save WP Ghost settings?

Yes, whenever you change paths in WP Ghost. Cached files contain the old paths until regenerated. Clear the Hummingbird cache after any WP Ghost path change to ensure visitors see the updated paths immediately.

What if I use a CDN with Hummingbird?

If you use Hummingbird with a CDN (Cloudflare, BunnyCDN, KeyCDN), you also need to purge the CDN cache after enabling WP Ghost path changes. The CDN serves cached versions of your files from edge servers, which won’t reflect the new paths until purged. Most CDNs have a “Purge Everything” or “Clear Cache” option in their dashboard.

Does this work with WooCommerce?

Yes. WP Ghost is fully compatible with WooCommerce and Hummingbird works with WooCommerce too. Make sure Hummingbird excludes cart, checkout, and account pages from caching (this is the default and recommended for any WooCommerce site).

Does WP Ghost modify Hummingbird files?

No. WP Ghost doesn’t modify Hummingbird’s plugin files or any WordPress core files. The Change Paths in Cache Files option processes the output before Hummingbird saves it to disk, ensuring the cached files contain the correct paths from the start.

Related Tutorials

WP Ghost with cache and performance plugins:

• Change Paths in Cached Files – Detailed configuration of the WP Ghost cache rewrite feature.
• Compatible Plugins List – All cache and performance plugins tested with WP Ghost.
• Run a Security Check – Verify your full WP Ghost configuration.
• Safe URL Recovery – Bypass WP Ghost temporarily if you get locked out.
• Emergency Disable – Recovery via FTP if needed.