First of all, kudos on the release of 2.0M2 -- it is awesome. I cloned /var/lib/mysql after shutdown of mysqld for quiescence, and quickly got a 5-way multiwiki replicated onto a home system: loaded in the appropriate fedora RPM packages for tomcat, installed the latest 64 bit sun jvm RPM, and everything pretty much upgraded without a hitch. Good job! * One thing I've noticed, and I'm not sure if it's due to a styling or customization that I didn't upgrade, is that the footer of documents that normally has the comments/attachment/information/history tabs doesn't work. The tabs' contents are all empty. I skipped upgrading some documents to prevent overwriting my customizations -- is there a 2.0 update lurking among these docs causing this problem: XWiki.XWikiPreferences, XWiki.XWikiAdminGroup, XWiki.WebPreferences, XWiki.Admin, XWiki.XWikiAllGroup, Main.WebHome, Panels.QuickLinks ?? * What happened to the "styling" and scrollable list in Main.SpaceIndex http://localhost:8080/xwiki/bin/view/Main/SpaceIndex?space=Main used to display in a scrollable list. Now it just inserts an ugly-looking sequence, not even in tabular format, into the document. * Finally, I'm having ongoing problems with the office-importer, which I have't really been able to get running ever since 1.8 final, when it was rearchitected to manage it's own oofice-server instance. http://code.xwiki.org/xwiki/bin/view/Applications/OfficeImporterApplicationL... is my prior result of my getting this working on Linux, allowing a more sysadmin-friendly startup of openoffice server at boot via SYSV-init (cf. chkconfig). Unfiortunately I could not get the external openoffice importer management to work. When enabled, the openoffice importer control panel would not display, giving a velocity error in place of the page contents. Using an "internally managed" ooserver instance, I had the following problems: (1) not setting "Server path /usr/lib64/openoffice.org3" gave a default path of /opt/... unfortunately, for fedora, that's not where openoffice is installed. Also, unless the code specifically checks e.g. for 32 vs 64 bit architecture, this path could also be wrong even if this particular bug is fixed. It may better to have the documentation not set user-expectations that the correct path will be chosen. Instead, a statement, on windows, this default path is chosen, on linux, a different one, etc. (2) Auto-start=yes resulted in a totally non working wiki, across all vhosts. It should die more gracefully. (3) When trying to start a internally managed ooserver-instance, I consistently get message "Inadequate privileges." despite being Admin. (I can start the external ooserver instance so openoffice seems to work). Niels http://nielsmayer.com