avoid CMS coupling

In the current setup, we cannot use a custom security controller without the cms module. This changes allow setting another controller as "page_class".
This commit is contained in:
Thomas Portelange 2021-01-19 16:51:46 +01:00 committed by GitHub
parent 0da15f0f27
commit 2007a6fed6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 1 deletions

View File

@ -579,8 +579,13 @@ class Security extends Controller implements TemplateGlobalProvider
$holderPage->URLSegment = 'Security';
// Disable ID-based caching of the log-in page by making it a random number
$holderPage->ID = -1 * random_int(1, 10000000);
if ($holderPage instanceof Controller) {
$controller = $holderPage;
} else {
$controller = ModelAsController::controller_for($holderPage);
}
$controller = ModelAsController::controller_for($holderPage);
$controller->setRequest($this->getRequest());
$controller->doInit();