Shift-reload pages, every time you upgrade Javascript on an Xwiki-based site. Especially, before saving any documents, administration, users, preferences, etc, be sure to shift-reload otherwise you'll have problems when a new Xwiki meets the old Javascript stored in the browser-cached from the previous installation. It would be a great "defensive programming" improvement for Xwiki to check the browser-cached javascript, e.g. by expected version#, or even better, by "digital signature" , before proceeding, in order to prevent this potential class of problems. Niels http://nielsmayer.com
On Tue, Sep 29, 2009 at 6:54 AM, Valdis Vītoliņš <[email protected]>wrote: > Hello friends! > I have migrated xwiki testing instance from 1.8 to the 2.0 > http://test.odo.lv:8180/xwiki/bin/view/Main/ > I could import XAR 2.0 only using hack with stopping 2.0 instance, and > ran updated DB with 1.8 web instance, imported XAR, and svitched back to > web 2.0. > It worked previous times. Though currently there are many regressions: > > 1. Can't choose different view/edit modes from the menu, only default > ones ar accessible, as drop-down menus aren't shown, > 2. Can log in only with superuser. Using other users Xwiki says: "You > are not allowed to view this document or perform this action." > 3. Cannot edit neither groups, nor users. When form is opened, it stills > with progress bar and "Loading..." message. > 4. Site index doesn't work. > > In summary it seems, there ar bunch of pages where either Javascipt > doesn't work properly, or there is global problems with page access. > Site is multi lingual, there are lot of custom objects in some spaces. I > couldn't find anything interesting in tomcat logs. > > Can you point some directions, what to check and investigate? > > Thanks in advance, > Valdis _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
