We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 16083
    • 28 Posts
    Well, it isn’t my server, so it will be up to my ISP (or I can relocate), but I will certainly ask them.

    I would imagine that that particular bug would manifest as a long pause followed by a blank page. I/we see a blank page almost immediately. Also, I would imagine that having turned off caching, no serialising is happening at all. Regardless, it is worth a shot, so thanks for that.
      • 17282
      • 283 Posts
      dunno if this is the same poblem .. but i sometimes get an unstyled page for a few seconds before the stylesheet kicks in .. anyway of fixing that ?

        Everytime you use Flash ... a puppy dies .....
        R.G Taylor
        • 4041
        • 788 Posts
        This is called FOUC... flash of unstyled content... I am assuming you are using this to add the stylesheet -

        <style type="text/css">
                     @import url('path/to/style.css');
                </style>


        try this instead

        <link href="path/to/style.css" rel="stylesheet" type="text/css">
          xforum
          http://frsbuilders.net (under construction) forum for evolution
          • 25497
          • 22 Posts
          Hi - I had set up a test site on a domain few weeks ago. No problems

          Just set up another test site on a temp ip location without a domain associated with it 66.216.120.27

          same hosting service only other variable in question:
          site with problem is running mysql 4.0 - but site without problem is running mysql 4.1


          when viewing a page in the manager, I see a blank preview screen - even when I installed modx with the generic/homepage template, and the generic home page of the site is also blank.


          under source I see:
          This document has not (yet) been cached.
            • 16083
            • 28 Posts
            Just to give a little more information, I installed 0.9.0 onto the same server and encountered *exactly* the same issues, so now I’m at a little bit of a loss. My hosting company are unsurprisingly unwilling to upgrade the version of PHP they are using so it will be difficult to test that theory without moving to another hosting company.
              • 16083
              • 28 Posts
              Okay, I got a new server hosting package using PHP 4.4.1 and the problems have gone away, so at least that’s my issue sorted, but I still feel as though there is an issue lurking somewhere. It could be down to anything, but maybe it was a server things all along.

              Anyway, it works, but is now replaced with another issue, but I’ll start a new thread for that smiley
                • 263
                • 52 Posts
                Hope this can be of help to somebody: after installing MODx locally (WinXP Home, WAMP5) I was getting similar problems to those in this thread. Tried all sorts of stuff: reinstalling everything, messed around with config files, ditched WAMP5 for XAMPP, went back to PHP 4.4.1 and pulled a lot of hair.... Then came across this:

                The Solution
                Find in your apache httpd conf file the following:

                #EnableSendfile off
                #EnableMMAP off

                Both should be commented out by the use of # which you will need to remove (they may even by "on" but you will need to have when finished:

                EnableSendfile off
                EnableMMAP off

                In my XAMPP version it wasn’t even there so I had to download apache and copy it out from there httpd conf file. It needs to be placed under the section
                "### Section 2: ’Main’ server configuration"

                Remember, you will need to save the file, shut down apache and restart it.

                You will also need to clear your entire internet cache and close it / open it back up again (all windows) to make this work.

                I tried this on my 2000, XP and a mates NT box, all which had the same problem. Now I can see any image size and it all works fine!

                in a post on the apache forum:
                http://www.apachefriends.org/f/viewtopic.php?p=29378&sid=ab46d057d01499244c63e9e8052ba490

                Now everything works perfectly. Aren’t computers wonderful?
                  • 17282
                  • 283 Posts
                  Quote from: breezer at Mar 04, 2006, 06:30 AM

                  This is called FOUC... flash of unstyled content... I am assuming you are using this to add the stylesheet -

                  <style type="text/css">
                               @import url('path/to/style.css');
                          </style>


                  try this instead

                  <link href="path/to/style.css" rel="stylesheet" type="text/css">


                  hey thnx smiley

                  i randomly use either method actually smiley

                    Everytime you use Flash ... a puppy dies .....
                    R.G Taylor
                    • 13577
                    • 302 Posts
                    Another clue to add to the mystery. This one is interesting.

                    I have a developing site running 0.9.1. (Sorry, it’s an intranet so I can’t *show* you!! Dang.) Anyway, it was rolling along smoothly with no blank page errors - until this morning. I added a bit of code to a snippet. The code was in essence:

                    ...
                    $schedArray = $srgss->makeTermScheduleArray($schedRaw);
                    print_r($schedArray);
                    ...


                    The print_r was merely a way for me to see the results of the the $srgss member function (which should return an array). The array got built as it should and displayed as it should with the print_r.

                    Knowing that the array was giving me what I expected it to, I removed the line "print_r($schedArray);" and WHAM! Blank screen. Refresh. No love. Oh no. Panic. Ulcers.

                    I checked my syntax about 238 times to be sure I wasn’t leaving out a semi-colon or something somewhere. I even added back in another line in place of the print_r function to give me SOME sort of output, but nada. So I did what any self respecting developer would do. I pouted. But when I was done with that, I figured maybe my makeTermScheduleArray function had a bug in it. Seemed unlikely since I had seen it give me my expected results. I checked. Nothing wrong. Looked good. I watched how long it took my blank page to load. It was fast (tho not instantaneous, so SOME sort of processing must be happening).

                    By the way, page not cached. Snippet not cached. But thinking about the cache I couldn’t help but think maybe something was wrong there... so I went to the cache folder and looked at siteCache.idx.php. I found my snippet in there along with all the others. Granted all snippets will show up there whether you use them cached or not. But then I got to wondering, what would happen if I didn’t use the siteCache.idx.php file?

                    I did a search for files that used this file and only found a few instances of it. A few in the install routine (which didn’t concern me at all), and one in the document parser. Looking at the document parser, I found that if there is NO siteCache.idx.php file, it will query the db for the information. So I could "live without" the file. So I renamed the siteCache.idx.php file OFFsiteCache.idx.php so it wouldn’t be found.

                    What do you know. No more blank page.

                    What is the problem? I have no idea. But I’m leaning more and more toward some glitch in the MODx cache routine.

                    More as it develops...

                      Standard Disclaimer
                      I could be totally wrong.
                      • 25663 MODX Staff
                      • 12,272 Posts
                      Interesting indeed. I’ve run into a similar problem on another server:

                      We had a snippet that did some basic DB queries and array manipulation, and made the page non-cachable. We called the snippet via [[. When the page ran, all sorts of bad connections and blank pages resulted.

                      The change we made to make it work was to set the page to be cacheable, and to call the snippet to be uncached. It’s very odd that that fixed the problem and we’re all scratching our heads.
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me

                      This discussion is closed to further replies. Keep calm and carry on.