v1.8.0
Show changelog
Changelog · v1.8.0
×
1.8.0 — 2026-07-09
✨ New
Delete-data-on-uninstall toggle, right on the License tab. A standard "Data Management" card on the License panel lets you decide what happens when you remove the plugin: leave it off (the default) to keep your settings and role allow-list for a future reinstall, or turn it on to permanently purge everything on uninstall. Same control, same place as every other TBC add-on.🔧 Changed
Settings screen rebuilt on the shared TBC design system. The admin page now uses the suite-wide card, token, and layout primitives for a consistent look across every add-on, and gains a sticky save bar — it tracks unsaved changes live, offers a Discard action, and confirms with a "Saved" flash — in place of the old plain Save button.📡 OTA & Internal
Ships the shared admin design-system drop-ins (lib/tbc-admin-tokens.php, lib/tbc-admin-base.php, lib/tbc-save-bar.php) and adopts them across the settings UI; retires the plugin's private admin CSS. Resynced the bundled licenser client (lib/class-tbc-licenser.php) to the canonical suite version so the unlicensed admin notice suppresses correctly regardless of plugin load order. 1.7.0 — 2026-06-20
✨ New
One-click updates from the store. Message Roles is now wired to the TBC licensing server, so new versions appear right on the WordPress Plugins screen — with a "View Details" changelog — and update in one click. No more manual zip uploads.License tab. A new License tab on the settings page where you paste your key (free with purchase) to turn on updates and the role restrictions.🔧 Changed
The role restrictions now activate once a valid license key is entered, matching every other TBC add-on. An unlicensed site falls back to Fluent Messaging's default messaging behaviour. 📡 OTA & Internal
Now wired to the store for licensing and one-click updates. Ships the shared TBC licenser client (lib/class-tbc-licenser.php). 1.6.0 — 2026-06-08
✨ New
Customizable restriction message shown to blocked members (mobile app + web chat) in place of Fluent Messaging's default denial textNew "Restriction Message" settings card with optional Title + Message 🔧 Changed
Overrides the in-chat empty state, the web send popup, and the app's denial — only for users the role rules block; everyone else sees Fluent's normal text Blank fields fall back to built-in default wording, so it works without configuration 📡 OTA & Internal
Implemented via a scoped gettext_fluent-messaging filter (no edits to Fluent, no app build) 1.5.0 — 2026-03-24
✨ New
Added space-level roles (Space Admin, Space Moderator) to all three sectionsThree role tiers: Global Manager Roles, Space-Level Roles, WordPress Roles 🔧 Changed
Space roles check fcom_space_user table via native SpaceUserPivot model Matches users who hold the selected role in any space Defaults: space admin + moderator always messageable on fresh install 1.4.0 — 2026-03-24
✨ New
Added Fluent Community roles (Admin, Moderator) to DM and Community Chat restriction sections🔧 Changed
Sender permission checks now evaluate both WP roles and FC roles All three sections (Always Messageable, DMs, Community Chats) now have consistent FC + WP role layout Either WP or FC role match grants access (OR logic) 1.3.0 — 2026-03-24
✨ New
Added Fluent Community roles (Admin, Moderator) to "Always Messageable" section🔧 Changed
Redesigned admin UI: card layout with compact chip-style role selectors Split always-messageable into WP roles + FC roles sections FC roles checked via getCommunityRoles() on target user Defaults: WP administrator + FC admin/moderator always messageable on fresh install 1.2.0 — 2026-03-24
✨ New
Any role can now be set as always-messageable (e.g. admin, team lead, support staff)🔧 Changed
Replaced "Always Allow Messaging Admins" checkbox with configurable "Always Messageable Roles" section Uses full role selector with all WordPress roles including administrator Defaults to administrator on fresh install 1.1.0 — 2026-03-24
✨ New
Added "Always Allow Messaging Admins" option (enabled by default)New admin setting with toggle in settings page 🔧 Changed
Any user can DM administrators and FC moderators regardless of role restrictions Reads target user from request body (intent_id) to check if recipient is admin/mod 1.0.0 — 2026-03-24
✨ New
Initial release Role-based DM initiation restrictions (overrides Fluent Messaging points system) Role-based community/space chat restrictions Admin settings page under TBC Community App menu (standalone fallback) Administrators and FC moderators always bypass restrictions Fail-open design: no roles selected = everyone can message
Role-based messaging control for Fluent Community
TBC Message Roles lets you decide exactly who can start conversations in your community. Restrict one-to-one direct messages and community/space chat by WordPress role, Fluent Community role, or space-level role — and show members who don’t have access a clear, friendly message instead of a generic error.
What you can do
Gate direct messages — choose which roles can start a 1:1 DM with other members.Gate community & space chat — choose which roles can post in space chat threads.“Always messageable” roles — let members always reach your staff (admins, moderators, support, etc.) even when messaging is otherwise restricted.Custom restriction message — set your own title and message shown to blocked members in both the mobile app and the web chat, instead of the default “not allowed” error. Leave it blank to use sensible built-in wording.Three role tiers — mix and match WordPress roles, Fluent Community roles (Admin/Moderator), and space-level roles (Space Admin/Moderator).
How it works
Enable role restrictions from the settings page and pick the roles allowed to message. Administrators and Fluent Community moderators always bypass the rules. If you don’t select any roles, everyone can message (fail-open) — so nothing changes until you choose to lock it down.
Requirements
WordPress 5.8+ and PHP 7.4+
Fluent Community with messaging enabled
Lightweight, no configuration overload, and free.
