React editor doesn't work when deployed to non-root context (eg example.com/zanata)
Description
Environment
None
is duplicated by
relates to
Activity
Show:

Former user 23 March 2017 at 07:03

Former user 23 March 2017 at 06:28
I need info on this one. Could someone deploying to cargo please copy the config div from the deployed alpha editor page source to this bug please, as described in the earlier comment.

Former user 23 March 2017 at 02:10
Reproduced by not deploying as ROOT.war. e.g. deploy as zanata.war
Benjamin Lefevre 21 March 2017 at 15:22
Have the same issue in 4.1.1

Former user 9 March 2017 at 23:57
could you open the page source for the editor page that is not working for you, and copy the URL and the section that starts <div id="config"... and the <script>... tag that follows it? That is the only thing I can think that could be causing this behaviour.
Ready for Release
Details
Details
Assignee

Reporter

Tested Version/s
None
Story Points
0.5
Components
Sprint
None
Affects versions
Priority

More fields
Time tracking
More fields
Time trackingCreated 9 March 2017 at 01:12
Updated 27 June 2018 at 02:24
Resolved 17 October 2017 at 11:23
When running Zanata in cargo, the alpha editor does not seem to be accessible. Pressing the button yields