如何将SilverStripe中的安全性/登录URL别名更改为用户/登录

Question

I am working on a new website being built in SilverStripe. Currently I am having a ton of trouble trying to get the system to let me change the URL alias (or create a second one) for the Security controller's login (and eventually logout) function.

I have tried playing around with the routes.yml file and I tried creating the paths in my own UserController and loading directly from the Security controller with "return Security::login()". But that gives me errors about the use of the static functions.

Unfortunately I don't come from a ton of object oriented experience and this is the first CMS I have used that actually uses a bunch of true object orientation. The current version of SilverStripe we are using is 3.0 (but we will be upgrading to 3.1.1 in a few days).

Does anyone know much about the routing in SilverStripe?

Answer 1

as you stated correctly, SilverStripe has routes, and they can be defined in a yaml config file.

if you take a look at the existing routes.yml in the framework you can see how the default security route is defined: https://github.com/silverstripe/silverstripe-framework/blob/fd6a1619cb7696d0f7e3ab344bc5ac7d9f6cfe77/_config/routes.yml#L17

if you just want to replace the Secuirty in Secuirty/login, its as easy as just creating your own routes.ymlin mysite/_config/ with the following content:

---
Name: myroutesorsomeotherrandomname
Before: '*'
After:
  - '#rootroutes'
  - '#coreroutes'
  - '#modelascontrollerroutes'
  - '#adminroutes'
---
Director:
  rules:
    'foobar//$Action/$ID/$OtherID': 'Security'

NOTE: make sure you ran a ?flush=1 to ensure the yml file is loaded (they get cached)
also make sure you use spaces in the yml file, if you use tabs you are going to have a bad time

---

if you however wish to also replace /login and /logout this is no longer a thing for routing.
login and logout are actions (php functions that are listed in Security::$allowed_actions and thus available as URL) on the on Security.
but its still rather easy, just subclass Security and create the actions you want:

<?php

class MySuperSecurity extends Security {
    private static $allowed_actions = array(
        'showMeTheLoginForm',
        'alternative_login_action_with_dashes',
        'doTheLogout',
    );

    function showMeTheLoginForm() {
        // can be visited via http://website.com/foobar/showMeTheLoginForm
        return $this->login();
    }

    function alternative_login_action_with_dashes() {
        // can be visited via http://website.com/foobar/alternative-login-action-with-dashes
        return $this->login();
    }

    function doTheLogout($redirect = true) {
        // can be visited via http://website.com/foobar/doTheLogout
        return $this->logout($redirect);
    }
}

and make the route point to your new class instead of Security inside the routes.yml:

    'foobar//$Action/$ID/$OtherID': 'MySuperSecurity'

NOTE: again, make sure you did a ?flush=1, both the private static $allowed_actions as well as the yml config file are cached by silverstripe.
NOTE: both solutions suggested in this post will create an additional route to login and does not replace the existing one, so the old Security/login will still be available