We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 25663 MODX Staff
    • 12,272 Posts
    Quote from: pixelchutes at Aug 03, 2009, 12:08 PM

    Quote from: rthrash at Aug 03, 2009, 11:58 AM

    php_flag zlib.output_compression Off
    


    Ryan, I had thought about this as well. Does anyone know what commit in the SVN could possibly lead to this behavior?

    No clue Mike.
      Ryan Thrash, MODX Co-Founder
      Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
      • 12028
      • 152 Posts
      Quote from: rthrash at Aug 03, 2009, 12:40 PM

      I suspect Suhosin is to blame there for that one Henrik.

      You are probably right - sorry if I thrown any confusion into this!
        - A small step for mankind, so why not take two...

        Working with web production, graphic design/workflow, photo and education - but are trying to get a life in between!
        • 19293
        • 4 Posts
        A value of 8192 is an invalid value for output_compression on my system, and results in zlib.output_compression automatically set to Off, which does fix the issue.

        My system setup is:
        Apache 2.2.11
        PHP 5.2.8
        zlib 1.2.3


        Quote from: garryn at Aug 03, 2009, 11:45 AM

        Aha, just tried a few things - it would seem the problem could be related to the buffer size being used when zlib compression enabled. Altering my .htaccess as follows seems to solve the issue for me:
        php_flag zlib.output_compression 8192

        Anyone wanna try this fix out? smiley
          • 27586
          • 31 Posts
          good morning!

          very strange. i just realized that i was still using the "old" .htaccess file from the latest modx version 0.9.6 with evolution. i replaced it with the new one to figure out if disabling zlib-compression on my ubuntu server would help. looged into the manager a few secs ago and have to say that its working now without any problems. how can that be? maybe we are all using the old -ghtaccess file instead of the new one?

          still checking why its working now.
            • 27586
            • 31 Posts
            i can confirm that using the new .htaccess file from evolution do the trick. it´s working now. ;-)
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              At some point between the versions those lines were commented out by default.

              You can also simply add a line to the .htaccess in the Manager
              php_flag zlib.output_compression Off

              and compression will still be available to the front-end, but turned off for the manager.

              However, all this still does not explain why it suddenly began to break things in the Manager.
                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
                • 25663 MODX Staff
                • 12,272 Posts
                Can you post the contents of both files, less all the crufty comments from the original 096x file?
                  Ryan Thrash, MODX Co-Founder
                  Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
                  • 10487 MODX Staff
                  • 1,535 Posts
                  Quote from: michaelcm at Aug 03, 2009, 08:50 PM
                  A value of 8192 is an invalid value for output_compression on my system, and results in zlib.output_compression automatically set to Off, which does fix the issue.
                  That’s odd, the PHP docs say that the zlib.output_compression can take either a boolean value or an integer, the integer being the desired buffer size. I couldn’t find anything to say that it would be invalid on different PHP versions, oh well!
                    Garry Nutting
                    Senior Developer
                    MODX, LLC

                    Email: [email protected]
                    Twitter: @garryn
                    Web: modx.com
                    • 28042 ☆ A M B ☆
                    • 24,524 Posts
                    My mistake; as far back as 095 those lines have been commented out by default. If somebody had an old .htaccess with them uncommented then somewhere along the line somebody must have uncommented them for that installation.

                    Unfortunately I’ve been pruning my svn versions as I upgrade from svn, or I’d go back through them until I found which was the last one I had where it worked. It definitely still worked in RC3, though.
                      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
                      • 25663 MODX Staff
                      • 12,272 Posts
                      They’ve been commented out since commit 987 on 13-Apr-2006.
                        Ryan Thrash, MODX Co-Founder
                        Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me