Using Chrome on the blog also work but,
if you read my original post, http://forum.avast.com/index.php?topic=87371.msg702109#msg702109 you’ll notice that the problem
I mentioned pertains to the post that contains the actual story.
Click on read more and you’ll find out that it does not “load fine”. :frowning:

It loads fine for me but then you are using IE10 are you not. ???
This was posted with Chrome from my Windows 7 system.

Morning, :smiley:

It worked with me, however I reported it to our webguys. They will test it and make sure that error is fixed.

Thanks & best from foggy Prague

Our web guy Richard tried to duplicate this error on multiple versions of IE and also on multiple PC’s. Could you please give us more info? what version of IE you were running, what version of windows, which page he/she visits etc.

Thanks,

Julia,

I will assume you are asking about the OP. If this assumption is incorrect, please let me know.

The picture in the OP was taken from:

Windows Vista x32 Home Basic with SP2;
IE8;
1 GB RAM, which is also shared for video memory for the built in video (no additional memory card);
Avast Free (the exact Avast version was the latest stable version available at that time).

Other users reporting the same problem might be using different systems (read the topic).

The workaround (credit goes to Scott, in this same topic) is:

In IE8 → Internet Options → Security Tab → Restricted Sites → add the site:

https://connect.facebook.net

.

If you or Richard need more info or some additional test, please let us know.

i cross checked now here in my IE…no problem here :slight_smile:

He should upgrade to IE9 on Vista.

No problem reading the blog right now.

Thank you very much, I have submitted information to Richard. I will keep you posted! :slight_smile:

Julia,
If you’re talking about the problem I reported, it’s still there:


http://my.jetscreenshot.com/2701/m_20111216-atqn-72kb.jpg

I’m using the latest stable version of Google’s Chrome:


http://my.jetscreenshot.com/2701/m_20111216-3vp7-32kb.jpg

Bob3160,

I can normally go there with my Chrome Privacy Guard, no problems,

Damian

So am I on my XP Pro system and also my Windows 7 system.

YoKenny,
Apparently you still haven’t read or followed what I posted.
I never said that I couldn’t get to the blog.
Please re-read and follow what the actual problem is and then reply to it.
Thanks.

Guys

thanks for submitting all information. However our developers weren’t able to simulate the problem. We don’t see it in any browser :-\ We checked it on multiply PCs, with different users, but nothing appeared. thus they can not fix the error. ???

Best

Julia

@Julia,
I’m happy to report that even I can’t repeat the original problem. The only logical conclusion is that the
latest stable version of Chrome has eliminated what ever caused the original problem.
Tell the guys “Thanks for trying…” :slight_smile:

My report was with IE.

I’m not interested in keep testing this. No additional specific details were requested to find the source of the (noncritical for me) problem, and the workaround Scott recommended is still working. I may try deleting the added facebook exception some time in the future. Currently, I will live perfectly fine with the workaround, so the potential issue would / could be influencing some other blog readers.

Julia, thank you for communicating this to us, and thanks to Avast Team too for trying.