Updating Benecaster Safely

Benecaster updates ship on a regular schedule. Most updates are straightforward — activate the update, confirm nothing is broken, done. But when an update touches something you depend on — the feed pipeline, your bridge connection, a specific email template — it’s worth taking five minutes to test on staging before applying to production.

This page covers the full update workflow and how to install add-ons safely.

The Safe Update Workflow

Step 1 — Back Up Your Site

Take a backup before you change anything. It is the step that turns a bad update from a problem into an inconvenience, and it takes a couple of minutes.

Many managed hosts take daily backups and offer one-click restores — check whether yours does before installing anything. If not, UpdraftPlus will back up to local storage for free, which is all you need here. For extra peace of mind, UpdraftPlus and most alternatives can also push a copy to offsite storage (Dropbox, Google Drive, S3) at no added cost.

Back up both your files and your database. A Benecaster update can include a database migration, and restoring files alone will not undo one.

A restore returns your site to the moment the backup was taken, and anything that happened since is gone. For a podcast that means real losses: subscriptions taken in the meantime, new subscribers, token resets, cancellations. Restoring is a genuine last resort, not an undo button — which is the reason for Step 3 below. Keep the window between backup and update short, and prefer catching the problem on staging over restoring production.

Step 2 — Check the Changelog

Before updating, read the release notes. The changelog is at benecaster.com/docs/changelog. Look for:

Breaking changes — anything that requires a configuration change after updating
Bridge updates — changes to how Benecaster talks to your membership plugin
Feed changes — updates to RSS output that might affect podcast app behavior
Database migrations — schema changes that run on activation (these are automatic, but good to know about)

Most updates require none of these. But a 30-second changelog review means you won’t be surprised.

Step 3 — Test on Staging

Apply the update on your staging site first. If you don’t have a staging site set up yet, see Setting Up a Staging Site for Benecaster.

After updating on staging, run through the checklist in the next section.

Step 4 — Apply to Production

Once staging passes, apply the update on your production site from Plugins → Available Updates. Run the quick production checklist below.

What to Check After Updating

You don’t need to check everything every time. Run through the items relevant to what the update touched.

Benecaster checks (always):

[ ] Benecaster admin loads without errors or PHP notices
[ ] Benecaster → Dashboard loads and shows the correct subscriber count
[ ] Your staging site shows the orange staging border — if your production site shows it, staging mode is accidentally active on the wrong site

Feed checks (if the update touched feed generation):

[ ] Request your feed URL in a browser — it should return valid XML, not a blank page or error
[ ] Your feed URL works with a valid subscriber token (use a staging-active subscriber or, on production, your own subscriber account) — opening a private URL in a current browser now shows the feed landing page, not XML, since the page is served before the feed compiles. That only confirms the token is valid; check the actual feed with curl, a feed validator, or a podcast app.
[ ] An episode notification you’d expect to see is present in the feed

Bridge checks (if the update touched bridge code):

[ ] Benecaster → Settings → Subscription shows your membership plugin as connected
[ ] A subscriber who should have access can access their feed
[ ] A subscriber who cancelled recently cannot access their feed

Email checks (if the update touched email templates):

[ ] Trigger a welcome email (create a test subscriber on staging) and verify it arrives with correct content
[ ] Check email merge tags are populated — no raw {{subscriber_name}} or similar strings visible in the email body

Add-on checks (if an add-on was also updated):

[ ] The add-on’s settings screen loads without errors
[ ] Features you depend on in the add-on continue to work as expected

Installing Add-ons

Benecaster add-ons are standard WordPress plugins. You install them the same way as any other plugin.

How to Install

Get the add-on .zip file — see Downloading and Updating Benecaster Plugins →. In most cases you won’t need to: entitled add-ons update through WP Admin → Plugins automatically.
In your WordPress admin, go to Plugins → Add New → Upload Plugin
Upload the .zip file and click Install Now
Click Activate Plugin

