What's New Digest 5.4.1

5.4.1 (2026-10-16)​

• the two template modifications that add the digest preference to the admin user page are now one. XenForo changed how template macros are written in 2.3, so there was one modification per syntax and exactly one of them always matched nothing — correct, but whats-new-digest:validate reported it as an unmatched modification, which reasonably reads as a fault. A single pattern now handles both, so validate reports all modifications applied and anything else is a real problem

5.4.0 (2026-10-15)​

• 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

Minor change for XF2.2 backwards compatibility. Only required if running XF2.2 - anyone running XF2.3 can skip this upgrade if you choose.

• 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.

• update helper_account template modification to work with both XF2.3 and earlier versions
• listen for sparkpostmail_non_transactional_stop_map event and use the whatsnewdigest email stopper
• tweak unsubscribe confirmation message
• separate out getMail function so we can over-ride it and add functionality

XenForo 2.2.14 adds new functionality for adding one-click unsubscribe headers to emails. Unfortunately, the code released in 2.2.14PL2 breaks functionality by removing a core option.

This release of WND fixes the errors by relying on XF 2.2.14 to set the headers for us - which should work in the majority of cases.

Note: if you are not planning to upgrade to XF 2.2.14 yet, I recommend you do not install v5.0.6 of this addon. Installing 5.0.6 with XF 2.2.13 or earlier won't break anything - but the one-click unsubscribe headers won't be added to your digest emails, which is not ideal.

So I currently recommend:

• XF <= 2.2.13, you remain on WND 5.0.5
• XF >= 2.2.14, install WND 5.0.6

The test tool was not respecting the exclude forums list from the options - that is now fixed.

Note that this bug did not affect the emails sent to users - that did use the exclude forums list correctly.

Fixed typo in XF\EmailUnsubscribe\Processor::applyUserUnsubscribeAction - thanks to @Mouth for finding the bug!

No changes to functionality - but I removed all of the testing code from the release package.

There is no need to install this version if you already have v5.0.3 installed - it won't fix the problem and there is no new code.

If you have already installed 5.0.3 and you want to clean up the additional files, you can safely remove the following files and directories under src/addons/Hampel/WhatsNewDigest/...:

• composer.json
• composer.lock
• phpunit.xml
• tests/
• vendor/

The upgrade process doesn't delete the additional files, but it won't do any harm to leave them there.

Critical bugfix release - all users of v5.x should update to this version immediately

• rewrite job to fix some logic issues
• fix repo query which wasn't counting users the same way that we were selecting them
• remove redundant PreferenceFieldId helper class - field no longer used
• remove redundant listener function - has been moved to adapter addon