Replaces the portal navigation configuration, preserving the protected attributes of built-in menu entries.
Items missing a title or a permalink are discarded. Items without a slug are treated as new custom entries and get a generated one. For entries that already exist, is_system, is_locked, is_unavailable and slug are carried over from the stored version so a client cannot promote a custom link into a system one.
Endpoint
Method:
POSTPath:
/settings/menu-settingsEdition: Core
Controller:
SettingController@saveMenuSettingsRoute source:
fluent-community/app/Http/Routes/api.php:157Controller source:
fluent-community/app/Http/Controllers/SettingController.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 Menu Settings
Replaces the portal navigation configuration, preserving the protected attributes of built-in menu entries.
Controller: SettingController@saveMenuSettings
Route source: fluent-community/app/Http/Routes/api.php:157
Authorizations
WordPress Application Passwords — use Basic auth with username:application_password.
Request Body
Responses
Successful response