Saves the feature flag configuration, merging the submitted flags over the stored ones.
Only recognised flags are accepted — courses, leaderboard, Giphy, emoji, badges, cloud storage, CRM sync, followers, custom profile fields and PWA. Enabling the Giphy module requires a key. Sending back the FCOM_ENCRYPTED_DATA_KEY placeholder preserves the stored key instead of overwriting it.
Endpoint
Method:
POSTPath:
/settings/featuresEdition: Core
Controller:
SettingController@setFeaturesRoute source:
fluent-community/app/Http/Routes/api.php:155Controller source:
fluent-community/app/Http/Controllers/SettingController.phpRequires the FluentCommunity community-admin permission (or a WordPress super admin).
Several flags gate whole route groups, so turning one off removes its endpoints on the next request.
Live sample
The request and response below were recorded against a running FluentCommunity install and then anonymised — member names, emails, avatars and post content are fictional, and long collections are trimmed to a few entries.
POST Save Feature Settings
Saves the feature flag configuration, merging the submitted flags over the stored ones.
Controller: SettingController@setFeatures
Route source: fluent-community/app/Http/Routes/api.php:155
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response