What this form does
This pack covers the legacy CMS page create and edit screens under Content.
- create screen, opened from the Content list
- edit screen, opened for one existing CMS page
Both screens use the same editor shell, but create and edit have different bootstrap and submit behavior.
What operators manage here
Slugfor the page URL fragment.Categoryfrom the static legacy category list:SupportAboutResponsible Gaming
Statusas the active/inactive visibility switch.- Active language tabs loaded from the active-language list.
- Localized
Contenton the selected language tab. - Localized
Titlewhere the current screen renders the title input for the selected language.
Create vs edit
Create
- Starts with blank values, active status enabled, and
ENas the initial tab. Createwrites a new CMS page immediately.- Successful create shows a success toast and resets the form in place.
- The operator stays on the create screen after submit.
Edit
- Loads one existing page before the form is shown.
Saveupdates that CMS page immediately.- Successful save shows a success toast and keeps the operator on the same edit screen.
Common confusion
This form does not have a separate publish step. Saving the form writes directly to the admin-owned CMS page record. The only visibility control in this flow is isActive.
Important caveats
Cancelis a fixed link back to the Content list.- The legacy category selector uses a static option map.
- The title input only appears for a language when that language already has a title value in the form state. Empty or missing locale keys therefore do not expose a standalone title box on that tab.
- The status switch on this form only changes the local form value until Create or Save is submitted.
- There is no unsaved-changes confirmation on Cancel in this legacy form flow.