How to create and use staging environments in JetHost WordPress Manager

The Staging tab in JetHost WordPress Manager allows you to create a complete copy of your WordPress installation for testing changes safely before applying them to your live site. In particular, staging environments let you test plugins, themes, code changes, and updates without risking your production website. Furthermore, you can choose between creating staging sites on subdomains or new subdomains, giving you flexibility in how you organize your testing environments.

What is a staging environment?

A staging environment is an exact copy of your live WordPress site where you can safely experiment with changes. Moreover, it operates independently from your production site, meaning visitors to your main website won’t see any staging changes. This separation allows you to break things, test thoroughly, and perfect your changes before deploying them to your live site.

Accessing staging features

To access staging management, navigate to the Staging tab from the top navigation menu in WordPress Manager. Once there, you’ll see the staging creation interface showing your live installation URL and options for configuring your staging site.

Creating a staging environment

The staging creation form displays your live installation URL at the top, helping you confirm you’re creating a staging copy of the correct site. Below that, you’ll configure where your staging site will be located:

Choosing a domain for staging

The Choose Domain dropdown provides two options:

• New subdomain: Creates a completely new subdomain specifically for staging (e.g., “staging.yourdomain.com”). This option keeps your staging site clearly separated and easily identifiable.
• Existing domain: Uses one of your existing domains or subdomains for the staging site. Select this if you’ve already set up a subdomain you want to use for testing.

Setting the directory

The In Directory field specifies where staging files will be stored on your server. By default, this might be “staging” or similar. You can leave this empty to install in the root directory of your chosen domain, though using a subdirectory like “staging” keeps files organized. Additionally, the system suggests leaving it empty to install in the root directory if preferred.

Creating the staging site

After configuring your domain and directory, click the orange Create Staging Environment button. The system begins copying your live site to the staging location. Depending on your site size, this process may take several minutes. Consequently, larger sites with many files and database entries require more time to duplicate completely.

Working with your staging site

Once created, your staging site appears in the WordPress Manager site selector at the top of the interface. You can switch between production and staging using this dropdown, which displays the environment badge (Production or Staging) for quick identification.

Accessing staging features

After switching to your staging environment, you have access to all WordPress Manager features:

• Overview: View staging site details and clear cache
• Plugins & Themes: Install and test new WP plugins and WP themes
• Users: Manage test user accounts
• File Manager: Edit files via cPanel File Manager
• Backups: Create staging-specific backups
• Security: Test security configurations
• Advanced: Access advanced settings

Logging into staging WordPress admin

Your staging site copies your production site’s login credentials. Use the same username and password you use for production to access the staging WordPress admin panel. Click the WP Admin button from the overview tab to open the staging dashboard.

Pushing staging changes to your live site

When you’re satisfied with changes on your staging site, you can deploy them to production using the Push to Live feature. This tab shows a side‑by‑side comparison of your staging and live installations, including their domains and URLs, so you can confirm you’re pushing to the correct site.

Push options

Before pushing, configure the transfer settings:

• Overwrite files/folders: When enabled, files and folders on the live site are replaced with the versions from staging. Use this when you’ve changed themes, plugins, or other files on staging.
• Push full database: When enabled, the entire database is pushed from staging to live. If you disable this, you can choose specific tables for structural or data updates instead.

Before you push

You must back up your live site before pushing. Check the confirmation box that says “I confirm that I have backed up the live site before proceeding.” This helps avoid data loss if something goes wrong. After confirming, click the orange Push to Live button to start the transfer.

Common staging use cases

Staging environments serve multiple purposes for safe WordPress development and testing:

Testing plugin and theme updates

Before updating WP plugins or WP themes on your live site, install updates on staging first. This reveals compatibility issues or bugs before they affect real visitors. Moreover, you can thoroughly test functionality to ensure everything works as expected after updates.

Trying new WP plugins

