A broken product page, a failed plugin update, or an accidental deletion can cost a cannabis business sales and credibility fast. Knowing how to restore WordPress backups gives you a practical way to recover without rebuilding your site from scratch. The key is restoring the right backup, in the right order, while protecting any changes made since that backup was created.
For dispensary-adjacent brands, CBD stores, seed vendors, medical marijuana organizations, and mushroom businesses, your website often handles more than marketing. It may hold product information, customer inquiries, order records, compliance messaging, and the content that brings organic visitors to your business. Treat a restoration as a controlled recovery process, not a button to press when you are frustrated.
Before You Restore a WordPress Backup
Start by identifying the problem. If one page looks wrong after an edit, restoring an entire website may be excessive. You may be able to recover the page revision, disable a recently added plugin, or replace one damaged file instead. A full restore is usually appropriate after a major site failure, malware cleanup, a failed update that affects multiple areas, or an accidental overwrite of critical files and database content.
Next, check the date and contents of your available backups. A typical WordPress backup has two essential parts: website files and a database. The files include WordPress core files, themes, plugins, images, and uploads. The database contains posts, pages, settings, users, comments, WooCommerce products, and much of the information that makes the site function.
Restoring only one part can create problems. For example, restoring old files with a newer database may cause plugin or theme mismatches. Restoring an older database may remove recent orders, form entries, inventory changes, or customer account updates. If you run WooCommerce, review the timing especially carefully. You may need to preserve recent order information before moving forward.
Create a fresh backup of the current site before you restore anything, even if the site is broken. That extra snapshot is your safety net if you realize the chosen backup is too old or you need to retrieve newer content later. Download a copy to your computer when possible, rather than relying on one backup location.
How to Restore WordPress Backups From cPanel
Many hosting accounts provide backup tools inside cPanel. The exact labels may vary, but you may see Backup, Backup Wizard, JetBackup, File Manager, phpMyAdmin, or a similar tool. If your host provides a managed restoration interface, use it when available. It is generally faster and less error-prone than manually replacing files and importing databases.
Restore with a hosting backup tool
Open the backup section in cPanel and locate the available restore points. Choose the date that existed before the issue began. If the system lets you restore files, databases, email, or your full account separately, select only what you need.
For a complete WordPress recovery, restore both the home directory files and the correct database. Some tools also offer an option to restore the database user or permissions. Use that option if it is available, particularly if the site displays database connection errors after restoration.
Wait for the restoration job to finish before testing the site. Do not start another restore, install plugins, or make changes while the job is running. Depending on site size and server activity, this can take several minutes or longer. Once complete, clear your browser cache and any WordPress caching plugin or server cache before judging the result.
Restore WordPress files manually
Manual recovery is useful when you have a downloaded ZIP backup and database export but no one-click restore tool. In cPanel, open File Manager and go to the folder where WordPress is installed. For many primary domains, this is public_html. Add-on domains and subdomains may use a different folder.
Before replacing files, rename the existing WordPress folder or move its contents into a temporary folder. This gives you a fallback copy. Upload your backup ZIP file, extract it, and make sure the restored files land in the correct document root. A common mistake is extracting a backup that creates an extra folder layer, such as public_html/backup/public_html. If that happens, WordPress may appear missing even though the files are present.
Confirm that the restored folder includes wp-admin, wp-content, wp-includes, and wp-config.php. Your wp-content folder deserves special attention because it contains themes, plugins, and uploads. If you only need to restore missing images or a custom theme, replacing the whole WordPress installation may not be necessary.
Restore the WordPress database manually
Open phpMyAdmin from cPanel and identify the database used by the site. You can find its name in wp-config.php, usually next to DB_NAME. Before importing an older database, export the current one as a backup.
Select the WordPress database in phpMyAdmin. If you are performing a full rollback, remove the existing tables or use the import option that replaces them, depending on how your backup was created. Then choose Import, select your SQL backup file, and run the import. Large databases may need to be compressed or imported through a hosting support process if server limits prevent an upload.
After import, check wp-config.php again. The database name, user, password, and host must match the active database credentials. If the site says “Error establishing a database connection,” check these settings first. Also confirm that the database user has full privileges assigned through cPanel’s MySQL Database tools.
Restore Through a WordPress Backup Plugin
If you created backups with a WordPress plugin, restore through that same plugin whenever possible. Plugins often package files and database data in a format designed for their own restore process. Uploading those files through File Manager or importing them directly into phpMyAdmin may not work.
Log in to WordPress if you still can, open the backup plugin, and select the desired restore point. Most plugins let you choose whether to restore files, plugins, themes, uploads, and the database. For a site-wide failure, restore all available components. For a small issue, select the smallest portion that solves the problem.
If you cannot access wp-admin, you may still be able to use the plugin’s recovery instructions, but this varies by plugin. At that point, cPanel tools and support may be the more dependable route. Keep in mind that restoring a plugin backup may overwrite the current admin account settings, so use the credentials that existed at the backup date if your newest login does not work.
Test the Restored Site Before You Move On
A site that loads on the homepage is not necessarily fully recovered. Test the parts of the website that matter to your operation. Check the WordPress admin area, contact forms, menus, product pages, images, checkout functions, payment integrations, and mobile display. If your site sends transactional emails, submit a test form and confirm delivery.
For ecommerce sites, review recent orders and inventory counts. A backup from yesterday may restore your store’s design while removing orders placed this morning. Depending on your setup, you may need to manually recreate those orders, adjust stock, or retrieve information from payment processor records. This is one reason frequent backups matter for stores with daily activity.
Also check permalinks if pages return 404 errors after restoration. In WordPress, go to Settings, then Permalinks, and save the settings again. This refreshes rewrite rules without changing your selected permalink structure. If styling is broken, clear all caches and verify that your active theme and plugins are present.
Common WordPress Restore Mistakes to Avoid
The most expensive mistake is restoring the first backup you find without checking its date. A backup from months ago may fix a technical issue but erase substantial work. Always compare the backup timestamp with the moment the problem started.
Another common issue is restoring files but not the database, or the database but not the related files. WordPress depends on both. Plugin versions, theme settings, product information, and media references can become inconsistent when they come from different points in time.
Do not assume backups are automatically usable just because they exist. Periodically verify that your backup system is running, that you can access restore points, and that it includes both files and databases. For a revenue-generating cannabis store, daily backups are a sensible baseline. More frequent backups may be worth it if you process many orders, publish frequent content, or make regular catalog changes.
If you are unsure which backup to use or the restoration affects customer data, ask for help before guessing. Weed Hosts customers can use responsive support to confirm the safest recovery path and avoid turning a manageable website problem into a larger outage.
A backup is only valuable when you can restore it calmly and correctly. Keep more than one recovery point, save a current copy before major updates, and give yourself enough time to test the site after every restore. That preparation protects the work you have put into building your online business.