Mumara Campaigns 7.0.1
Release Date: May 2026 Type: Minor Release (Stabilization) Previous Version: 7.0
Version 7.0.1 is a stabilization release on top of 7.0. It strengthens the trigger engine, fixes several segmentation and dynamic-content edge cases reported after the 7.0 rollout, repairs a few PHP 8.4 issues on the admin dashboard, and rolls in a handful of quality-of-life upgrades — List-Unsubscribe headers for Drip Groups, a new Stable / Beta / Specific Version channel selector in the update wizard, and deep-linked Help Article buttons that point at the new docs.mumara.com site.
If you're already on 7.0, this update is straightforward — no schema upheavals, no architectural shifts, and no manual steps required.
Highlights
| Area | Summary |
|---|---|
| Trigger Engine | Forward-cursor processing — trigger runs are stable, crash-resilient, and resumable across worker restarts |
| Drip Groups | Native List-Unsubscribe header support, matching scheduled-campaign behaviour |
| Update Wizard | New Stable / Beta / Specific Version channel selector with live version badges |
| Help Articles | Migrated to docs.mumara.com with deep-linked anchors on every Add/Edit screen |
| Dynamic Content Tags | Cleaner Single/All return-mode model, smarter per-tag preview regeneration |
| Segmentation Fixes | "Does not contain" / "Is not" filters now correctly include subscribers with no stored value |
| Admin Dashboard | License-attributes crash on PHP 8.4 fixed with self-healing fallback |
| Security | phpseclib bumped from 3.0.50 to 3.0.51 |
Before You Update
7.0.1 is a minor release — there are no architectural changes, no storage restructures, and no breaking changes. The in-app updater handles everything for you.
How to Update
Navigate to Tools → Update in the admin panel. The new channel selector lets you pick how you want to receive future releases:
- Stable — production-grade releases (recommended)
- Beta — early access to upcoming features for testing environments
- Specific Version — pin to an exact version number
Pick Stable unless your team has a specific reason to test pre-release builds, and click Begin Update. The wizard handles the rest.
Server requirements are identical to 7.0 — PHP 8.4 (with 8.3 and 8.5 also supported), Laravel 12, MySQL 8.0+ recommended.
Backup First
Even for minor releases, take a quick database and files backup before updating. It costs you nothing and gives you a clean rollback path if something unexpected happens in your environment.
Trigger Engine — Stable & Resumable
The trigger processing engine has been hardened against the failure mode that was most painful in 7.0: a worker crashing or being restarted mid-run, leading to either skipped subscribers or double-processed subscribers.
In 7.0.1, triggers iterate subscribers using a forward cursor that is persisted as the run progresses. If a worker is interrupted, the next run picks up exactly where the previous one left off — no gaps, no duplicates.
What you'll notice:
- Long-running trigger executions complete reliably even on busy servers
- Worker restarts (planned or unplanned) no longer cause subscribers to be missed or processed twice
- Duplicate trigger evaluations are filtered out cleanly instead of erroring
This change is automatic — no configuration, no migration steps for you. Existing triggers continue to work without modification.
List-Unsubscribe Headers for Drip Groups
Drip emails can now advertise a List-Unsubscribe header — the same way scheduled broadcasts already do. This improves deliverability with major mailbox providers and gives subscribers a one-click unsubscribe option directly from their inbox.
On the Drip Group form you'll find:
- Master toggle to enable List-Unsubscribe headers for every email in the group
- Link option — include the unsubscribe URL in the header
- Mailto option with a configurable mailto address — let recipients unsubscribe by email
The header is emitted automatically when the drip starts sending — no per-email configuration required.
Enabling List-Unsubscribe is a deliverability best practice for any list-based email. Most major providers (Gmail, Yahoo, Apple Mail) now expect or require it on bulk sends.
Update Wizard — Channel Selector
The new in-app updater (introduced in 7.0) now exposes the same three update channels that the command-line edition supports:
| Channel | Best For |
|---|---|
| Stable | Production installations — official, fully-tested releases |
| Beta | Staging or test environments — early access to upcoming releases |
| Specific Version | Pinning to an exact version (handy for rollbacks or coordinated upgrades across multiple installations) |
Each option displays a live version badge so you can see the latest build available on each channel before you commit to updating. When no beta is currently published, the Beta option shows an Unavailable state instead of failing silently.
The Begin Update button is channel-aware — it always reflects the version you'll actually receive.
Help Articles — Refreshed and Deep-Linked
Every Help Article button in the admin panel has been updated to point at the new docs.mumara.com documentation site. On top of the URL migration, each button now deep-links to the relevant section anchor on the docs page — so clicking Help Article from the Sending Domains screen lands you on the Sending Domains section of the docs, not the parent topic page.
Newly wired pages (previously missing a help link):
- Add-ons, DB Check, Authentication Logs, Bounce Rules
- PHP Info, Languages, AI Settings, AI Builder
- My Profile, Security, Drip Groups list
- Broadcast Templates, Failed Jobs
Newly anchored pages on Add/Edit screens:
- Lists & Contacts — contact lists, custom fields, segments (create + edit)
- Campaigns — broadcasts, evergreen edit, drip groups, drips, split tests, spintags, dynamic content tags
- Setup — bounce addresses, bounce rules, sending domains, sending nodes, web forms, feedback loops, administrators, admin roles, profile fields, email templates, marketplace
- Users — users, packages, user roles
- Stats Detail — broadcast and trigger statistics detail pages
The application-level "disable help" setting still works as before — when help is disabled, the Help Article button is hidden site-wide.
Dynamic Content Tags — Cleaner Model
Dynamic Content Tags have been reworked to use a clearer Single / All return mode instead of the legacy storage format used in 7.0. The result is a more predictable preview-generation flow and fewer edge cases when tags are saved or updated across broadcasts, drips, and web forms.
What changed under the hood:
- New return mode field replaces the legacy storage sentinel — existing tags are migrated automatically
- The per-tag preview regeneration flow has been consolidated, eliminating redundant work that previously fired on every save
- The dynamictag:convert command gained two new options for operators who manage dynamic tags at scale:
- Rebuild a single tag instead of all of them
- Skip specified tags during a bulk rebuild
- Repair only missing previews (don't regenerate existing ones)
Existing dynamic content tags continue to work without any manual changes — the migration runs as part of the update.
Segmentation & Custom Field Fixes
Several segmentation edge cases that surfaced after 7.0 have been addressed:
"Does Not Contain" / "Is Not" — Custom Fields
Custom-field filters using does not contain or is not previously dropped subscribers who had no value stored for the field. Those subscribers are now correctly included in the matching set — which is the behaviour most operators expect.
"Does Not Contain" — Empty Value Lists
A "does not contain" filter with an empty or comma-only value (for example, ,,,) silently excluded every subscriber in 7.0. Empty value lists are now treated as a no-op filter, so the segment matches normally instead of returning zero subscribers.
Segment Recount Cron
The segment recount cron was always falling back to a daily run, ignoring the per-user interval configured under Settings → Cron Settings. The configured cadence is now respected.
PHP 8.4 Compatibility on Admin Dashboard
A missing license_attributes row caused a fatal error on the admin dashboard under PHP 8.4 (where missing-key warnings are now strict errors). 7.0.1 fixes this in two places:
- The dashboard view safely handles a missing license attributes row instead of crashing
- The license-validation logic self-heals the missing row on the next license check, using the cached license payload — no extra remote calls
If you saw a blank or errored admin dashboard on a self-hosted install after upgrading to 7.0, this update resolves it.
Other Improvements
Performance & Reliability
- Email previews are no longer compiled twice when a new broadcast, drip, or web form is created — saving a new record now does the work once
- Preview repair (
--missing-onlyflag) now verifies the full set of preview files (HTML, text, subject) instead of only the HTML file, so partial caches caused by mid-write errors are correctly detected and rebuilt - API rate limiting is now scoped per token — each API token gets its own throttle bucket
- Empty API tokens are treated as no token instead of being accepted as a string, preventing false-positive authentications
- Split Test create/edit page no longer hangs on installations with large subscriber tables — dead database queries that the screen never used have been removed
Logging & Diagnostics
- Preview compilation failures in autoresponders and web forms now log to
laravel.loginstead of being silently swallowed during HTTP requests — storage and permission issues are now visible in production logs - Beta version lookup is now validated with a regex, so a 404 HTML page from the update server can no longer be mistakenly treated as a valid version number
UI Polish
- Login page styling regression introduced in 7.0 fixed
- AI menu icon rendering corrected on the default theme
- Drip Groups card border styling fixed
Security
- phpseclib bumped from 3.0.50 to 3.0.51 for SFTP/SSH security and stability improvements
Breaking Changes
None. 7.0.1 is fully backward-compatible with 7.0 — no configuration changes, no schema migrations beyond the dynamic-content-tag normalization (handled automatically), and no API contract changes.
Getting Help
If anything looks off after the update, please contact your Mumara team member with:
- The exact error message (or a screenshot)
- Which updater channel you used (Stable, Beta, or Specific Version)
- Your previous Mumara version and current PHP version
You can also visit our Support Portal or review the Troubleshooting guide.
Last updated on May 6, 2026