There's a fix coming for the console error bug in IE. (Good ol IE… only browser that gets this wrong.).
What versions of IE are you using there? We're *strongly* encouraging modern browsers (not IE) from here on out, and will be aggressively dropping support for older versions of IE going forward. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Jan 23, 2013, at 1:24 PM, iamagui <chella5...@gmail.com> wrote: > The actual site is live. I took a copy of the VM and trying the upgrade of > 1.6.3 to 1.7.2. The upgrade was successful but the page(s) look different on > Internet Explorer (IE) and FireFox (FF). Please refer attachments. The > attached 'done-Error-IE.PNG' is the pop-up when I click the 'Done, but with > errors on page' in the IE 'Status Bar'. > > Could you please let me know whether I missed anything during the upgrade. > > Kindly let me know if you want me to post this under a new topic. > > Thanks in advance. > > On Tuesday, January 22, 2013 4:30:39 PM UTC-6, Christian Hammond wrote: > Hi, > > Sorry to hear you got bit by some failed upgrade problem. All upgrades > *should* be done in one transaction. > > It's *possible* that this is really a problem of some upgrade metadata that > is screwed up. Something to try is: > > $ rb-site manage /path/to/site shell > >>> from django_evolution.models import Version > >>> Version.objects.exclude(evolutions__pk__gt=0).delete() > > Back up the database first, though. > > Once you run that, try to do an upgrade again. > > Christian > > > -- > Christian Hammond - chi...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > On Jan 22, 2013, at 1:50 PM, christop...@gmail.com wrote: > >> After some investigation, the reported error above was easily fixed. >> >> As it is clearly explained here, on Windows the default configuration of >> MySql doesn't allow default value for BLOB type. Setting sql_mode to >> "MYSQL40" in my.ini solves the problem. >> >> But an error can hide another, and at the next run rb-site complained about >> a field "diff_base64" which couldn't be added because it was present already. >> >> I guess that the origin of the problem is a previous unsuccessful upgrade >> attempt to reviewboard 1.7. Some database changes shouldn't have been >> reverted properly. >> >> This database schema problem could be very difficult to fix, I think I'm >> better off setting up a new reviewboard site from scratch. And from now >> backing up my database before every upgrade ! >> >> >> >> -- >> Want to help the Review Board project? Donate today at >> http://www.reviewboard.org/donate/ >> Happy user? Let us know at http://www.reviewboard.org/users/ >> -~----------~----~----~----~------~----~------~--~--- >> To unsubscribe from this group, send email to reviewboard...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/reviewboard?hl=en >> >> > > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~----------~----~----~----~------~----~------~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en > > > <login-IE.PNG><login-FF.PNG><logged-in-IE.PNG><logged-in-FF.PNG><done-Error-IE.PNG> -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
