Haha awesome.

I should add that I get the same error when I try to edit a page. Most of the 
page loads but the edit control (MCE — UI widgets and textarea or input or 
whatever) just shows a loading spinner forever with the same error as below.

I filed http://jira.xwiki.org/browse/XE-1602 
<http://jira.xwiki.org/browse/XE-1602> for the mixed content issue; however 
that was an issue that was also in 8.4.3.

Should I file another issue for this?

Thanks,
Craig

> On Jan 11, 2017, at 11:19 PM, Ludovic Dubost <ludo...@xwiki.com> wrote:
> 
> Indeed this looks upgraded. Now if you are getting errors in chrome on the
> home page the. That could be the empty document tree as it does JavaScript.
> The http/https issue might be more general. You might have found a blocker
> bug on 8.4.x
> 
> Ludovic
> 
> Le 12 janv. 2017 09:12, "Craig Wright" <crw+xw...@crw.xyz> a écrit :
> 
>> Hi Ludovic,
>> 
>> It appears as if it did. When I look at the installed extensions, I see:
>> 
>> XWiki Enterprise - UI - Tour 8.4.4
>> XWiki Enterprise Flavor - Main Wiki 8.4.4
>> XWiki Enterprise - UI - Common 8.4.4
>> 
>> The "XWiki Enterprise Flavor - Main Wiki”  was the extension that choked
>> on the Distribution Wizard with the mixed content error; I clicked “Later”
>> but it looks like the upgrade worked, or kinda worked?
>> 
>> Thanks,
>> Craig
>> 
>>> On Jan 11, 2017, at 11:03 PM, Ludovic Dubost <ludo...@xwiki.com> wrote:
>>> 
>>> Did your upgrade go through ? When you started XWiki after the debian
>>> package upgrade you should have seen the distribution wizard to complete
>>> the upgrade.
>>> 
>>> Maybe your http issue is the cause. If it's that try accepting the
>>> http/https mixed content from chrome and/or go back to http to finalize
>> the
>>> upgrade
>>> 
>>> Ludovic
>>> 
>>> Le 12 janv. 2017 08:57, "Craig Wright" <crw+xw...@crw.xyz> a écrit :
>>> 
>>>> Howdy again,
>>>> 
>>>> I just upgraded to 8.4.4 via the Ubuntu packages, and the Navigation
>> Panel
>>>> has no content whatsoever! It’s blank except for the title. Is there a
>>>> quick or obvious fix for this?
>>>> 
>>>> Thanks,
>>>> Craig
>> 
>> 

Reply via email to