Cumulus Support

Is everyone having the same problem as me with graphs/charts at the moment? Since yesterday morning, none are displaying, either on my website or my local Cumulus MX interface, and I seem to see the same when browsing to other Cumulus sites. I guess this is a highcharts issue rather than Cumulus?

In my browser (Chrome) the Console shows the following errors when trying to display "Recent" graphs in the local interface:

GET https://code.highcharts.com/stock/9.1.0/highstock.js net::ERR_BLOCKED_BY_CLIENT
graphs.html:114 GET https://www.ashingtonmet.co.uk/assets/v ... ing.min.js net::ERR_ABORTED 404
graphs.html:116 GET https://code.highcharts.com/stock/9.1.0 ... porting.js net::ERR_BLOCKED_BY_CLIENT
graphs.html:117 GET https://code.highcharts.com/9.1.0/modules/boost.js net::ERR_BLOCKED_BY_CLIENT
graphs.html:118 GET https://code.highcharts.com/9.1.0/themes/grid.js net::ERR_BLOCKED_BY_CLIENT
cumuluscharts.js:256 Uncaught ReferenceError: Highcharts is not defined
at doTemp (cumuluscharts.js:256:5)
at changeGraph (cumuluscharts.js:98:13)
at Object.success (cumuluscharts.js:87:13)
at c (jquery-latest.min.js:2:28327)
at Object.fireWith [as resolveWith] (jquery-latest.min.js:2:29072)
at l (jquery-latest.min.js:2:79901)
at XMLHttpRequest.<anonymous> (jquery-latest.min.js:2:82355)
doTemp @ cumuluscharts.js:256
changeGraph @ cumuluscharts.js:98
success @ cumuluscharts.js:87
c @ jquery-latest.min.js:2
fireWith @ jquery-latest.min.js:2
l @ jquery-latest.min.js:2
(anonymous) @ jquery-latest.min.js:2
load (async)
send @ jquery-latest.min.js:2
ajax @ jquery-latest.min.js:2
(anonymous) @ cumuluscharts.js:78
e @ jquery-latest.min.js:2
t @ jquery-latest.min.js:2
setTimeout (async)
(anonymous) @ jquery-latest.min.js:2
c @ jquery-latest.min.js:2
fireWith @ jquery-latest.min.js:2
fire @ jquery-latest.min.js:2
c @ jquery-latest.min.js:2
fireWith @ jquery-latest.min.js:2
ready @ jquery-latest.min.js:2
B @ jquery-latest.min.js:2
graphs.html:1 Unchecked runtime.lastError: The message port closed before a response was received.

It says you're missing jquery.easing.min.js

Either install that if you're using it, or delete the line: <script src="assets/vendor/jquery.easing/jquery.easing.min.js"></script>

Thanks Mapantz. No, I do definitely have that in place. I hadn't changed anything between the 10th May (was working) and the 11th (was not), but I have just discovered it is fine in both Edge and Firefox. I had already tried disabling Norton, and also the Norton SafeWeb extension in Chrome, but have just tried all the other browser extensions and I have something called "Privacy Badger" which appears to be the issue. If I tell that to ignore the relevant site pages it works fine again.

Privacy Badger is primarily an Ad and tracker blocker, so I am not sure if it managed to update itself somehow, or more likely something changed at highcharts that suddenly triggered the filtering.

Anyway it was a false alarm but possibly useful if anyone else gets the problem.

Cheers

Ah, my mistake, you were right Mapantz. Actually my jquery easing path had not been updated properly (the 'vendor' directory is no longer used). This was not the cause though and doesn't seem to effect anything else obvious.

Thanks for looking anyway!

It's still showing up in your webpage as using the vendor directory.

Your other graph pages are using: <script src="assets/jquery.easing/jquery.easing.min.js"></script> and work fine.

This is for: https://www.ashingtonmet.co.uk/custom.html

Yes I had one more file to change. I think your other previous suggestion is probably better though, i.e. to remove them. Perhaps I will at some point, as nothing on the Cumulus side seems to use that script anymore.

All seems to be OK now?!

Yes, all good now. So in summary for anyone that sees the Topic title and wants to see the conclusion:


1. The "Privacy Badger" Ad blocker/tracker blocker extension to my Chrome browser caused all graphs to stop working, and all the highcharts "Blocked by client" errors. This suddenly started happening on 11th May out of the blue.
2. My other browsers were OK primarily because I rarely use them and I have no extensions in them.
3. I also had an incorrect path to jquery.easing.min.js in several webfiles, which caused some browser errors (but no noticeable symptoms).
4. I have since noticed that enabling the Norton Safeweb browser extension also throws some errors, but again no symptoms.