Yeah, just noticed that... wonder what's causing that?
All of our avatars are screwed up, too.

    i think the moderators already notice this... hopefully they have some spare time to correct it...

    if jstarkey fall sleep, somebody please help us to PING this guy... lol 🙂

      well, now i know, phpbuilder don't ob_start()

      that's probably a good thing, ob_start() isn't the best thing to use
      in a large scale site like this

      its better to remove all output rather than output buffering

      but obviously something is wrong

        i think they do this

        error_reporting = E_ALL

        in this production and large complex site... 🙂

          tuf-web.co.uk

          u are a fast $postNum++ learner... 😃

            u are a fast $postNum++ learner...

            me too 🙂

            well, I think one should use output buffering like using GOTOs.
            Use it if needed, but avoid it.

              u are a fast $postNum++ learner... 😃

              errr, is that good?!

                errr, is that good?!

                well, is some way, otherwise, this would be a $postNum++ thread... 🙂 lol

                  you should be.......

                  anyway what jimson is saying is that he and apparently me only
                  post to get our post number up

                  on the other hand i do post and help large amounts of people

                  that is all he is saying

                    ahh i c now, just some more jargon language
                    oh well now i know incase i need to know later

                    and on the other hand, i dont not $Postnum++ 😛

                    well yet anyways 😉

                      stolzyboy / laserlight ... I'm just curious, why don't you recommend output buffering? I didn't really notice any major drawbacks to using it on php.net. I have recently started using output buffering on all sites that I create. Is that a bad idea?

                        this was from one of my previous posts

                        the only difference is that it forces to internally buffer the output instead of outputting the buffer, you will see no difference in speed or server overhead with a simple header redirect, or setting a cookie, and i have yet to see any difference when doing anything with that option regardless of what it is, glad i could help

                        however that was til a site i had grew to number and number of posts/request that sort of thing

                        it is a company intranet of 1000 peeps involving calendars/chats/message boards all that sort of thing and i relied on ob_start() until it grew enormously and they were using it

                        they called and asked why it was so slow, since its right on their network

                        i said hmmmmm......let me think

                        so i removed all ob_start()'s, then removed all output before header calls and voila it works like lightning

                        now keep in mind that this is hundreds of requests per minute and if you don't get into something that large you shouldn't have
                        a problem with ob_start()

                          okay .. thanks stolzyboy, I'll keep that in mind. Most of the sites I create are not that busy. 🙂

                            try saving a site page... if > 30 kb, may consider to turn off the ob_start()... imho

                              30K is squat and is irregardless compared to user activity, and you can have 300K if it isn't doing too much it won't matter

                              and you can have 30K doing a whole load of crab and have it kill your page

                              i wouldn't get hooked on a size as how you "think" your page will perform

                                IMHO... if
                                a.php = 30 kb
                                b.php = 300 kb

                                structure of a.php

                                +----------------+
|   (a)   10 kb  |
|----------------+
|  (b) |   (c)   |
|  8   |    22   |
|  kb  |    kb   |
|      |         |
+----------------+

                                structure of b.php

                                +----------------+
|   (a)   80 kb  |
|----------------+
|  (b) |   (c)   |
|  40  |   180   |
|  kb  |    kb   |
|      |         |
+----------------+

                                where a = header area
                                b = menu area
                                c = content area

                                if we ob_start() and don't flush it, user will see nothing untill the 300 kb is downloaded for the b.php and 30kb is downloaded for a.php
                                while... our main targets still the 56k peeps... if they can't see anything in the first few seconds... they will move from our sites.
                                they thought we are down... 🙁

                                so, IMHO.. size really matters.