[AGS] AGS hardcodes /share context in multiple locations
Customer has changed the /share context to another context (presumably by renaming the war, and setting share.context property). Share is functioning properly. However, they have noticed some AGS functionality doesn't work.
Steps to Reproduce
1. Install AGS 3.3.1
2. Rename share.war to foo.war
3. Set share.context=foo
4. Go to Admin Tools > Security Controls > Configure
5. Click "Classification Reasons" tab
Classification Reasons page is rendered.
An error is thrown: "We couldn't load the data. Try refreshing your screen, or check with your Alfresco Administrator that the server is running."
We hardcode the /share context in several places. We should instead use the value of share.context. See:
Tested the issue by renaming the war file and changing the share.context property and the issue doesn’t reproduce on AGS 3.5.1-SNAPSHOT. Before closing this we need to set the correct Fix Version
We have a fix for this issue in review for the master branch.
While this seem to be an older issue (affected versions include 126.96.36.199, 3.3.1, 188.8.131.52), there's no Fix version set on the JIRA ticket. We would like to know how far back we should backport the fix.