our IT has installed zanata as zanata.mycompany.com/zanata
in settings page the links/routes are now pointing to zanata.mycompany.com/link.. and not to zanata.mycompany.com/zanata/link..
the same is true for the new editor. i can open a file for translation in the new editor, but when i want to switch it it results in 404, cause /zanata is missing in the Uri
administration page seems to work fine
the new editor is not using the /zanata ...
the glossary left bar navigation has this link: mycompany.com/zanata/zanata...
so /zanata is twice there
How did you deploy your Zanata instance as /zanata? is by renaming the war file to zanata.war? or using web server proxy/redirection?
For our tested use case, you can either deploy as ROOT.war in JBoss that will have no context path, or rename to zanata.war which will results to /zanata path. Both of these scenarios work for us.
we have set up zanata according to this documentation: https://github.com/zanata/zanata-docker-files/blob/master/zanata-server/README.md
We have also set a nginx infront of zanata to redirect zanata.mycompany.com to the container serving at port 8080
I can confirm that this is a bug in the new editor. Thanks for letting us know, will schedule the fix.