Persists the portal-wide settings record — branding, access level, auth copy and redirects, and the portal slug.
Only keys that already exist in the stored settings are accepted, so unknown fields are dropped silently. Logo, white-logo and featured-image URLs are resolved against the media table and the matching media rows are marked active so the cleanup cron does not remove them. Changing slug flushes the rewrite rules and returns a redirect_url; the slug is ignored when the FLUENT_COMMUNITY_PORTAL_SLUG constant is defined.
Endpoint
Method:
POSTPath:
/admin/generalEdition: Core
Controller:
AdminController@saveGeneralSettingsRoute source:
fluent-community/app/Http/Routes/api.php:105Controller source:
fluent-community/app/Http/Controllers/AdminController.phpRequires the FluentCommunity community-admin permission (or a WordPress super admin).
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 General Settings
Persists the portal-wide settings record — branding, access level, auth copy and redirects, and the portal slug.
Controller: AdminController@saveGeneralSettings
Route source: fluent-community/app/Http/Routes/api.php:105
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response