Admin Dashboard Chart Blank After 1.4.4 Update

PitaJ

Check the browser console for errors. This is most likely a socket issue.

scottalanmiller

How not found a socket error yet, but did find this...

ReferenceError: o is not defined[Learn More]  cloudflare.min.js%20line%204%20%3E%20eval:3:7420
	[25]</e.exports/<.transition/< https://mangolassi.it/assets/src/modules/Chart.js:3:7420
	[26]</e.exports/o.each https://mangolassi.it/assets/src/modules/Chart.js:3:8417
	[25]</e.exports/<.transition https://mangolassi.it/assets/src/modules/Chart.js:3:7095
	[24]</e.exports/<.draw https://mangolassi.it/assets/src/modules/Chart.js:3:5109
	[23]</e.exports/<.drawDatasets/< https://mangolassi.it/assets/src/modules/Chart.js:2:31656
	[26]</e.exports/o.each https://mangolassi.it/assets/src/modules/Chart.js:3:8286
	[23]</e.exports/<.drawDatasets https://mangolassi.it/assets/src/modules/Chart.js:2:31596
	[23]</e.exports/<.draw

scottalanmiller

So wait, if we RESIZE the browser in suddenly starts populating the chart! WHAT THE CRAP???!!! LOL

How does that work? No charts work, then all start after the browser resizes significantly?

scottalanmiller

This trick works on multiple browsers. But the issue impacts only one of the sites that we run, all use the same code on the same server.

julian

Seems confirmed, I experienced this with a hosted client after upgrade to latest master. Weird!

Can you create a GH issue? Thanks.

julian

Oh, and @scottalanmiller -- if you can rebuild the assets with the dev switch (NODE_ENV=development ./nodebb build) and try again, let us know if the error text changes

PitaJ

@julian I think ./nodebb build --dev works too

julian

@PitaJ Thanks, good to know (ha, I even called it the "dev switch" and suggested the env var...)

julian

Also looks like when you resize to "fix" the graph, the hover events don't work (nor do the controls below, to change the graph data), so it's not a complete workaround

scottalanmiller

Sorry,I've been AWOL for a week. Got stuck in Palermo without real Internet access. I just did the 1.4.5 update and things seem to be fixed now.

julian

Oh, well that's great to hear