Site Modes in JCP – Live, Development and Debugging
The JCP provides three distinct Site Modes – Live, Development, and Debugging to help you manage your website effectively depending on its lifecycle stage. Each mode adjusts caching, search engine visibility, and diagnostic tools to suit your needs.
Live Mode
- Purpose: Default mode for production websites.
- Features:
- Enables all caching mechanisms (Full Page Cache, PHP Op Cache, Browser Caching, GZIP compression).
- Optimizes site performance for end users.
- Makes the site discoverable by search engines like Google and Bing.
- Use Case: Recommended when your site is complete and ready for public access.
Development Mode
- Purpose: Ideal for building and editing websites.
- Features:
- Disables all forms of caching to provide an up-to-date view of changes.
- Blocks search engine crawling to prevent incomplete or draft content from being indexed.
- Use Case: Use during design, content creation, or code changes to ensure accurate previews without caching interference.
Debugging Mode
- Purpose: Designed for troubleshooting and performance analysis.
- Features:
- Enables WordPress debug mode (if applicable).
- Displays PHP errors and notices on the frontend for easier issue identification.
- Disables caching and compression (Full Page Cache, PHP Op Cache, Browser Caching, GZIP).
- Activates the PHP Slow Request log for performance monitoring.
- Provides access to logs (access, error, debug logs) within JCP.
- Use Case: Use temporarily when diagnosing issues. Not recommended for long-term use due to performance impact.

How to Switch Modes
- Log in to your JCP.
- Navigate to the Site Management page.
- Locate the Mode dropdown box in the Overview section.
- Select Live or Development or Debugging depending on your use case.
- Confirm your choice by clicking the tickbox next to the dropdown.

Best Practices
- Keep your site in Live Mode when serving real users.
- Use Development Mode during active site changes to avoid caching conflicts.
- Enable Debugging Mode only when troubleshooting, and disable it once issues are resolved to restore performance.