After Changing the wp-content Path, Some Plugins Are Not Functioning Properly

If plugins break, display errors, or lose functionality after changing the wp-content path in WP Ghost, the plugins are loading assets from /wp-content/ and the server isn’t correctly rewriting the custom path back to the original directory.

Clear all caches

Cached pages still reference the old /wp-content/ path in script, stylesheet, and image URLs. Clear your WordPress cache plugin, CDN cache, and browser cache. Enable Change Paths in Cached Files at WP Ghost > Change Paths so cached CSS and JS files are rewritten with the new paths. Check in an incognito window.

Run the Frontend Test

Go to WP Ghost > Change Paths and click the Frontend Test button. If the test fails for the wp-content path, your server’s rewrite rules aren’t correctly mapping the custom path. Follow the configuration instructions shown for your server type (Apache, Nginx, LiteSpeed, etc.).

Check for typos in the custom path

Go to WP Ghost > Change Paths and review the custom wp-content path for typos, spaces, or special characters. The path should be a simple alphanumeric name like content or assets.

Revert to the default wp-content path

To confirm the custom path is causing the issue, go to WP Ghost > Change Paths and set the wp-content path back to wp-content. Save and test. If plugins work again with the default path, the issue is server rewrite rules not handling the custom path.

Identify the conflicting plugin

If the Frontend Test passes but a specific plugin still breaks, that plugin may hardcode references to /wp-content/ instead of using WordPress constants like WP_CONTENT_URL. Deactivate plugins one at a time and test after each. Common conflicts include plugins that enqueue assets with hardcoded paths, plugins that write to wp-content subdirectories directly (like backup or cache plugins), and plugins that reference /wp-content/plugins/plugin-name/ in inline JavaScript. For the conflicting plugin, try adding its specific paths to WP Ghost > Change Paths > Whitelist Paths.

If you’ve lost access to the admin dashboard, see the emergency disable guide.