We’ve had a similar problem with IE6 and IE7 - pages don’t display properly and buyers can’t get to the cart…

It seems to work when one of the default settings in IE is changed:

IE’s settings page // Advanced and turn off ‘Show Friendly HTML errors’

This is a BIG issue though as we can’t expect consumers to change these settings in order to purchase!

This happens randomly in IE6 & IE7 on older Showroom-based themes (note that current Showroom themes have a fix for IE).

You can fix it by replacing the following line in your shop.js
(please make a backup before you do this)

new Effect.Pulsate($('item-' + line_item.id).firstChild, { duration: 1.0, pulses: 3 });    

with this:

if($('item-'+line_item.id)) {
  new Effect.Pulsate($('item-' + line_item.id).firstChild, { duration: 1.0, pulses: 3 });    
}

Little Jacks problem is a different one, solved here:
http://forums.shopify.com/categories/7/posts/15135

Daniel: If that was the problem with thebrowncorporation.com (the IE PNG fix), do you have any idea why it isn’t happening on all pages? Every page loads and uses the PNG fix (for the navigation at the top of the page) and most pages load fine.

Additionally, if I remove the PNG fix, the problem still occurs.

(PS: I’m the developer of the site!)

— Last edited 08:58AM, Jun 17, 2008

Addendum: My second point seems to be incorrect, I had tested this before (after seeing the thread in question) and it didn’t have any effect. It does seem to fix the issue now, however.

Still, I’d be interested to hear a response to the first point—why isn’t it affecting all pages?

May it be that only this page (http://www.thebrowncorporation.com/products/bog-standard) has a transparent png?

The home page has one (an img embedded in the HTML) and the background image to the navigation (which appears on all pages) is a png … in fact, the page you’ve linked to (the one that fails) has as few transparent PNGs as any page.

I’ve changed the PNG fix to a javascript based one for now and it works OK, with no IE6 crash, but I’d be interested to try and discover why there were issues with that page….