> Finally got back to this one, seem to have the hang ups solved. You appear to have
> hit it on the head Pi, it was the loops. The foreach loop would run flawlessly on
> firefox, but IE7 had a shitfit when running foreach on large dirs over +5000 files..
> Changing that particular loop to a plain vannila for loop ending at the array size
> works in all browsers tried. Strange that IE7 would freak over one valid line of php
> like that depending on what was thrown at it.
I am glad that you were able to fix it, but how can it be a browser problem when PHP is a server-side script language? In other words, IE7 doesn't run a single PHP line. It only outputs the html or text that the PHP spits out. So, maybe the way the output is being sent to the browser (with frequent pauses, irregular block sizes, etc.) makes IE7 freak out. Maybe IE7 has a streaming or buffering problem. And that would be a really BAD problem, that is a basic area to have a bug there...
I'm also glad that I was able to help, I was running out of possibilities. Fixing a bug is easy, finding why a supposedly correct code has a bug, and where exactly is the tricky part. When I started spending more time debugging than writing code, I started SANE coding habits to avoid those stupid and unfindable bugs.
Wound up, can't sleep, can't do anything right, little honey / Oh, since I set my eyes on you. / I tell you the truth.
I can't get it right / Get it right / Since I met you...
|
Previous 
Index 
Next 
Flat 
Re: update....
Reply
