We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 1266
    • 50 Posts
    I just put www.primaloft.com live after moving it from a testing server, but the Manager is exhibiting some really odd behavior. I’ve already run an upgrade install to see if that would fix anything, and it doesn’t seem to have.

    At first I would get partially blank pages in some instances:



    Then after my browser crashed, I’m seeing those pages that were previously blank, but now some of the tabs are missing:



    Either way, the Manager still doesn’t let me save changes to Chunks. Changes to Snippets, plugins and pages seems to stick. I can Duplicate/Cancel/Delete Chunks. But clicking Save does nothing.

    Any clues what might be going on? I’m on Modx 1.0.4.

    Edit: I should also point out that the Tools -> Configuration -> File Manager tab is missing…

    Edit 2: changed the subject to be more descriptive.
      • 22840
      • 1,572 Posts
      Just a guess but what do you have in the .htaccess file on the server ??

      Also try re uploading all files in the manager directory
        • 1266
        • 50 Posts
        hmm re-upping the manager directory didn’t seem to do anything. This is my .htaccess file:
        # For full documentation and other suggested options, please see
        # http://svn.modxcms.com/docs/display/MODx096/Friendly+URL+Solutions
        # including for unexpected logouts in multi-server/cloud environments
        # and especially for the first three commented out rules
        
        #php_flag register_globals Off
        #AddDefaultCharset utf-8
        #php_value date.timezone Europe/Moscow
        
        Options +FollowSymlinks
        RewriteEngine On
        RewriteBase /
        
        # Fix Apache internal dummy connections from breaking [(site_url)] cache
        RewriteCond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
        RewriteRule .* - [F,L]
        
        # Rewrite domain.com -> www.domain.com -- used with SEO Strict URLs plugin
        #RewriteCond %{HTTP_HOST} .
        #RewriteCond %{HTTP_HOST} !^www\.example\.com [NC]
        #RewriteRule (.*) http://www.example.com/$1 [R=301,L]
        
        # Exclude /assets and /manager directories from rewrite rules
        RewriteRule ^(manager|assets) - [L]
        
        # Friendly URLs
        RewriteEngine On
        RewriteBase /
        
        # Fix Apache internal dummy connections from breaking [(site_url)] cache
        RewriteCond %{HTTP_USER_AGENT} ^.*internal\ dummy\ connection.*$ [NC]
        RewriteRule .* - [F,L]
        
        # Exclude /assets and /manager directories from rewrite rules
        RewriteRule ^(manager|assets) - [L]
        
        # Redirect from mydomain.com/rootname to mydomain.com/rootname/
        RewriteRule ^en$ en/ [R=301,L]
        RewriteRule ^fr$ fr/ [R=301,L]
        RewriteRule ^de$ de/ [R=301,L]
        RewriteRule ^it$ it/ [R=301,L]
        RewriteRule ^uk$ uk/ [R=301,L]
        
        # The Friendly URLs part
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^uk/(.*)$ index.php?q=$1 [L,QSA]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^it/(.*)$ index.php?q=$1 [L,QSA]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^de/(.*)$ index.php?q=$1 [L,QSA]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^en/(.*)$ index.php?q=$1 [L,QSA]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^fr/(.*)$ index.php?q=$1 [L,QSA]
        RewriteCond %{REQUEST_FILENAME} !-f
        RewriteCond %{REQUEST_FILENAME} !-d
        RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]
        
        # Reduce server overhead by enabling output compression if supported.
        #php_flag zlib.output_compression On
        #php_value zlib.output_compression_level 5

          • 22840
          • 1,572 Posts
          Never seen a .htaccess file like that shocked

          Ok can you try something for me, the reason I want you to try this is because one of our hosts did a upgrade last week and it totally wrecked about 20 of our sites and it was all down to the htaccess file, worked fine one min then not the next ( must say none of the sites affected were MODx sites but we don’t alter their htaccess files ).

          Can you rename .htaccess to ht.access, clear your browser cache ( or even try another browser ) and then login to the manager and see if anything is fixed.

          Failing that can you post your server environment and where it’s actually hosted as there are a few hosts out there that have problems.
            • 4310
            • 2,310 Posts
            That’s a YAMS modified .htaccess file wink
              • 1266
              • 50 Posts
              Yeah, it’s pretty much the standard modx .htaccess plus the YAMS stuff. I’m wary of renaming it because I’m not sure what that’s going to do to the functionality of the site itself. undecided

              As for the server, we’re using Dreamhost -

              MySQL: 5.1.39
              PHP: PHP 5 CGI
              I’m pretty sure it’s a Linux machine, but Dreamhost seems to squirrel that info away in their web UI.

              Oh and the pages are going back to being partially blank…what’s weird is that it seems to effect certain levels of pages.

              Edit: here’s something else. If I disable ManagerManager, I can see those pages again, but _only_ the General tab. Not the settings etc. and all the multilingual tabs that should be there. I also realized the 1.0.4 upgrade upgraded a bunch of plugins. Could that have anything to do with it?
                • 19787
                • 28 Posts
                Have you checked your ManagerManager rules and settings?
                Sometimes after upgrading, it will switch the ManagerManager default config chunk back to mm_demo_rules chunk. Check in Plugins > ManagerManager > Configuration - and make sure your MM rules includes the YAMS rules (yams.mm_rules.inc)

                few other points that may be relevant
                1. I also had a very strange issue when moving a YAMS modified Modx site - odd empty pages. I never did find out what the issue was.
                2. I recently tried installing YAMS on a fresh Modx 1.0.4 but gave up - again, i could not work out what the issue was and reverted back to 1.0.3 version and it worked fine
                  • 1266
                  • 50 Posts
                  What would be the proper way of forcing ManagerManager to use the mm_rules.inc.php file? I do see that the upgrade deactivated old versions of the plugins. But I don’t see directories for those older plug-ins in my plugins folder? huh

                  Reverting to 1.0.3 might be the way to go. how did you go about that?

                  BTW, thanks everyone so far and in advance to anyone else who might have some clue as to what’s going on!
                    • 19787
                    • 28 Posts
                    Have a look at the section on ManagerManager Setup when installing YAMS

                    http://svn.modxcms.com/docs/display/ADDON/YAMS+Installation


                    basically you have to make sure that the YAMS rules are included by adding this code to your mm rules chunk

                    require( $modx->config['base_path'] . 'assets/modules/yams/yams.mm_rules.inc.php' );  
                    

                      • 1266
                      • 50 Posts
                      Right. I can’t save Chunks right now for some reason. I checked the permissions for the php files in the manager directory, and things look ok…

                      That’s why I was using the mm_rules.inc.php file for ManagerManager. I checked and the YAMS rule is there. Do I have to do anything to make ManagerManager use that file for rules, or does it do it automatically? That’s how I had it before, but for the life of me, I can’t figure out what I changed.

                      @mjm - how did you revert to 1.0.3 from 1.0.4?