Feature #81269
closed
Context support for sys_domain records
0%
Description
sys_domain records fail in combination with contexts (production/testing/development) because the first domain record is used for preview links in the backend, no matter what context I'm in.
This makes it hard to use the production database on testing and development systems.
sys_domain records should have a "context" field that is then used in their enableFields() hook.
Updated by Christian Kuhn almost 7 years ago
Actually, the goal is to get rid of that table altogether (along with sys_language in the end) and make it a configuration instead - in mid-term, hopefully for v9. This would allow such context dependent configurations out of the box, then.
Note: killing db dependency of language and domain configuration seems to be common agreement in core team already, the details are not sorted out yet, though.
Updated by Christian Weiske almost 7 years ago
Unfortunately, BackendUtility::getViewDomain() cannot be influenced by enableFields hooks to get a specific domain record.
Updated by Georg Ringer about 6 years ago
- Status changed from New to Rejected
as stated, domain records will vanish and be replaced by a different configuration. therefore I am closing this issue.