People 2.0 Beta, Faster Sermons, and Cleaner Modals
This release is about trust in the places churches touch every week: people records, sermon archives, modal interactions, and conditional page content. Some of the work is visible right away. Some of it is careful foundation work that makes future releases safer.
Here’s what’s new since our last update.
People 2.0 Enters Beta
What changed: Digital Church now includes the first beta foundation for People 2.0, including custom-table storage, migration tooling, audit and rollback support, REST integration, import compatibility, family relationship support, and a beta-gated tabbed editor under Settings → Features.
Why it matters: People data sits at the center of ministry operations. Names, households, family relationships, imports, and profile details need to be handled with care because churches depend on that data for follow-up, care, communication, and admin work.
People 2.0 is the next step toward a cleaner and more scalable people system. The new editor can run against existing legacy People fields while custom-table storage remains an explicit migration step. That keeps the beta useful without forcing churches into an all-or-nothing jump.
The release also adds a migration prompt when the People 2.0 editor is enabled but legacy People records have not been migrated yet. That small guardrail matters. It keeps the admin experience honest about what is active and what still needs attention.
Middle-name support was added across legacy People fields, imports, People 2.0 storage, migration, and family display paths too. It’s a small detail until you need it. Then it’s the difference between a record that feels complete and one that needs a workaround.
Sermon Archives Load with Less Waste
What changed: the sermons archive received performance work around initial rendering, archive payload caching, taxonomy count caching, and safer cache storage.
Why it matters: sermon archives can become busy pages. Recent sermons, total counts, series data, taxonomy tabs, and archive payloads all compete for database work during page load. This update reduces repeated query cost by caching archive payload and tab/count data through the object cache.
The archive also stopped using DB-backed transient writes in this path. That matters for sites where concurrent requests can create database lock pressure. Object-cache storage is a better fit for this kind of repeated frontend render data.
We also removed the React StrictMode wrapper from the sermons archive mount. StrictMode is helpful during development, but it can duplicate render work. Removing it from this archive path makes the production render lighter.
Latest Sermon Sections Now Respect Missing Video
What changed: the sermons archive template now shows the Latest Sermon section only when the newest published sermon has a saved video URL and usable embed output.
Why it matters: an empty or broken hero section makes the whole archive feel unfinished. If the latest sermon does not have video attached yet, the page now skips that section and starts with the Sermons heading and tabbed archive content.
That is a better default for real church workflows. Sermons are not always edited, uploaded, and embedded at the same pace. The archive should still look intentional while that work catches up.
Modals Are More Reliable for Forms and Content
What changed: the modal component and Beaver Builder trigger module now handle form loading and modal sizing more cleanly. Modal form content renders inline from shortcode context instead of depending on REST-only rendering, Contact Form 7 handling was removed from modal code paths, default sizing was adjusted, and close-button interaction styling was tightened.
Why it matters: modals are often used at high-intent moments: registering for an event, opening a form, reading details, or responding to a call to action. If the modal loads strangely or the form confirmation breaks, the site loses trust at exactly the wrong moment.
This release makes modal forms steadier and the interface more predictable. The defaults now keep modals viewport-safe, the close button behaves more consistently, and labels focus on the Digital Church forms flow instead of implying support paths that are not part of the current feature.
Conditional Logic Can Compare Against the Current Time
What changed: Beaver Themer gained a Digital Church conditional logic rule for comparing the current site time against a selected datetime using less-than and greater-than operators.
Why it matters: churches often need page content to change around real-world timing. Registration messages, event reminders, service details, and seasonal content may need to appear before a deadline and disappear after it.
This rule gives editors a cleaner way to handle that timing directly inside Conditional Logic. It includes server-side evaluation and client-side builder UI wiring, so the rule appears where editors expect it and evaluates consistently when the page renders.
The Result: Safer Foundations and Cleaner Sundays
This release has two tracks. People 2.0 moves the platform toward stronger long-term ministry data. Sermon, modal, and conditional logic updates make weekly site experiences feel cleaner right now.
That combination matters. Churches need big foundations to improve carefully, and they need Sunday-facing details to keep working while that foundation gets better.
If your church wants to try People 2.0 beta features or clean up sermon archives, modals, or time-based content, reach out. We can help you turn the right pieces on and make sure the workflow fits how your team actually works.