#2694 closed task (fixed)
Weblate sign-in screen does not contain any information about how to "register" (to LDAP)
Reported by: | strk | Owned by: | cvvergara |
---|---|---|---|
Priority: | normal | Milestone: | Sysadmin Contract 2023-II |
Component: | SysAdmin/Weblate | Keywords: | |
Cc: |
Description
The SignIn page doesn't say HOW to get an account: https://weblate.osgeo.org/accounts/login
Change History (9)
comment:1 by , 3 years ago
Milestone: | Sysadmin Contract 2022-I → Sysadmin Contract 2022-II |
---|
comment:2 by , 23 months ago
Milestone: | Sysadmin Contract 2022-II → Sysadmin Contract 2023-I |
---|
pushing to next milestone since my contract funds have been used.
comment:3 by , 14 months ago
A contributor user just mailed sysadmin asking how he could translate given registration was closed. I suppose this issue is what confuses him... Time to deal with it!
comment:4 by , 14 months ago
weblate is a docker, I found for example where to the icons are within the docker container, like the favicon. This are possible files to modify
for the reset_url : https://github.com/WeblateOrg/weblate/blob/ac50f44f72e75e37ec51f27ea8a0667808b32238/weblate/templates/accounts/login.html
for the about: https://github.com/WeblateOrg/weblate/blob/ac50f44f72e75e37ec51f27ea8a0667808b32238/weblate/templates/snippets/about.html
Looking right now where to change the in the configuration the reset_url
comment:5 by , 14 months ago
Milestone: | Sysadmin Contract 2023-I → Sysadmin Contract 2023-II |
---|---|
Owner: | changed from | to
It would be good to have those overrides deployed via Ansible
comment:6 by , 14 months ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Could not modify the messages or the page, but created a redirection of the forgot your password?
link on nginx
rewrite ^/accounts/reset$ https://id.osgeo.org redirect;
comment:8 by , 14 months ago
Could the login page template not be customized to add a Sign Up section ?
comment:9 by , 14 months ago
Maybe the templates/ dir needs be a mount of a directory on the host ? This is another case of "done with ansible would be easier to deal with" ...
Ticket retargeted after milestone closed