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:
parent
0da15f0f27
commit
2007a6fed6
|
@ -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();
|
||||
|
||||
|
|
Loading…
Reference in New Issue