Install and experiment with new plugins on staging to evaluate whether they meet your needs. This prevents cluttering your production site with test plugins. Additionally, you can assess performance impact and compatibility without affecting your live site’s speed or stability.

Testing WP theme changes

Customize themes or try entirely new themes on staging before committing to design changes. This allows your team to review changes and gather feedback before making them public. Similarly, you can test mobile responsiveness and cross-browser compatibility without rushing.

Developing custom code

Write and test custom PHP, CSS, or JavaScript code on staging before deploying it to production. Use File Manager to edit files safely, knowing mistakes won’t break your live site. Furthermore, staging provides a safe environment for learning and experimentation.

Testing WordPress core updates

Major WordPress version updates can sometimes cause compatibility issues. Test core updates on staging first to identify problems before applying them to production. Configure automatic updates differently for staging and production if desired.

Training and demonstrations

Use staging to train team members on WordPress without risking live content. Additionally, staging provides a safe environment for creating tutorials or demonstrating features to clients.

Best practices for staging environments

Following these recommendations ensures you get maximum value from staging:

Keep staging synchronized

Periodically recreate your staging site to keep it synchronized with production. Over time, staging diverges from your live site as you make production changes. Recreating staging ensures you’re testing against an accurate copy of your current live environment.

Don’t use staging for live content

Never direct real visitors to your staging site or use it for actual business operations. Staging sites lack the stability, performance optimization, and security hardening of production environments. Moreover, changes made on staging can be lost when you recreate the staging environment.

Back up before major tests

Create staging backups before conducting destructive tests. This lets you quickly reset staging to a known state if tests go wrong. Additionally, backups document your testing progress at different stages.

Block search engines from staging

Ensure search engines don’t index your staging site, which would create duplicate content issues. Use the Advanced section to disable search engine visibility on staging. Similarly, consider password-protecting staging to prevent accidental public access.

Test thoroughly before deploying

Don’t rush from staging to production. Test all critical functionality, including:

• Contact forms and lead generation
• E-commerce checkout and payments
• User registration and login
• Custom features and integrations
• Mobile responsiveness
• Page loading speed

Deploying changes from staging to production

After testing changes successfully on staging, you need to apply them to your live site. This process depends on what you changed:

For plugin and theme updates

Create a production backup, then apply the same updates to your live site through the Plugins & Themes section. Verify functionality immediately after updating.

For code changes

Download modified files from staging using File Manager, then upload them to production. Always back up the original production files before replacing them. Alternatively, manually recreate code changes on production after validating them on staging.

For configuration changes

Document configuration changes made on staging, then manually apply the same settings to production. This includes security settings, plugin configurations, and WordPress options.

Managing multiple staging sites

You can create multiple staging environments if needed. For instance, one staging site might test long-term development while another tests immediate updates. Use descriptive subdomain names (like “dev.yourdomain.com” and “staging.yourdomain.com”) to keep them organized.

Troubleshooting staging issues

Staging creation fails

If staging creation fails, verify you have sufficient disk space for a complete site copy. Additionally, very large sites may time out – contact JetHost support for assistance with creating staging for especially large installations.

Staging site looks broken

If staging displays incorrectly, clear the staging cache using the overview tab. Some themes and plugins cache URLs, which may need regenerating after creating staging. Similarly, check that staging URLs are properly configured in WordPress settings.

Cannot log into staging

Staging copies your production credentials at creation time. If you changed your production password after creating staging, use the old password for staging. Alternatively, use File Manager or database tools to reset the staging admin password.

Need more help?

Explore more WordPress Manager guides and hosting tutorials in our knowledgebase. The WordPress Manager is included free with all hosting for WordPress plans at JetHost.

For additional support with staging environments or deployment workflows, our team is here to help you test changes safely.

—

SEO KEYPHRASE: WordPress Manager staging environment

META DESCRIPTION: Learn how to create and use staging environments in JetHost WordPress Manager. Test plugins, themes, updates, and code changes safely before deploying to your live WordPress site.