You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
Hey dear developer.
I love the app and recently tested it and then set taiga up for my small workplace. We installed Taiga under a subpath and everything works fine in the web version.
But unfortunately now the login through the app that previously worked perfectly fine under a subdomain doesn't work anymore.
So before it worked under taiga.mydomain.com and now doesn't work anymore under mydomain.com/taiga
The "taiga server url" field on the start screen of the app just comes up with an error (red frame)
So is there something I can do or is it something to fix easily?
Thanks so much in advance, I really appreciate the effort
The text was updated successfully, but these errors were encountered:
This would be controversial feature request. Of course position of menu items is highly opinionated, but it's been like this for a long time and I bet a lot of users are used to it. Thus I'm not sure if it will be a good idea to change this order.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey dear developer.
I love the app and recently tested it and then set taiga up for my small workplace. We installed Taiga under a subpath and everything works fine in the web version.
But unfortunately now the login through the app that previously worked perfectly fine under a subdomain doesn't work anymore.
So before it worked under taiga.mydomain.com and now doesn't work anymore under mydomain.com/taiga
The "taiga server url" field on the start screen of the app just comes up with an error (red frame)
So is there something I can do or is it something to fix easily?
Thanks so much in advance, I really appreciate the effort
The text was updated successfully, but these errors were encountered: