routing wrong in new editor and settings


our IT has installed zanata as

in settings page the links/routes are now pointing to and not to

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




Alex Eng
May 8, 2018, 11:00 PM

I can confirm that this is a bug in the new editor. Thanks for letting us know, will schedule the fix.

Andreas Kappel
May 8, 2018, 8:45 AM


we have set up zanata according to this documentation:

We have also set a nginx infront of zanata to redirect to the container serving at port 8080

Alex Eng
May 7, 2018, 11:55 PM

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.

pawel spoon
May 7, 2018, 8:13 AM

administration page seems to work fine

the new editor is not using the /zanata ...

the glossary left bar navigation has this link:

so /zanata is twice there

pawel spoon
May 7, 2018, 8:08 AM

in Server Configuration we already have this:

Ready for Release
Your pinned fields
Click on the next to a field label to start pinning.


Alex Eng


pawel spoon

Tested Version/s