I made the update to avast 7 (directly from avast 6) a couple of hours ago. Everything is working fine. However, there seems to be a little glitch with the Firefox Webrep plugin. It says the plugin version is 6.0.1407, instead of 7.0.1407 (Firefox version 10.0.2). For IE9, it says correctly 7.0.1407.
I already rebooted twice since updating the program, there was no change. There doesn’t seem to be any actual issue with the plugin, it seems to be working correctly.
Is this supposed to be like this for Firefox or can this be somehow corrected? Thank you.
I have the same problem with chrome (18.0.1025.39) and it DOES effect my functionality. I just see a large black “X” where the webrep icon should be. Thanks in advance for all your help.
That has nothing to do with the actual number, but there are some reported problems with Chrome.
I have no idea if this is entirely depends on chrome version you are using, if you are using one of the bleeding edge versions of chrome and not the regular release version, then it may not be supported the webrep.
I don’t use chrome so I don’t know if the version you have is the regular update release version.
Thanks for the response. I have always used the beta version of Chrome and the webrep has always worked previously with the beta version. The problem only developed with this latest avast7 release.
I think the problem is with Chrome, no one can keep pace with their multiple update streams and I think avast just gave up trying (guess on my part) concentrating its resources on ensuring the webrep works with the regular release version.
I can back up bjstef8 on this one. The WebRep extension that came with Avast v6 worked fine on all versions of Chrome (stable, beta, dev, even the latest canary builds). Now that Avast v7 is installed, the extension just sits there with a gray X on it’s face.
The problem has to be Avast, since the only thing that changed between today and yesterday was the version of Avast.
same here, but my problem is the whole firefox browser are unable to connect internet, so I have to switch back to ie 9 for the time being in order to connect internet and report this issue.