We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 40427
    • 16 Posts
    I'm experiencing a strange problem. I'm using the sticky footer from cssstickyfooter.com, and it's not liking one character of my code. I can save ALL of the CSS in my css document minus one single character.
    @charset "utf-8";
    
    html, body {
    height: 100%;
    }
    
    #wrap {
    min-height: 100%;
    }
    
    #main {
    overflow:aut;
    padding-bottom: 180px;
    }
    
    #footer {
    position: relative;
    margin-top: -180px;
    height: 180px;
    clear:both;
    }
    
    body:before {
    content:"";
    height:100%;
    float:left;
    width:0;
    margin-top:-32767px;
    }


    See how I have the overflow:aut; in my main id? I can make as many changes as I want to and it'll save almost instantly, but when I go and put the "o" in there to make it say overflow:auto;, it gets caught in a saving loop where the bar continuously keeps repeating itself and never saving the page. This is a fresh install (1 hour old) on a GreenGeeks server that supports the latest of everything I need. I'm using FireFox to code. Any ideas?
      • 3749
      • 24,544 Posts
      It sounds like a mod_security issue.

        Did I help you? Buy me a beer
        Get my Book: MODX:The Official Guide
        MODX info for everyone: http://bobsguides.com/modx.html
        My MODX Extras
        Bob's Guides is now hosted at A2 MODX Hosting
        • 40427
        • 16 Posts
        OK, then how do I fix this?
          • 3749
          • 24,544 Posts
          It usually means getting your host to disable a particular modx_security rule, or disabling it yourself if that's possible.


          http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me
            Did I help you? Buy me a beer
            Get my Book: MODX:The Official Guide
            MODX info for everyone: http://bobsguides.com/modx.html
            My MODX Extras
            Bob's Guides is now hosted at A2 MODX Hosting
            • 40427
            • 16 Posts
            The very first solution caused this message:
            Internal Server Error

            The server encountered an internal error or misconfiguration and was unable to complete your request.

            Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

            More information about this error may be available in the server error log.

            Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

            So what do I need to do?
              • 3749
              • 24,544 Posts
              That probably means you can't fix it yourself and will have to talk to the host.
                Did I help you? Buy me a beer
                Get my Book: MODX:The Official Guide
                MODX info for everyone: http://bobsguides.com/modx.html
                My MODX Extras
                Bob's Guides is now hosted at A2 MODX Hosting
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                You might be able to work around this by using a bogus snippet in between the aut and the o. MODx will just ignore it since the snippet doesn't exist, thus generating overflow:auto for the page, but the mod_security that doesn't like saving a form with the word "auto" in it will save the whole thing happily enough.

                overflow:aut[[nothing]]0;


                  Studying MODX in the desert - http://sottwell.com
                  Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                  Join the Slack Community - http://modx.org
                  • 40427
                  • 16 Posts
                  OK, I haven't done anything new to try and fix this problem except contact my hosting provider, but when I go to log in now, it shows my dashboard and all, but it adds these lines above the page:
                  Warning: MagpieRSS: Failed to parse RSS file. (xml declaration not at start of external entity at line 1, column 1) in /home/joneslea/public_html/core/model/modx/xmlrss/rssfetch.class.php on line 237

                  Warning: array_keys() expects parameter 1 to be array, null given in /home/joneslea/public_html/manager/controllers/default/dashboard/widget.modx-news.php on line 28

                  Warning: Invalid argument supplied for foreach() in /home/joneslea/public_html/manager/controllers/default/dashboard/widget.modx-news.php on line 28

                  Warning: MagpieRSS: Failed to parse RSS file. (xml declaration not at start of external entity at line 1, column 1) in /home/joneslea/public_html/core/model/modx/xmlrss/rssfetch.class.php on line 237

                  Warning: array_keys() expects parameter 1 to be array, null given in /home/joneslea/public_html/manager/controllers/default/dashboard/widget.modx-security.php on line 25

                  Warning: Invalid argument supplied for foreach() in /home/joneslea/public_html/manager/controllers/default/dashboard/widget.modx-security.php on line 25

                  Any idea what all this means?
                    • 28042 ☆ A M B ☆
                    • 24,524 Posts
                    I think the feeds are down; I'm not getting any errors, the feeds just aren't showing up at all in the Dashboard. A local install of Evo is showing the feeds are all down.
                      Studying MODX in the desert - http://sottwell.com
                      Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
                      Join the Slack Community - http://modx.org
                      • 6038
                      • 228 Posts
                      I've had the same editing issue before, and it was also mod_pain_in_the_a$$, sorry i meant mod_security

                      Feeds are down here too - probably should turn off php errors if not a dev site
                      (in your .htaccess: php_flag display_errors off)