By fago on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
1.5
Introduced in version:
Issue links:
Description:
A new _lupus_frontend route option to control frontend/backend routing per route has been introudced:
- TRUE: Route belongs to frontend. Redirects to frontend on backend access, URLs point to frontend domain.
- FALSE: Route belongs to backend. Redirects to backend via ce-api, URLs point to backend domain in API responses.
- NULL (not set): No routing opinion. No redirects
This replaces the old lupus_decoupled_ce_api.frontend_routes service parameter. The service parameter still works and is automatically applies the route options, but is going to be dropped in a future major release.
Changes:
- New
LupusFrontendRouteSubscribersets_lupus_frontend: TRUEon routes from the deprecated frontend_routes parameter (BC bridge). - For
lupus_decoupled_ce_api.frontend_pathsthe route option is set automatically now, thus it's not necessary to set it manually.
Impacts:
Site builders, administrators, editors
Module developers