minimum PHP is now 7.4, raised from 7.2. A forum on PHP 7.2 or 7.3 cannot install or upgrade to this version and will be told so; 5.3.2 remains available for those forums
new whats-new-digest:validate command, which checks that a forum can send the digests it is configured to send: the preference column and its values, the three cron entries, the thread limit and default frequency, excluded forums that no longer exist, how many members each period would reach, and whether the preference can still be set. It exits 0 unless a check failed, 1 on failure, and --strict reports warnings as 2
new whats-new-digest:config command, which prints the digest settings in use and where each comes from. It reads only; it changes nothing and sends nothing
logging levels have changed, and so have the messages. The per-recipient line is now debug where it was info, and the run summary is info with its counts, which is the reverse of before — a forum logging at info now gets one line per run rather than one per recipient. The recipient's email address is no longer logged at any level; the member's id and name remain. Message text is now a fixed string with the varying parts in context, and context keys are snake_case, so anything matching on the old messages needs updating
the add-on now declares its settings to the Admin API add-on, where installed, so that its text settings are shown rather than only reported as set. It holds no credentials and declares none
six phrases that nothing used have been removed
the optional logging integration now asks the Monolog Logging Service add-on for its channel through that add-on's 5.x interface, falling back to the 4.x one, so either version works. Where that add-on is absent, logging is a no-op as before
5.3.2 (2026-09-04)
digest job now caches node permissions for each recipient rather than for the visitor. XenForo keys that cache by permission_combination_id, so warming it for the visitor never applied to the users being emailed, and permission lookups fell back to one query per combination and node instead of a single batched fetch. Most noticeable on larger forums; which threads each user receives is unchanged
bugfix: user preference field in AdminCP wasn't showing in XF 2.3 due to template modifications that no longer worked - this has been fixed
bugfix: unsubscribe uses stopAllExcept by default in XF 2.3 - so we need to ensure we're stopping Whats New Digest if this is called instead of StopAll
update test tool to allow sending test emails to a specific user - and handling no threads
Updated test tool now allows you to choose a user to receive a test email digest - which means you can use a test user to validate that unsubscribe options are working as expected.
