We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 19872
    • 1,078 Posts
    I've done a couple of updates before so not sure what's happening this time, but the setup screen is blank.

    I have merged the directories. Then copied the index.php and config.core.php from the MODx install folder out to the root. Still, the setup screen is blank. I did already have an ht.access file, which I had changed to be .htaccess. Thinking that was the issue, I renamed that file to temporarily take it out of play and had already copied the ht.access from the MODX install folder out to the root.

    Anyone have any tips or ideas as to why the setup has a blank screen?

    I was trying to get the host support to help me move some of the files out of the MODX install folder, but rather than help, they suggested I Google it, and/or just navigate to the Setup directory as it sat within the MODX folder. At which point he navigated to that directory with his browser and said the page is blank. Did he mess something up by trying to access it while it was still in the MODX-2.2.14-pl folder?

      • 19872
      • 1,078 Posts
      I found this troubleshooting tip, but I did not rename anything. And where are these located anyway. I have the blank white screen, but I don't think this is the issue.

      I did do that suggested patch on my 2.2.12 install. Could that be the issue?

      "I get a blank white screen instead of the options page!"
      You probably copied config.inc.tpl to config.inc.php, which is incorrect. Make the config.inc.php file an empty, writable file.

      If you renamed the config.inc.tpl to config.inc.php, rename it back to config.inc.tpl and create a blank file named config.inc.php that is writable.
        • 19872
        • 1,078 Posts
        My memory limit is 128M. PHP version is 5.3.3. The core/config/config.inc.php is there, so I did not accidentally delete it.

          • 28042 ☆ A M B ☆
          • 24,524 Posts
          First, did you back up your site before trying to upgrade?

          Did you upload the files via FTP/SFTP individually, or did you upload the zip archive, extract it on the server and move the files into place?

          Check a phpinfo() and see if allow_url_fopen is set to On. If it is, put the installer.php file from here in your site root and run it from the browser. This file automatically fetches the MODX zip file and extracts it in place, then redirects to the MODX setup.

          You'll need to edit it to download the 2.2.14 version instead of 2.2.13. Line 38 (for standard installation):
          	'revo2.2.14-pl' => array(
          		'tree' => 'Revolution',
          		'name' => 'MODX Revolution 2.2.14-pl Standard Traditional (04.04.2014)',
          	    'link' => 'http://modx.com/download/direct/modx-2.2.14-pl.zip',
          	    'location' =>'setup/index.php'
          	),


            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
            • 19872
            • 1,078 Posts
            Hi Susan: Thank you for responding in my hour of need.

            I did do backup.
            I uploaded a zip. Extracted on server with SSH. Merged directories with SSH (have done so 3 times in the recent past with the same commands—with update folder name for the MODx version of course)

            allow_url_fopen: Local value = OFF, Master value = OFF
              • 19872
              • 1,078 Posts
              If the support tech navigated to the setup/index.php while it was still in the MODX-2.2.14-pl folder, would that have messed something up. As I was chatting to him why I thought that didn't work and I needed his assistance moving it out into the domain, he mentioned that the page was blank.
                • 28042 ☆ A M B ☆
                • 24,524 Posts
                Hm. Should have worked then.

                No, trying to run the setup from the extracted folder won't do any damage to the MODX installation, it would just try to install in that location if it's in the web space somewhere so that it has PHP available.

                Check your PHP error logs to see if there's anything relevant there.
                  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
                  • 19872
                  • 1,078 Posts
                  With the setup folder. The tech support guy not being very friendly and did not seem willing to help me move the setup folder outside of the MODX-2.2.14-pl. At which point I ended my chat, and then using Fetch, I cloned the window and drug the folder out using fetch. Could that have cause some kind of permission error that is preventing the setup for displaying an info?

                  Problem is, I am not getting an error messages. Just a blank page. Nothing to go by.
                    • 19872
                    • 1,078 Posts
                    Yikes. OK. Here it comes. "How do I check the error logs?'

                    I'm on a Apache/2.2.3 (CentOS)
                      • 28042 ☆ A M B ☆
                      • 24,524 Posts
                      If you have CPanel, there should be an item for the logs.
                        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