Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'Allow User Registration' instructions in README not working #286

Open
pamtbaau opened this issue Nov 30, 2021 · 0 comments
Open

'Allow User Registration' instructions in README not working #286

pamtbaau opened this issue Nov 30, 2021 · 0 comments

Comments

@pamtbaau
Copy link

Triggered by a Discourse post, I've been trying to add a menu item pointing to the user registration form.

According the README there are 2 options to realise this:

  1. "The first and easiest way is to add a page with the same slug (route) as the registration form. [..]"
  2. "A second way is to add a custom menu item that points to the registration page [..]"

I've tried them both using the following config in login.yaml:

route_register: '/register'
user_registration:
  enabled: true

Re 2.
Adding a menu-item with a url pointing to /register, works fine. The registration form is shown correctly.

Please note that "This works in most themes" is however not exactly true. This might have been true on 2 Dec 2015, but is no longer the case.

  • Only 42% of themes use config site.menu one way or another.
    Quark only uses it for modular pages and not for regular pages which use the navigation macro.
  • Halve of the themes supporting site.menu are old themes with Grav 1.7 compatibility issues.

Re 1.
I've tried several options, but cannot get this to work.
The following attempts are not working:

  • Empty page: 04.register/register.md -> blank page in browser
  • Empty page: 04.register/default.md -> blank page in browser
  • Empty folder: 04.register/ -> error 404

Only copying file /login/pages/register.md into folder 04.register/ did work.

Am I misinterpreting the instructions in README, or should the instructions be updated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant