When a page with the folder name "login" exists, access: site.login does not work anymore

Hi there,

when I create a page called login, the pages containing

access:
site.login: true

are not found anymore.

When I rename that login-Page, evertythings seems to work fine again.

I know, for my case, it’s not strictly required to name the page exactly that way and I have some workarounds, but I needed two days to figure that obscure bug out.

Greetins from Germany,

Lorenz

@loie, Your question does not provide specific information, so my answer might be incorrect…

The Login plugin provides its own login.md page which has a default route of /login. If you override that route with your own page called /login, I guess the Login plugin will no longer function correctly.

I have created a page 02.login/modular.md and that broke the entire login system.

@loie, Well, doesn’t that confirm my suspicion… You have overridden the default /login route with your own page. When the Login plugin calls your page, it doesn’t know how to handle it.

There is no need to create a “login” page, since the plugin already provides one.

On admin, if you go to /admin/plugins/loginand on the “Routes” tab change the “Login route” from /login to something else, I believe it should work. Don’t know what to change directly on YAML config