Shouldn’t this always happen? How do I force it to check that again?
I did get the “Check for updates” UI (also, I am getting timeouts using the Extension Updater, but that could be a machine performance issue).
Well, looking at status.xml it appears that it did run:
org.xwiki.platform:xwiki-platform-distribution-war 10.3 org.xwiki.platform:xwiki-platform-distribution-war 10.4Looking at the release notes, I can’t tell I should be getting that screen or not.
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.4/
Deleted status.xml, restarted Apache Tomcat, now I got the “Upgrade the flavor” UI. Strange.
When you upgrade the WAR you should always get the Distribution Wizard appearing.
See http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/DistributionWizard#HTroubleshooting which maybe could help.
As a rule you shouldn’t remove your status.xml file.
Note that by doing so; you lost your flavor so you’ll need to “repair” it. See http://www.xwiki.org/xwiki/bin/view/Documentation/UserGuide/Features/DistributionWizard#HUpgradewithRepair
No, note exactly. The currently installed flavor is searched among installed extensions (top level extension with the flavor category) so there is nothing to repair (repair is not related to the status.xml anyway but to having wiki page without the corresponding extension index).
So there’s no side effects/problems to removing the status.xml file?
Since we moved to flavors pretty much the only side effect with the standard DW is that you main end up with it (if there is something to do which may not always be the case).
Still you are loosing important information in theory (which might affect some extensions I guess) even if XWiki Standard does not use them much currently.
I’m confused. I was told to remove the status.xml in the DW Troubleshooting section:
I didn’t see any other way to get the DW to start again.
I did get the DW the first time, but it “skipped” the Flavor upgrade screen.
I also got this a few times myself but I was pretty sure we fixed it. Maybe you should try to force clear your browser cache before progressing in the DW to verify if that’s the issue?
Indeed 
But this is only for the case when you would have copied some permanent directory from a previous install (which is wrong).
This is also why I was asking Thomas what were the downsides of removing status.xml. @tmortagne would be great if you could explain there the consequences of doing that.
I answered your question in a previous message already.
Understood and I did see that note, but is there another way to force the DW process to start again?
Yes, I’ve seen it but I was asking if you could modify the documentation!
1 Like