-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Option to skip welcome page #12551
Comments
the homepage can be already disabled in config.json |
I am having trouble finding that option. I tried setting |
Null should do it. |
There's not currently an option to skip the welcome page. You can change the welcome page content, but if you set the setting to |
That works but causes awkward flashing. Scripts I write in the welcome page don't seem to run either. I can add a config option a make a merge request if you want. |
I'd want to check with the product team and development team before recommending a PR on this, only because this particular area of the code is hard enough to maintain and another config option might make it worse/impossible. |
How? I tried putting a |
This now exists as the
We used this on https://app.gitter.im/ and it works great! |
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Is your suggestion related to a problem? Please describe.
I am setting up a private server and would like users to be able to log in as quickly as possible. I don't need a welcome page explaining what riot and matrix are.
Describe the solution you'd like
I would like a server wide config option that if true takes the user to the log in page whenever it would take them to the welcome page, i.e. whenever a unauthenticated users goes to the main page or any room's url, or logs out.
Describe alternatives you've considered
It would be sufficient to redirect unauthenticated users to the login page whenever they go to and address like #/home or #/roomid.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: