Stores both welcome banner variants and pre-renders their Markdown descriptions to HTML so the portal does not have to parse them per request.
Rendering happens only for a variant whose enabled flag is yes. When the logged-out variant has a button label and useCustomUrl is not yes, its link is replaced with the portal auth URL. The result is written to the options table and cached for a week.
Endpoint
Method:
POSTPath:
/admin/welcome-bannerEdition: Core
Controller:
AdminController@updateWelcomeBannerSettingsRoute source:
fluent-community/app/Http/Routes/api.php:110Controller 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 Admin Welcome Banner
Stores both welcome banner variants and pre-renders their Markdown descriptions to HTML so the portal does not have to parse them per request.
Controller: AdminController@updateWelcomeBannerSettings
Route source: fluent-community/app/Http/Routes/api.php:110
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response