We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 11526
    • 93 Posts
    I having the following problem:

    I am trying to get the PHP Layers Menu (http://phplayersmenu.sourceforge.net/) working with MODx as Ralph did on Etomite (http://www.etomite.com/browsesnippets.html?int_snipid=81&lst_category=2), but getting a strange error...

    When i open my site for the first time, and click on a submenu item, i am getting the following error:
    Warning: Cannot modify header information - headers already sent by (output started at /chroot/home/brigitte/brigittedebiolley.be/html/manager/includes/document.parser.class.inc.php:452) in /chroot/home/brigitte/brigittedebiolley.be/html/manager/includes/document.parser.class.inc.php on line 416
    
    « MODx Parse Error »
    MODx encountered the following error while attempting to parse the requested resource: 
    « PHP Parse Error » 
      
    PHP error debug 
      Error:  Cannot modify header information - headers already sent by (output started at /chroot/home/brigitte/brigittedebiolley.be/html/manager/includes/document.parser.class.inc.php:452)   
      Error type/ Nr.:  Warning - 2   
      File:  /chroot/home/brigitte/brigittedebiolley.be/html/manager/includes/document.parser.class.inc.php   
      Line:  416   
      Line 416 source:  header($header);    
      
    Parser timing 
      MySQL:  0.0233 s s (52 Requests) 
      PHP:  0.1286 s s   
      Total:  0.1520 s s   
    


    However, when i click again on the subitem, the error disappears and the menu is fully working...

    Think this is related to the problem mentioned above?
      • 11526
      • 93 Posts
      Having this error now on other sites... And they don’t use the PHPLM-snippet, so that can’t be the cause of this error...

      But now there are allready 3 sites of mine with this error, hoping on a solution...
        • 7923
        • 4,213 Posts
        Have you tried the temporary solution to disable the visitor logging? Works for me..


          "He can have a lollipop any time he wants to. That's what it means to be a programmer."
          • 11526
          • 93 Posts
          Quote from: doze at Apr 02, 2006, 12:40 PM

          Have you tried the temporary solution to disable the visitor logging? Works for me..

          Yes indeed, that fixed the error...
            • 29635
            • 361 Posts
            Hi all.
            This error just showed up all of the sudden on a totally separate site. Disabling the visitor stats fixed it. Thanks for that fix!

            Thought I’d add this comment in case it seemed interesting to anybody else that it would be fine for months (six, maybe?) and then just show up out of the blue one day with no changes to the site or server.

            Also, not sure if anybody else gets this on their sites, but when I have visitor loggin on, I get this string of errors from the manager (you know, when you log in and it shows you the stats, that section gives these errors instead of the stats):
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 110
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 117
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 124
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 132
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 139
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 146
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 155
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 162
            
            Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/domains/complexdrive.com/web/manager/actions/static/welcome.static.action.php on line 169
            This table shows some visitor statistics for your site. For more detailed information, please visit the `Visitor Stats` page.


            Hopefully that helps further diagnose the issue.
            -Brett
              Need MODx Ecommerce? Try FoxyCart!
              • 11413
              • 203 Posts
              This is exactly the bug I have too... Is there a real fix yet?? I release my website to the public soon and want to get rid of it before "The Day" wink
                Blaise Bernier

                www.medialdesign.com - Solutions for small business, hosting, design and more!
                • 22303 MODX Staff
                • 10,725 Posts
                Quote from: grunt_lord at Apr 06, 2006, 09:41 PM

                This is exactly the bug I have too... Is there a real fix yet?? I release my website to the public soon and want to get rid of it before "The Day" wink
                IMO, the "real" fix will be to remove MODx native logging altogether. It just plain s*cks, and I personally never use it, because of errors like this, issues with decreasing performance as log table sizes increase, and having to manually clean the db tables every week or two. There are 3rd-party statistics alternatives to using the native stat features that improve both performance and will avoid this problem, and the plan for 1.0 is to replace the current audit logging portion of this with a configurable native logging system that can send output to wherever you want it to (DB, apache logs, text files, XML files, etc.). See Jeff Whitfield’s (Bravado) blog post on Integrating Mint with MODx for some alternative approaches regarding logging visitor statistics.
                  • 11413
                  • 203 Posts
                  How to remove it?? I don’t have webusers on my website anyway
                    Blaise Bernier

                    www.medialdesign.com - Solutions for small business, hosting, design and more!
                    • 7923
                    • 4,213 Posts
                    Quote from: grunt_lord at Apr 07, 2006, 04:05 PM

                    How to remove it?? I don’t have webusers on my website anyway
                    In manager: Administration > System configuration > Log visits > No


                      "He can have a lollipop any time he wants to. That's what it means to be a programmer."
                      • 22303 MODX Staff
                      • 10,725 Posts
                      Quote from: grunt_lord at Apr 07, 2006, 04:05 PM

                      How to remove it?? I don’t have webusers on my website anyway
                      Nothing to do with web users grunt_lord; this is plain old visitor stats tracking that is causing the problem, which, as doze pointed out, is easy to turn off. And! It was already a LOT of fun to rip it out of the MODx 1.0 core code that is in development...so maybe we’ll rip it out for the coming release. I need more FUN in my life! (ugh, I’m such a geek)
                      grin