Need help? Check out our Support site, then


My blog is shutting down viewers computers!

  1. Hi,

    A couple of people have complained that their computers shut down when they open my blog. I just shifted from Blogger to WordPress one week ago. I'm still getting comments from a lot of other viewers so it's not a general problem. I was wondering whether there might be some bugs or malware that's doing this?

    Thanks
    Starry

    The blog I need help with is starsinmeyes.wordpress.com.

  2. Hello there,
    I just visited your blog linked to your username and experienced zero problems. I'm on a PC with windows XP and my browser is Firefox 3.5.5.

    In order to begin to fathom what's going on your friends will have to provide the following information:
    (1) What is their operating system?
    (2) Which browser and version of it they are using?
    (3) Are they on dial-up service or broadband?
    (4) Are they behind a proxy server?

  3. This isn't uncommon with imports from blogger. A brand new blogger blog, with no posts will have over 300 XHTML errors and over 60 warnings if you do a validation report on it. Sadly when you do an import from blogger, it brings in a whole bunch of errors typically. I just did a validation report on the blog linked to your username and there are 120 errors on your main page alone.

    http://validator.w3.org/check?uri=http%3A%2F%2Fstarsinmeyes.wordpress.com%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

    You can correct many of these errors, but it will take a little work. Go to settings > writing and select "WordPress should correct invalidly nested XHTML automatically" and click "save changes."

    Next start opening each of your posts in the post editor one by one, switch from the visual tab to the HTML tab and back again (waiting for the change to completely load prior to clicking the tab again), and then click "update post. WordPress should automatically correct any HTML issues in the posts and fix a good portion of the issues for you.

  4. @TSP
    Thanks for the intervention - bookmarked! :)

  5. Thanks a bunch, thesacredpath and timethief! It's error free now. This is amazing...it really worked! Thanks again:)

  6. Wow, that was quick and worked better than it does normally. Typically it will leave a few errors here and there that need to be corrected by hand. Perhaps wordpress made some adjustments to the editor stuff that made it a smarter.

    And you are very welcome. Keeping the setting at settings > writing selected should keep any other errors from creeping in on you in the future as well.

  7. Wow, I didn't know that about Blogger, or that this validator even existed. Having also ported over from Blogger originally, I decided to run it on my blog. I'm not sure if I'm interpreting the results correctly, but it looks like the validator hates at least one instance of the WP audio player, the WP search widget, and the BlogExplosion code I added in a text widget. Even if I am interpreting the results correctly, I have no idea what to do about the errors since they aren't referring to code I wrote.

    Any thoughts?

  8. The audio player, and videos will create apparent errors when you do a validation report, but they are not something we can do anything about. The other thing to remember is that the effects of one blogger introduced error can actually cascade down through the markup and create apparent errors in other parts of the page. I've worked on blogs where they had 50 errors being reported and after I fixed 5 things, all the errors had gone away.

    The code for the blog explosion is definitely broken. One thing is that it has border 0pt, and that is wrong, it should be border 0 . There is no need to put a unit when the value is 0. There are also a number of syntax errors and you had no closing "p" tags for the 4 different sections of code. Replace the code you have in that text widget with the following and it should straighten out a bunch of errors.

    <p style="text-align: center;"><a id="clustrMapsLink" href="http://www2.clustrmaps.com/counter/maps.php?url=http://iwanticewater.wordpress.com/"><img style="border: 0;" title="Locations of Visitors to this Blog" src="http://www2.clustrmaps.com/counter/index2.php?url=http://iwanticewater.wordpress.com/" alt="Locations of Visitors to this Blog" />
    </a></p>
    <p style="text-align: center;"><a href="http://www.blogexplosion.com/index.php?ref=IzaakMak"><img src="http://banners.blogexplosion.com/button1.gif" border="0" alt="" width="88" height="32" /></a></p>
    <p style="text-align: center;"><a title="Philosophy Blogs - Blog Catalog Blog Directory" href="http://www.blogcatalog.com/directory/philosophy"><img style="border: 0;" src="http://assets.blogcatalog.com/buttons/blogcatalog4.gif" alt="Philosophy Blogs - Blog Catalog Blog Directory" /></a></p>
    <p style="text-align: center;"><a title="counter for wordpress" href="http://www.statcounter.com/wordpress.org/" target="_blank"><img src="http://c.statcounter.com/4857659/0/aa2dc22e/0/" border="0" alt="counter for wordpress" /></a></p>
  9. Actually, use the following code. The above had the ending of one code snippet on a separate line which will produce an error.

    <p style="text-align: center;"><a id="clustrMapsLink" href="http://www2.clustrmaps.com/counter/maps.php?url=http://iwanticewater.wordpress.com/"><img style="border: 0;" title="Locations of Visitors to this Blog" src="http://www2.clustrmaps.com/counter/index2.php?url=http://iwanticewater.wordpress.com/" alt="Locations of Visitors to this Blog" /></a></p>
    <p style="text-align: center;"><a href="http://www.blogexplosion.com/index.php?ref=IzaakMak"><img src="http://banners.blogexplosion.com/button1.gif" border="0" alt="" width="88" height="32" /></a></p>
    <p style="text-align: center;"><a title="Philosophy Blogs - Blog Catalog Blog Directory" href="http://www.blogcatalog.com/directory/philosophy"><img style="border: 0;" src="http://assets.blogcatalog.com/buttons/blogcatalog4.gif" alt="Philosophy Blogs - Blog Catalog Blog Directory" /></a></p>
    <p style="text-align: center;"><a title="counter for wordpress" href="http://www.statcounter.com/wordpress.org/" target="_blank"><img src="http://c.statcounter.com/4857659/0/aa2dc22e/0/" border="0" alt="counter for wordpress" /></a></p>
  10. Thanks man! Oddly enough, your original code didn't give me an error but I fixed it anyway. I also added some display padding between the blocks - I swear it was there before without it!

    Now the only errors are from the search widget and audio player. As I've used the audio player the same way for many other posts, I can only assume that I'm getting the error only for this one post because that's all that shows on the start-up page.

  11. Yeah, the audio player errors and video errors as I mentioned cannot be corrected. The errors are in the flash code used in the wordpress backend. They aren't anything to be worried about.

    I've verified just now that the search widget issue is an actual issue with the search widget and what you will have to do is to send the information into staff so that they can fix it in the theme files.

  12. I was afraid you might say that. I can't say that I'm a fan of the "contact support" page, but I'll give it a go. Thanks.

  13. You don't really have to worry about it. I sent a report in on it just a little while ago in case you did not.

  14. I did already. But hey, maybe two reports are better than one?

  15. Most definitely more are better. Squeaky wheel and all that...

  16. I just got a reply from staff, and the "role" attribute is for accessibility and is not supported in XHTML 1.0, but is in the upcoming XHTML 1.1 specification. WordPress is getting a jump on the accessibility issues so this error will show up until 1.1 comes out of draft and the XHTML validator is updated to test for 1.1.

Topic Closed

This topic has been closed to new replies.

About this Topic