#89573Allow removal of baseUrl in backend for slug fields
Description
If field type slug is used in custom records (e.g. news), it is missleading that the baseUrl is shown before the slug field and in the update notice (“Congrats ….”),
since the final URL may vary based on routeEnhancer.
since the baseUrl is not saved in the slug field itself, I think it should be possible to stop the baseUrl from being prepended.
slug-content: “news-1“
will be displayed as: “https://domain.de” “news-1”
Not sure if it is better to have $baseUrl empty or change both occurences to check for configuration.