Announcement

**lesliekirk** · 01-22-12, 07:00 AM

Re: Miva 4.24: Display inconsistency between Internet Explorer

May I ask why you are putting such effort into an MM4 site? Is there a specific module that you can't find for a MM5.5 store?

Leslie

**shooter56** · 01-22-12, 07:29 AM

Re: Miva 4.24: Display inconsistency between Internet Explorer

The store has about 15 or 20 modules installed and the client like to avoid paying to replace them all. Also, this issue notwithstanding, I'm more capable and experienced with MM4 than with 5.5, even though I have done a 5.5 site recently. And the client is already familiar and comfortable with the MM4 order processing interface. I understand the drawbacks, but they made the decision to stay with this version. So that's what I'm left working with.

**lesliekirk** · 01-22-12, 08:09 AM

Re: Miva 4.24: Display inconsistency between Internet Explorer

Understood - do check to see how many of those modules are no longer needed. I sure you have already mentioned MM4's end of life to them, along with the issues of of PCI Compliance and all that stuff.

**shooter56** · 01-22-12, 08:40 AM

Re: Miva 4.24: Display inconsistency between Internet Explorer

Yes to all. Do you have any ideas on the specific issues in my post?

**Bruce - PhosphorMedia** · 01-22-12, 11:20 AM

Re: Miva 4.24: Display inconsistency between Internet Explorer

The first problem is that there is no doctype. Without a doctype, you'll be forever chasing your tail with modern browsers AND you may solve a problem for you...but you'll have no idea how anyone else sees the site.

**RayYates** · 01-22-12, 09:32 PM

Re: Miva 4.24: Display inconsistency between Internet Explorer

Your 3 main content <td> tags are rendering a total of 175+620+192 = 987 pixels wide. Your site content is set to 960 pixels wide. This is freaking out IE.

After looking at the source script, I must say you are likely going to spend a LOT of time debugging IE in its various flavors because the site will render in IEs notorious quirksmode because of the lack of a doctype. PLUS the ugly html the MM4 spits out will make debugging difficult.

Merchant 4 will not allow you do add a <doctype> tag because the starting <HTML> tags is output directly by merchant.mvc. There is a trick to get around this but it involves renaming merchant.mvc and adding a new fake merchant.mvc to act as a front end.

If you do add a doctype something else will break because the site will render in a more "standard" way, and so you will have to debug those.

As for your 15-20 modules, just let me say I've done a lot of these conversions and that number will likely go down to less than 5, because there is so much more built in now.

**Bruce - PhosphorMedia** · 01-23-12, 09:41 AM

Re: Miva 4.24: Display inconsistency between Internet Explorer

...and you won't be rebuilding it a year from now in MM5. Not that you want to hear this, but we (and a number of other developers) will no longer build anything in MM4. Beside being an ultimate waste of money, there's some liability involved as you should know that its not PCI compliant. (Now, being one off, its highly unlikely that anything will become of this liability, but its out there.)

**shooter56** · 01-24-12, 01:33 PM

Re: Miva 4.24: Display inconsistency between Internet Explorer

Thanks to everyone for the replies. I'm happy to report that I have convinced the client to upgrade to 5.5, so this won't be an issue. Your feedback was much appreciated.

Announcement

Miva 4.24: Display inconsistency between Internet Explorer

Miva 4.24: Display inconsistency between Internet Explorer

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment