![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
Feedjit not working in Firefox 31
Hi, I am a forum owner and we use the Feedjit live traffic feed. everything has been fine until one of my admin computers auto-updated to Firefox 31. From then on the Feedjit widget is not showing on the site, (it is still visible from my other pc which has Firefox 30 installed) Further, any visitors that we get to the site that are using Firefox 31 do not appear in the site traffic listing. This is obviously causing inaccuracies in our site traffic statistics.
Clearly we can't expect everyone who visits our site to revert to an earlier version of Firefox so that our traffic stats work. We have tried all manner of procedures to try to combat this problem including, but not limited to, clearing the cache, clearing all browsing history, rebooting the pc. My site is displayed perfectly in other browsers, including IE11, Opera, Google Chrome and slim browser. And also like I mentioned, in Firefox pre version 31. (we have version 30 and listed in the live feed is version 28 and 26 today that have listed ok) But nothing from version 31.
Are there any tweaks that you can make to Firefox 31 to solve this problem? as quite obviously, just altering my admin machines would just make the Feedjit work for my own machines, it still wouldn't solve the problem of Firefox 31 not being detected by the feedjit system on any guest or member who visited my site.
My site is: http://learn4free.org.uk/
Thank you in advance for any information that you may be able to supply regarding this problem.
Semua Balasan (3)
I looked into this last week and did not see a solution.
Mysteriously, if you disable Flash, the feed does work, so it could be something about the way the Feedjit script uses Flash that is no longer working in Firefox 31.
I submitted a comment to Feedjit last Thursday night, but haven't heard anything back yet. You might want to try contacting them and pointing them to this thread to see if that helps speed things up.
Earlier thread: Why doesn't the Feedjit widget work in FF 31.0
Thanks for getting back so quick. I have contacted Feedjit yesterday but as of this morning they haven't got back to me. Your suggestion to disable flash is welcomed, however is of no practical use unless I have the ability to disable flash on every other persons computer who visits my site.
This is because it is not only, not showing the live feed in Firefox31, but it is not picking up any visitors to the site who are using Firefox 31 either! Effectively rendering them 'Invisible' to the statistics.
Whilst disabling flash on my own computer would enable me to view the live traffic feed, it would not display any visitor who was using Firefox 31, unless of course they had disabled flash also.
In the meantime, although I have contacted Feedjit about the problem and am awaiting a response from them, I feel that the problem does lie with Firefox, rather than with Feedjit. This is because of the fact that the Feedjit live traffic feed works perfectly in all other browsers tested so far, and even works in the previous versions of Firefox, Firefox 30 and before!
Therefore something that the coders have done in Firefox 31 has altered it's compatibility with a widely used service used by many webmasters.
If as you suggest, that it may be something to do with the way flash is handled in Firefox 31 ? Then surely Mozilla should be taking steps to address the issue? rather than expecting other companies to change their coding just so that it is compatible with a new version of Firefox, (especially when their code is working perfectly in all other browsers)
Surely, on this occasion it's Mozilla who has got it wrong?
Hopefully Mozilla will be able to address this issue and bring out a patch for their Firefox browser? In the meantime any further suggestions would be most welcomed.
I didn't suggest disabling Flash, just noted the difference.
Feedjit's script is too hard for me to figure out -- of course, I'm not a programmer -- so hopefully the company will figure out where the problem lies and either report it to Mozilla or change the script.