Feature #86549
openAllow Backend URL to be specified for Admin Panel
0%
Description
This feature request is related to #86548
Imagine you have a multi-domain install:
- domain1.example.com
- domain2.example.com
- domain3.example.com
You want (for whichever - good - reason) to force (or at least highly suggest) the webmasters to access the Backend through admin.example.com.
In order for Admin Panel to work, the trick is to force the FE/BE cookies like that (typically in AdditionalConfiguration.php
):
$GLOBALS['TYPO3_CONF_VARS']['BE']['cookieDomain'] = '.example.com'; $GLOBALS['TYPO3_CONF_VARS']['FE']['cookieDomain'] = '.example.com';
This will effectively allow the Admin Panel to show up whenever you are authenticated into the Backend (on admin.example.com) while browsing, say, domain1.example.com.
So far so good!
However then try to click on the admin panel button to edit the page:
The Backend will open up but using domain1.example.com/typo3 and not admin.example.com/admin (because there is no such configurable setting).
Note: the jump link is generated in typo3/sysext/frontend/Classes/View/AdminPanelView.php
around line 654 and generates an absolute link starting with a /
(slash), thus effectively reusing the current domain. Trying to hardcode (to test) some scheme + domain at this place won't work since the security token will not be correct.
Files