Forum Subscription Admin for bbPress

FAQ

Who can use this plugin?

Settings require manage_options. The user list requires list_users and access to the selected forum. Profile changes require edit_user for that user and access to the forum. A user can manage their own subscription if those checks pass. Subscribing someone additionally requires that user to be able to read the forum. Public, private, and hidden forums are supported; drafts and trashed forums are not.

Does this subscribe users to topics or child forums?

No. It changes only direct subscriptions to the selected forum. It does not change topic or child-forum subscriptions, user roles, or forum permissions.

What happens when saving fails?

Invalid or missing subscription nonces never change subscriptions. A nonce issued for a previously selected forum is rejected. WordPress profile validation failures leave subscriptions unchanged. After a successful profile save, the plugin verifies the requested subscription state. If that step fails, it shows a separate error explaining that the profile was saved but the subscription needs checking. Successful saves use the standard WordPress profile update confirmation.

Does it send email?

The plugin itself does not send subscription-confirmation email. Future notifications are handled by bbPress and any installed integrations. A subscribed status does not guarantee email delivery.

Does it work on multisite?

Settings and forum data are site-specific. Use each site’s administration screens. Network user administration has no subscription controls. A profile must belong to the current site before its subscription can be changed. Network activation does not create settings or alter subscriptions on any site.

What happens on deactivation or deletion?

Both the site option bbpfsa_forum_id and all bbPress subscriptions are preserved on deactivation and deletion. This intentionally preserves the existing plugin behavior. Before deletion, save 0 to clear the selected forum. The option may remain stored as 0. No uninstall routine deletes subscription data.

Is it suitable for a large user directory?

Subscriber IDs are cached once per request and membership lookups use an indexed set. Filtering uses WordPress include/exclude arguments, preserving other query constraints. Memory use and SQL IN/NOT IN size still grow with the number of subscribers. Benchmark on staging before using very large subscriber lists.

日本語で利用できますか？

WordPress.orgの日本語言語パックが公開・インストールされている場合、WordPressまたはユーザーの言語設定に従って日本語を表示します。翻訳がない場合は英語で表示します。翻訳ファイルはプラグインZIPに同梱しません。「設定」→「掲示板購読」でフォーラムIDを設定し、「ユーザー」画面で状態の確認・絞り込み、プロフィール画面で購読の登録・解除ができます。対象フォーラムへの直接の購読のみを扱い、個別トピックや子フォーラムの購読は変更しません。停止・削除時にも既存の購読データと設定値を保持します。