The add-on connects to Benecaster automatically on activation — no additional setup required beyond the add-on’s own settings.

Before Installing on Production

Test add-on installation on staging first. Add-ons occasionally interact with your theme or other plugins in ways that aren’t obvious until activated. Five minutes on staging prevents surprises on production.

The same staging subscriber set and email catch-all setup you use for Benecaster updates works here.

If an Add-on Causes Problems

Deactivate the add-on from Plugins → Installed Plugins. Deactivating restores Benecaster to its pre-add-on state. No data is lost when an add-on is deactivated — subscriber records, tokens, and episode data are unaffected.

If you’re troubleshooting a conflict, deactivate plugins one at a time (starting with the most recently added) until the issue resolves.

Keeping Add-ons Updated

Add-on updates appear in Plugins → Available Updates alongside Benecaster plugin updates. Apply add-on updates the same way — staging first, production after.

Your plan covers add-on updates for as long as the add-on is included or your purchase of it is active. There is nothing separate to enter for each add-on.

Recommended Tools for Update Testing

Two tools that make testing significantly more useful:

User Switching — Test Any Subscriber’s Experience

User Switching (free, by John Blackbourn) lets you log in as any WordPress user with a single click — no password needed.

After installing, go to Users in your WordPress admin. Each user has a “Switch To” link. Click it to instantly become that user. An “Switch back to [your name]” link appears in the admin bar to return to your account.

Anything you do while switched into an account is real. You are that subscriber for as long as the switch lasts — cancelling a subscription, changing a tier, resetting a token or triggering an email all happen for real, to their account, and switching back does not undo them. This is the reason to do it on staging rather than production.

This is the fastest way to verify a subscriber experience after an update:

Does their feed URL still work?
Does the subscriber account page show the right information?
Do they see the episodes they should have access to?

Install this on your staging site. It’s too powerful to leave on production permanently, but you can install and deactivate it when needed.

Email Catch-All — See Every Email Without Sending to Real People

On staging, you need to be able to read the emails Benecaster sends without delivering them to real subscriber addresses. An email catch-all redirects all outgoing email to a single test inbox.

Emails Catch All (free) — simplest option:
Install Emails Catch All and set a catch-all address. Every email the site sends is redirected to that address instead of its real recipient. One setting, nothing else to configure. The plugin can also send you a copy while still delivering to the real recipient — on staging you want the mode that replaces the recipient, not the one that copies.

A redirected email still looks like it came from your site. Subject, sender and content are unchanged — only the recipient differs, so a staging test can read exactly like a real subscriber email landing in your inbox. Check which site sent it before you act on it.

WP Mail SMTP:
Install WP Mail SMTP on your staging site. Enable Email Log in the settings. All outgoing emails are captured in the WordPress dashboard — you can read them without any delivery. Useful when you just want to confirm the email was triggered and the merge tags are populated.

Mailtrap.io — full email preview:
Mailtrap.io (free tier available) is a test email inbox service. Configure WP Mail SMTP to use Mailtrap’s SMTP credentials on your staging site. Every outgoing email lands in your Mailtrap inbox — fully rendered, with headers, HTML preview, spam score, and more. You’ll see exactly what a subscriber would receive.

Either approach lets you safely test:

Welcome emails (correct feed URL, correct subscriber name)
Token reset emails (working link, correct new URL)
Episode notification emails (episode title, player link, correct tier)
Migration emails (if you’re testing the Migration Wizard add-on)

Quick Production Update Checklist

For a typical update with no breaking changes:

Back up files and database — or confirm your host’s daily backup ran
Read the changelog — any breaking changes or migration notes?
Apply the update on staging and run through the relevant checks above
Apply the update on production from Plugins → Available Updates
Confirm no orange border appears on your production admin
Verify your feed URL returns valid XML in a browser
Check the dashboard shows the expected subscriber count

Total time: 5–10 minutes. Most updates take closer to 5.