Page body
What this surface does
This is the only standalone route for the URLs module.
Operators use it to browse stored URL records, narrow the list to one page or locale, copy the public link, and jump to the related CMS page when a page-level change is needed.
How to use it
- Use
Searchwhen you know part of the URL path. - Use the
Pagefilter to inspect the URLs attached to one CMS page key. - Use the
Localefilter to narrow the inventory to one language orAny. - Use the copy action when you need the public URL for support or QA.
- Use the page-key link when you need to open the related CMS page editor and manage the page-level URL set.
What each card tells you
IDis the stored URL record identifier.Typeis the backend URL type such asdirectorredirect.Localeshows which language the record belongs to, orAnyfor a shared path.Pageshows the linkedurlPageKey.URLshows the stored path.- The footer preview shows the full public URL built from
CASINO_URL + url.
Known caveats
- Sorting by ID is FE-only. The list hook fetches the data set first and the page then reorders it in memory.
- The
Search by URL path or IDhelper text is broader than the real verified backend behavior. The core route only appliesLIKEmatching to the URL path string. - The standalone list does not expose edit or create actions. To change URLs for one page, open the linked CMS page and use the embedded
Manage URLsmodal. - The type chip label is truthful, but the current chip styling does not visually differentiate
directfromredirect.
Verification status
- status:
verified_backend_and_core - verified FE route:
/urls
- verified core route:
GET /urls