Buzzy powers a lot of viral content and BuzzFeed-style sites, and like any active script it ships regular updates for security patches, bug fixes, and new features. The problem? A rushed update can wipe out custom settings, break a theme, or leave you staring at a white screen right when your traffic spikes. The fix is simple: always take a backup first, test carefully, and automate the boring parts so you never forget.

This guide walks you through updating Buzzy and its add-ons the safe way, taking a full snapshot before you touch anything, and setting up automated backups through both DirectAdmin and cPanel.

Before You Update: The Golden Rule

Never run an update on a live site without a fresh, restorable backup. Buzzy stores your posts, categories, user data, and settings in a MySQL database, while themes, uploads, and config live on the filesystem. You need both to roll back cleanly.

Pro Tip: Treat every update as if it will fail. If you plan for failure, a broken update becomes a 2-minute restore instead of a 2-hour panic.

Step 1: Check Your Current Buzzy Version

Log in to your Buzzy admin dashboard (usually yourdomain.com/admin). From the left menu:

  1. Go to SettingsSystem Info (or the dashboard footer, which shows the version number).
  2. Note your current version and compare it with the latest release from your Buzzy vendor account.
  3. Read the changelog. If the update touches the database schema, a backup is non-negotiable.

Step 2: Take a Full Snapshot (Files + Database)

A snapshot means grabbing everything: your Buzzy files and the database, in one go. Here's how to do it in each panel.

Backing Up Files in DirectAdmin

  1. Log in to DirectAdmin.
  2. Open File Manager under the System Info & Files section.
  3. Navigate to your Buzzy folder (often public_html or a subfolder).
  4. Select the folder, click Add to Archive, and create a .tar.gz or .zip.
  5. Download the archive to your computer for safekeeping.

Backing Up Files in cPanel

  1. Log in to cPanel.
  2. Open File Manager under the Files section.
  3. Go to your Buzzy directory.
  4. Select all files/folders, click Compress, choose Gzipped Tar Archive, and confirm.
  5. Download the resulting archive locally.

Backing Up the Buzzy Database in DirectAdmin

  1. From the dashboard, open MySQL Management.
  2. Click the database Buzzy uses (check config.php or your install's env file if unsure).
  3. Use the Download / export option to save a .sql dump.

Backing Up the Buzzy Database in cPanel

  1. Open phpMyAdmin under the Databases section.
  2. Select your Buzzy database from the left sidebar.
  3. Click the Export tab, choose the Quick method and SQL format, then click Go.
Faster option: Both panels include a one-click full account backup. In cPanel it's BackupDownload a Full Account Backup. In DirectAdmin it's Create/Restore Backups. This bundles files, databases, and email in a single archive, perfect for a pre-update snapshot.

Step 3: Update Buzzy Safely

With your snapshot secured, you can update. If your Buzzy license supports staging, always test there first. If not, do the update during your lowest-traffic hours.

  1. In the Buzzy admin, enable Maintenance Mode if available (Settings → General). This shows visitors a friendly notice instead of half-loaded pages.
  2. Upload the new Buzzy files via File Manager, overwriting the old ones. Do not delete your config.php, .env, or the uploads folder.
  3. Visit yourdomain.com/admin/update or the install script if the changelog mentions database migrations. Buzzy will apply schema changes automatically.
  4. Clear your caches (see Step 5), disable Maintenance Mode, and test the site.

Updating Plugins and Add-ons

Update one plugin at a time, not all at once. If something breaks, you'll know exactly which add-on caused it.

  1. Go to Plugins (or Add-ons) in the Buzzy admin.
  2. Update a single plugin, then reload the front end and admin.
  3. Check key pages: homepage, a post, the submit/list form, and login.
  4. Only move to the next plugin once the current one is confirmed working.

Step 4: Test Before Declaring Victory

Run through this quick checklist after any update:

  • Homepage and category pages load without errors.
  • A single post displays correctly, including images and share buttons.
  • Admin login works and settings are intact.
  • New content can be created and published.
  • Reactions, comments, or voting features respond.

If anything looks off, restore your snapshot immediately rather than trying to patch a live problem.

Step 5: Clear Caches After Updating

Buzzy sites on Hostiso benefit from LiteSpeed caching and Redis object caching, which is great for speed but can serve stale pages after an update. To clear it:

  • Clear Buzzy's internal cache from the admin (Settings → Cache, if present).
  • In cPanel, open the LiteSpeed Web Cache Manager and flush the cache.
  • Hard-refresh your browser (Ctrl+F5) to confirm you're seeing the fresh version.

Step 6: Automate Backups So You Never Forget

Manual snapshots are great before updates, but daily automated backups protect you from everything else. Both panels support scheduled backups.

Automated Backups in DirectAdmin

  1. Go to Create/Restore Backups from the dashboard.
  2. Select the data to include: home directory, databases, email, and settings.
  3. If your host enables it, use Schedule Backups to run daily or weekly.
  4. Choose a remote destination (FTP or another server) so backups don't sit only on the same disk.

Automated Backups in cPanel

  1. If JetBackup is available, open it and review the automatic daily/weekly snapshots already running.
  2. Otherwise, use Cron Jobs to schedule a backup script. A simple database dump cron looks like this:
0 3 * * * mysqldump -u DBUSER -pDBPASS DBNAME > /home/USER/backups/buzzy-$(date +\%F).sql

This runs every night at 3 AM and timestamps each dump. Add a second cron to compress your Buzzy files, and periodically download or offload them to remote storage.

Good to know: On Shared Hosting and Cloud VPS plans at Hostiso, backups land on fast NVMe storage and restores are quick. Our 24/7 support team can also help you set up scheduled backups or restore a snapshot if an update goes sideways.

Recommended Update Routine for Buzzy

  1. Read the changelog.
  2. Take a full snapshot (files + database).
  3. Enable maintenance mode.
  4. Update Buzzy core, then plugins one at a time.
  5. Run migrations if required.
  6. Clear LiteSpeed and Redis caches.
  7. Test the checklist, then disable maintenance mode.
  8. Confirm your automated backups are still running.

Frequently Asked Questions

Will updating Buzzy delete my posts or settings?

A proper update overwrites core files only, not your database or uploads. Your posts, users, and settings live in MySQL and the uploads folder, which is why keeping config.php, .env, and uploads untouched during the file upload is so important.

How often should I back up my Buzzy site?

Automate a daily backup for active sites and always take a manual snapshot right before any update. For high-traffic content sites, daily plus a pre-change snapshot is the sweet spot.

My site broke after updating a plugin. What now?

Restore the snapshot you took before updating, or roll back just that plugin's files from your backup archive. Because you updated plugins one at a time, you already know which one caused it. If you're stuck, Hostiso support can help restore from your latest backup.