Navigation and extra bin in URL's after upgrading to 10.11

Help / Discuss
#1

Running Xwiki in Docker, upgraded from 10.9 to 10.11:

grep image docker-compose.yml

# Use an already built XWiki image from DockerHub.
image: "xwiki:10.11-postgres-tomcat"
image: "postgres:9.5"

After going through the Distribution and updating, for regular users, the navigation doesn’t display and existing links under “Visited” and “Updated” on the right show an extra /bin in the urls:
Instead of /bin/view/MyPage it is /bin/bin/view/MyPage

Strange thing is, logged in as admin, all looks fine.

#2

Hi, this is a known issue that’s been fixed in https://jira.xwiki.org/browse/XWIKI-16005 and in https://jira.xwiki.org/browse/XDOCKER-91.

The workaround is mentioned on XWIKI-16005:

The workaround is to set the property xwiki.webapppath properly in xwiki.cfg.

#3

Ok, uncommenting xwiki.webapppath= in the cfg file fixed the /bin/bin, but my Navigation pane is still empty as is the drop down from the current page:

xwiki12

As admin though, it’s fine for both.

#4

What’s strange, is we have a Test Xwiki on a separate server, and the only differences I have found are:

In the Production cfg file, we have our own default group set:

xwiki.users.initialGroups=XWiki.GroupAll

and in the docker-compose.yml file, we have set some JAVA_OPTIONS in Production:

  • JAVA_OPTIONS="-server -Xms800m -Xmx1600m -XX:MaxPermSize=222m -Dfile.encoding=utf-8 -Djava.awt.headless=true -XX:+UseParallelGC -XX:MaxGCPauseMillis=100"
#5

I see this in Chrome console on Production:

require.min.js?r=1:7 Uncaught Error: Script error for “/webjars/wiki%3Axwiki/xwiki-platform-tree-webjar/10.9/require-config.min.js?evaluate=true”
http://requirejs.org/docs/errors.html#scripterror
at F (require.min.js?r=1:7)
at HTMLScriptElement.onScriptError (require.min.js?r=1:30)

Hmnnn, 10.9, should be 10.11?

#6

New discovery - The Navigation appears in Edge and IE11, just not in Chrome!

Google Chrome is up to date
Version 71.0.3578.98 (Official Build) (64-bit)

Edit: However, Navigation works fine with Chrome on our test system.

#7

I think you just need to clear your browser cache!

#8

Ha! Yes, did a ctrl f5 and voila - thanks!