Caching stores reusable responses or files so a site can load with less repeated work. Your site may use browser caching, a WordPress cache plugin, host-level caching, or a content delivery network. Identify the active layers before changing them. The Control Center does not currently provide a cache-purge tool. Use the controls belonging to your...
A staging site is a separate copy of your website where you test updates and design changes. It needs separate files and a separate database so testing cannot alter live content. The available cloning tools and site allowance depend on your hosting plan. The Control Center's WordPress tab is an inventory, without cloning controls. Review...
Install WordPress into an empty website directory or a planned subdirectory. If the domain already hosts a site, back up its files and database and confirm the replacement plan before running an installer. In the Control Center, open Hosting services → Manage website → WordPress to review tracked applications. This page lists installations; it does...
Plan updates as routine site maintenance. Keep a record of the versions you changed and test the site's important functions after each maintenance session. Hosting service does not, by itself, establish who manages application updates; check the scope of your plan. The Control Center's WordPress tab shows applications tracked by Virtualmin. Use WordPress administration or...
Start with maintained software, individual accounts, and recoverable backups. Security plugins can provide useful controls, but you still need to review who can sign in and what software runs on your site. Use WordPress administration to manage WordPress users. The Control Center's Hosting login controls the shared hosting owner, while its WordPress tab only lists...
