Disabling activities/notifications/watch can serve any law or policy, not only
GDPR. Remove GDPR mentions from the code comments and the en.i18n.json toggle
descriptions (and the Admin Panel docs), keeping the neutral #5820 reference.
New Notifications category with three GDPR toggles (all default off), enforced
server-side:
- Disable all activities: activity-feed entries are neither recorded
(Activities.before.insert returns false to cancel) nor shown (the activities
publication returns nothing, hiding existing and new entries).
- Disable all notifications: the Activities.after.insert dispatch hook returns
early, so no watch notifications are sent; activity recording is unaffected.
- Disable watch: the watch() method rejects any watch-level change, and the board
header watch button is hidden.
A synchronously-readable server cache (models/lib/featureFlags.js, kept current by
a Settings observer) lets the sync before.insert hook read the flags without
awaiting. Adds settings disableActivities, disableNotifications, disableWatch,
published in the public setting, plus global Blaze helpers activitiesDisabled /
watchDisabled for UI hiding.
On the server only the default (English) translation bundle is loaded at
startup. Translating a notification to a user's language called
TAPi18n.__(key, params, lang) with lng=lang, but that resource bundle was
never added on the server, so i18next fell back to English — every
notification email went out in English regardless of the user's profile
language. (The client works because switching language calls setLanguage,
which loads the bundle.)
Add TAPi18n.ensureLanguageLoaded(language), which loads the bundle on
demand if i18next does not already have it, and await it before translating
in the email notification, EmailLocalization.sendEmail and outgoing webhook
paths.
Closes#5875
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Thanks to apiccolim, Raawen-dev and xet7 !
Fixes#6280
**Fix 1 — [models/cards.js:2170](models/cards.js)**: Added `await` to `Cards.updateAsync()` in the `move()` method.
Without `await`, the card update was dispatched as a fire-and-forget Promise. In Meteor 3's AsyncLocalStorage-based DDP context, this can cause the collection hooks (`after.update`) to fire outside the original DDP method context, making `Meteor.userId()` return `null`. With `await`, the async chain is intact and the DDP userId context is preserved through to the hooks.
Also tightened the `UserPositionHistory` guard to `typeof Meteor.userId === 'function'` — the error log showed `TypeError: o.Meteor.userId is not a function` in certain bundle contexts, and this guard prevents that crash.
**Fix 2 — [server/rulesHelper.js](server/rulesHelper.js)**: Added `withUserId()` helper that sets `DDP._CurrentMethodInvocation` before calling `card.move()` from rule execution.
When automation rules trigger a card move, the code runs in a server-side callback with no active DDP method invocation. `CollectionHooks.getUserId()` → `Meteor.userId()` returns `null`, so the resulting activity gets `userId: null`, and the email shows `undefined`. Wrapping `card.move()` in `DDP._CurrentMethodInvocation.withValue({ userId: activity.userId }, ...)` restores the user context so hooks pick up the correct userId.
**Fix 3 — [server/notifications/email.js:37](server/notifications/email.js)**: Defensive fallback `const actorName = params.user || ''` instead of interpolating `params.user` directly.
If `params.user` is ever `undefined` (e.g., activity inserted without a userId from a migration or cron job), the template previously produced the literal string `"undefined moved card X to list Y"`. The fallback produces a blank actor name instead, which is less confusing and avoids the regression.
Add missing await to EmailLocalization.sendEmail() calls and replace
fallback Email.send with Email.sendAsync in the notification email
handler and rules helper. The notification handler runs inside an
async setTimeout callback where the missing await meant email errors
were unhandled promise rejections instead of being caught.
Fixed bug with the reference to the customFieldValue in the cards.js
Activity Insert was not being passed the listId, swimlaneId which was required when building the webhook text string.
Added customField and customFieldValue as default values for the webhook msgs. There is no good reason to exclude these (they will only be included when changing a customField anyway). Updated the docker-compose comment to reflect this change.
responsible disclosure by [Dejan Zelic](https://twitter.com/dejandayoff),
Justin Benjamin and others at [Offensive Security](https://twitter.com/offsectraining),
that follow standard 90 days before public disclosure.
Thanks to xet7.
- Fix webhook error that prevented some card etc deleting from web UI of board.
Thanks to xet7.
- Add some more Font Awesome icons.
Thanks to xet7.
- Remove autofocus from many form input boxes so that they would not cause warnings.
Thanks to xet7.
Lauri Ojansivu
Harry Adel
Omar Abid
Yevhenii Pertiaka
Martin Filser
Jan Küster
n8ores
Jonathan Baird
Sam X. Chen
William Hughes
Justin Reynolds