We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 28042 ☆ A M B ☆
    • 24,524 Posts
    File and directory permissions is about the only other thing I can think of. Oh, check the individual user’s configuration (the User tab) and make sure he’s got the correct settings as well; the fields should be empty, and the "use system defaults" boxes should be checked.
      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
      • 5372
      • 6 Posts
      I followed the upgrade instructions and can’t get to a login screen like it did with 0.9.6.3 I get the following screen instead

      Warning: fopen(/homepages/31/d2ERASED BY ME/htdocs/manager/media/style/MODxCarbon/login.html) [function.fopen]: failed to open stream: No such file or directory in /homepages/31/dERASED BY ME/htdocs/manager/includes/accesscontrol.inc.php on line 129

      Warning: filesize() [function.filesize]: Stat failed for /homepages/31/ERASED BY ME/htdocs/manager/media/style/MODxCarbon/login.html (errno=2 - No such file or directory) in /homepages/31/ERASED BY ME/htdocs/manager/includes/accesscontrol.inc.php on line 130

      Warning: fread(): supplied argument is not a valid stream resource in /homepages/31/ERASED BY ME/htdocs/manager/includes/accesscontrol.inc.php on line 130

      Warning: fclose(): supplied argument is not a valid stream resource in /homepages/31/ERASED BY ME/htdocs/manager/includes/accesscontrol.inc.php on line 131


      I’ve tried a clean install, a dif database. Same results, 7 tries. HELP! PLEASE?!
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        This is a clean new install? Because the login.html and a couple of other frequently customized files are now in assets/templates/manager, not in manager/media/style/<whatever style>/.
          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
          • 5372
          • 6 Posts
          Yes. Clean install.
            • 5372
            • 6 Posts
            I’m going to just re-install 0.9.6.3. I haven’t been able to turn the global settings off. There’s a php.ini file that I was told to create and upload. Not sure if I did this correct. Yes total newbie but I’m trying hard! grin

            I looked into the htaccess and found the following: # MODx supports Friendly URLs via this .htaccess file. You must serve web
            # pages via Apache with mod_rewrite to use this functionality, and you must
            # change the file name from ht.access to .htaccess.
            #
            # Make sure RewriteBase points to the directory where you installed MODx.
            # E.g., "/modx" if your installation is in a "modx" subdirectory. If you have
            # problems with your .htaccess working at all, try un-commenting the first
            # line above the "RewriteEngine On" directive.
            #
            # You may choose to make your URLs non-case-sensitive by adding a NC directive
            # to your rule: RewriteRule ^(.*)$ index.php?q=$1 [L,QSA,NC]

            #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 www.domain.com -> domain.com -- used with SEO Strict URLs plugin
            #RewriteCond %{HTTP_HOST} .
            #RewriteCond %{HTTP_HOST} !^example-domain-please-change\.com [NC]
            #RewriteRule (.*) http://example-domain-please-change.com/$1 [R=301,L]
            #
            # or for the opposite domain.com -> www.domain.com use the following
            # >>> DO NOT USE BOTH THE ABOVE AND BELOW <<<
            #
            #RewriteCond %{HTTP_HOST} .
            #RewriteCond %{HTTP_HOST} !^www\.example-domain-please-change\.com [NC]
            #RewriteRule (.*) http://www.example-domain-please-change.com/$1 [R=301,L]



            # Rewrite secure requests properly to prevent SSL cert warnings, e.g. prevent
            # https://www.domain.com when your cert only allows https://secure.domain.com
            #RewriteCond %{SERVER_PORT} !^443
            #RewriteRule (.*) https://example-domain-please-change.com.com/$1 [R=301,L]



            # The Friendly URLs part
            RewriteCond %{REQUEST_FILENAME} !-f
            RewriteCond %{REQUEST_FILENAME} !-d
            RewriteRule ^(.*)$ index.php?q=$1 [L,QSA]



            # Make sure .htc files are served with the proper MIME type, which is critical # for XP SP2. Un-comment if your host allows htaccess MIME type overrides.

            #AddType text/x-component .htc



            # If your server is not already configured as such, the following directive
            # should be uncommented in order to set PHP’s register_globals option to OFF.
            # This closes a major security hole that is abused by most XSS (cross-site
            # scripting) attacks. For more information: http://php.net/register_globals
            #
            # To verify that this option has been set to OFF, open the Manager and choose
            # Reports -> System Info and then click the phpinfo() link. Do a Find on Page
            # for "register_globals". The Local Value should be OFF. If the Master Value
            # is OFF then you do not need this directive here.
            #
            # IF REGISTER_GLOBALS DIRECTIVE CAUSES 500 INTERNAL SERVER ERRORS :
            #
            # Your server does not allow PHP directives to be set via .htaccess. In that
            # case you must make this change in your php.ini file instead. If you are
            # using a commercial web host, contact the administrators for assistance in
            # doing this. Not all servers allow local php.ini files, and they should
            # include all PHP configurations (not just this one), or you will effectively
            # reset everything to PHP defaults. Consult www.php.net for more detailed
            # information about setting PHP directives.

            #php_flag register_globals Off



            # For servers that support output compression, you should pick up a bit of
            # speed but un-commenting the following lines.

            #php_flag zlib.output_compression On
            #php_value zlib.output_compression_level 5



            # The following directives stop screen flicker in IE on CSS rollovers. If
            # needed, un-comment the following rules. When they’re in place, you may have
            # to do a force-refresh in order to see changes in your designs.

            #ExpiresActive On
            #ExpiresByType image/gif A2592000
            #ExpiresByType image/jpeg A2592000
            #ExpiresByType image/png A2592000
            #BrowserMatch "MSIE" brokenvary=1
            #BrowserMatch "Mozilla/4.[0-9]{2}" brokenvary=1
            #BrowserMatch "Opera" !brokenvary
            #SetEnvIf brokenvary 1 force-no-vary


            What exactly is this and what should I be doing with it?
              • 28042 ☆ A M B ☆
              • 24,524 Posts
              Rename (or copy) that file to .htaccess; also the one in the /manager directory. Then you can uncomment (remove the # at the beginning of the line) of whatever lines you think you need. Test your site with every change. If you get a 500 error on your site, put the # back in front of the line.
                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
                • 5372
                • 6 Posts
                Thank you. Greatly appreciate it. Last question for today:

                Register_Globals is off: FAILED!

                I found a post on this before not sure what I did. Whatever it was it didn’t fix it.
                  • 3604
                  • 13 Posts
                  Quote from: cjsn3003 at Aug 20, 2009, 11:33 AM

                  Thank you. Greatly appreciate it. Last question for today:

                  Register_Globals is off: FAILED!

                  I found a post on this before not sure what I did. Whatever it was it didn’t fix it.

                  Did you channge the example domain to your domain?
                    • 5372
                    • 6 Posts
                    No. Exactly what will changing that do?

                    I’m lost obviously
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                      If all you’re trying to do is turn register_globals off, then editing the domain names in the other directives isn’t an issue. All you needed to do was remove the # at the beginning of the line
                      #php_flag register_globals Off

                      If it doesn’t work, that means that your server won’t let you make those changes to the PHP configuration from here.

                      What bloodstarstudios was referring to is the lines like this one
                      #RewriteRule (.*) http://example-domain-please-change.com/$1 [R=301,L]

                      where you need to change that example-doman-please-change.com part to match your actual domain; for example I would have
                      #RewriteRule (.*) http://sottwell.com/$1 [R=301,L]

                      But as long as you’re not using those lines (removing the # from the beginning) you can ignore them.
                        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