4

Hi Matt,

I’ve tried it on my Android phone, both Chrome and Firefox and it works for both.

One of the items I changed was the function name from “multigraph_init” to “multigraphInit”, which suggests that your problematic browsers are caching effectively old copies of these scripts.

However, to check the basics and ensure we’ve got the updated files (unlikely to be the problem as it’s picked up the function name change), please logon to your emoncms server and run (I assume you have a standard emonpi style install):

pi@emonpi(rw):~$ cd /var/www/emoncms/Modules/vis/visualisations
pi@emonpi(rw):visualisations$ cksum multigraph.php multigraph/multigraph.js
2891880849 3615 multigraph.php
2147837385 15232 multigraph/multigraph.js
pi@emonpi(rw):visualisations$
pi@emonpi(rw):visualisations$ grep -i multigraph.*init multigraph.php multigraph/multigraph.js
multigraph.php:            multigraphInit("#multigraph");
multigraph/multigraph.js:function multigraphInit(element) {
pi@emonpi(rw):visualisations$

And if all is well the checksums and the grep above will tally with yours.

Try opening an incognito tab in Chrome and this should ignore any cache and cookies you have. If this works, then it suggests your cache doesn’t think the server has a newer version, you could just clear your browser cache, but I’d also check the date and time for all the devices to ensure you don’t have something peculiar lurking.

I hope that fixes it for you.

I also get the “Synchronous XMLHttpRequest” and haven’t looked into it any further, but was thinking about asking Trystan and Glyn if it is worth considering updating a few of the underlying modules (jquery, flot …)

2 Likes