JWN: browser problem solved

Around 24 hours ago, both Internet Explorer and AOL started rendering the code for JWN in a very lame, primitive way.
I’m terrifically sorry if you were one of the readers affected.
In response to an appeal here, gallant reader Dan Z. leaped to my assistance and sent me a fix he thought would work.
But I’d been busting my own rear end meanwhile on finding a fix, and about an hour ago I found one.
So thanks, Dan– and sorry, the rest of you. I’ll try to make sure it doesn’t happen again…
In the meantime, I’ve learned more about Cascading Style Sheets, positionizing text, the particular frailties of Internet Explorer, etc., etc. than I ever really wanted to know.
Back to the big picture, eh?

6 thoughts on “JWN: browser problem solved”

  1. Your editor is adding extra line breaks that IE has trouble parsing. That will fix it.
    If you need help spotting in which places it’s crucial, let me know. Everything else seems to work. It’s just a few lines with your href’s and type’s at the top of the code.
    Let me know if you need more help.
    ciao,
    Dan Z.

  2. Your editor is adding extra line breaks that IE has trouble parsing. That will fix it.
    If you need help spotting in which places it’s crucial, let me know. Everything else seems to work. It’s just a few lines with your href’s and type’s at the top of the code.
    Let me know if you need more help.
    ciao,
    Dan Z.

  3. What was the fix? I’m very curious. I have a suspicion it is what ever was rendering the page server side. The more I thought about it, the line breaks had to get there somehow and I didn’t know enough about movable type to troubleshoot that (besides not having access to the server). I used to manage webhosting servers/sites. for a large ISP in america, so my suspicion is the perl script from MT. There are still some problems on the page tho, and I still think something is rendering the pages with misc line breaks or not calling scripts correctly.
    ciao

  4. Dan, you might be so sophisticated that u wdn’t recognize what I did as a “fix”. But what I did worked for me, so for my purposes it was a fix…
    I reinstalled the archived copy of the Main Index template that I had from mid-December, then carefully inserted the blocks of new HTML I’d been trying to insert into it since then (the new links; taking out an earlier link: that was about it). I made sure that every aspect of the new HTML conformed to the formating of the old, mid-dec HTML, saved it, rebuilt the site, and bingo–
    I wish I’d thought of that 23 hrs earlier, ‘stead of busting my gut… So I still don’t know exactly where the prob is. Along the way I ran an HTML validator called somethng like CSE Lite on the M.I. template HTML and it found zillions of errors, but most of them rising from MT’s own special tags…

Comments are closed.