Weird error even with a skeleton

This corroborates DrByte http://www.selfseo.com/html_source_view.php as it also shows the same...

Now the question is.. why is our browsers not working... I'm going to pull the die() line now.

<?php
/**
 * Simple Category Tree
 * @Version: Beta 1
 * @Authour: yellow1912
 * @license http://www.zen-cart.com/license/2_0.txt GNU Public License V2.0
 */ 

class simple_categories_gen extends base {
    function simple_categories_gen() { } // die("help");}
    function init(){ } //die("me"); }
}
?> 

By the way, your "Quentin's Pick" image for "Calcana Infrared Heater" is 2.1 MB in size ... and takes FOREVER to load, even on hi-speed DSL.

But that's another issue.

This is what I see in FF2 right now

NOTE: Attachment removed

Because if I can't see it, then I can't use it, or test my changes... all I'll receive is a blank page like I am right now. Which is the reason all this started is that even without the debug code, I was getting a blank page.. so I reduced it down and I still see a blank page...

Now the problem is that 2 of us see a blank page, 1 doesn't... okay.. let me turn off the debug stuff and see what happens....

with that tool (http://www.selfseo.com/html_source_view.php) I see the raw html, I copied it into a file and THAT displays fine... but why doesn't the browser display it... I am sooooo confused.... :frusty::frusty::frusty::frusty::frusty:

Who cares, lol, install the class now, turn on the debug, and we can use that tool to get the debug code we need.
PM me when you are ready.

quentinjs:

with that tool (http://www.selfseo.com/html_source_view.php) I see the raw html, I copied it into a file and THAT displays fine... but why doesn't the browser display it... I am sooooo confused.... :frusty::frusty::frusty::frusty::frusty:

I have no idea. Perhaps it's something related to browser settings on your PC. Or maybe firewall/security software.

But, right now, for the sake of your customers and for search engines indexing your site, I suggest that you remove the various lines where you've set DEBUG_AUTOLOAD to 'true' so that nobody sees the notice.
And maybe also turn off STRICT_ERROR_REPORTING, for the same reason.

I can't help you sort out your browser issues.

If you've uploaded the "working" code for the mod, and the site is functional, then either the mod is working without throwing any errors, or else it's not firing at all. Perhaps Yellow can help further with that code ... being the author and all.

Thats okay for testing.... (will install it now)

but how many other people will see this stupid blank page... that is what concerns me.. as its only when I turn on that auto_loader, otherwise it woks fine....

quentinjs:

but how many other people will see this stupid blank page... that is what concerns me..Valid concern.
Hard to know for certain.
I'm not experiencing anything unexpected from this end.

quentinjs:

as its only when I turn on that auto_loader, otherwise it woks fine....
Definitely odd ... since the auto_loader output seemed to show fine for me.

DrByte, what I have is a stub that should work for any auto_load.. not just his... that it throws this bizarre problem when I turn it on and its okay when I turn it off... I know its related to the auto_loader even if its not actually the problem.

And DrByte, thank you VERY MUCH for trying to help... it doesn't help that it works fine for you... I just wish it would work for me as well....

Questions.

1. what OS are you using
2. have you installed anything special for IE or FF ?

quentinjs:

Questions.

1. what OS are you using
2. have you installed anything special for IE or FF ?

On this machine, Windows XP Pro, with all released updates, except IE7.
As for addons, just web developer tools, but those are all currently disabled.
Browser configuration settings are largely defaults ... I keep it as generic as possible specifically for the purpose of testing.

K, the machines I am using are Win 2K servers... alas my laptop died for the second time this week... currently trying to diagnose the new problem....

So I took the results from that tool for with auto-loader and without. and did a compare on it... now assuming I got any control characters that might be in the results... the difference is that I have 2 spaces preceding the <!DOCTYPE in the one with the auto-load turned on and when its not, its the first thing on the first line.

So why would there be additional characters before the doc_type only in the auto_load: on version?

quentinjs:

So why would there be additional characters before the doc_type only in the auto_load: on version?

Those would typically be from spaces at the beginning/end of the PHP files in question. ie: before the <?php or after the ?>

Um... that was the problem.... does that make ANY sense?
IF there are spaces before that DOCTYPE tag it freaks out. I deleted 1 space from each file and it worked....

oh, on the image.. thanks! I forgot to make it image_1a not image_1.... fixed it.

Um ... you still have STRICT_ERROR_REPORTING enabled, and you still have the DEBUG_AUTOLOAD enabled ... and that's being displayed to your customers.