We’ve recently installed and developed a full Web site in MOD-X on our host provider, easycgi.com. Everything was working ok until they did their recent migration to a new server. Now it’s a blank screen...Their tech support refuses to help, saying that this is a "3rd party application" and so the responsibility falls back on us or the application creator...
I’ve reviewed the "How to move to a new server" page on this site, but honestly, not sure how to convert/modify the info on there to our situation. Is there an easier way for such situations to adjust certain file configurations or settings so they point to new database and other folder paths as a result of a migration? At this point we can only access the original app and db files through the host’s "control panel" and FTP. We can’t bring up either the MOD-X site or the MOD-X manager.
Here are the specs on the post-migration, current hosting settings (not much different from what it was before the migration):
Win 2003 server enterprises
MySql 5.0.45
Perl 5.8.8
PHP 4.4.7
thanks in advance...
Make sure that paths are correct. The easiest way to resolve this is to run the installer in upgrade mode (be sure not to install the demo site since it will erase your site, it is a good idea to do a database backup first just in case).
Thanks for the reply - I tried do a reinstall using the upgrade option (doing all backups of course). This option seems to just take whatever settings was in the original config.inc.php file. In the end, I get the same result - still can’t get to either the modx site or the manager (a blank screen for both w/ no page source code on those pages).
I’ve verified that the database connection info is correct and working.
Are the config.inc.php globals or path variables defined in the database, or are there certain files in the modx install I can manually alter to change these paths? I’m still at a loss on what caused this problem.
Quote from: buzzsaw at Nov 17, 2008, 12:22 PM
Thanks for the reply - I tried do a reinstall using the upgrade option (doing all backups of course). This option seems to just take whatever settings was in the original config.inc.php file. In the end, I get the same result - still can’t get to either the modx site or the manager (a blank screen for both w/ no page source code on those pages).
I’ve verified that the database connection info is correct and working.
Are the config.inc.php globals or path variables defined in the database, or are there certain files in the modx install I can manually alter to change these paths? I’m still at a loss on what caused this problem.
Pretty much all the settable settings are in config.inc.php. If you need to manually change things, that’s the place to do it. Clear your browser cache and cookies regularly when testing, just so you know that’s not an issue.
If the settings in config.inc.php are correct and you do an upgrade install and still have trouble, there’s a good chance that one or more files were corrupted in the FTP transfer to the new site (it’s more common than it should be).
MODx is pretty good about giving you *something* on the screen no matter what the error is, so a blank screen for both site and manager makes corrupted files even more likely unless the hosting service has a fairly unusual setup.
Hope this helps.
Thanks for the suggestion. I tried re-FTPing the files twice, with no change (still blank pages). I then installed modx in a separate folder as a new install, and not only was able to get that site up, but point to the old modx database and make the old modx site work again (w/ a different folder name). Very thankful for that.
Now the big problem I’m having is that I seemed to have lost the ability to view Chinese Unicode characters correctly in the Manager interface, which was installed and set to have UTF-8 Unicode as its character code (as it was before). They show as garbage characters almost everywhere - page headings, titles, document content window, chunk editors, template editors, etc. Interestingly, they show up fine on the template variable boxes on Web pages, and on the published pages or page previews in and out of the Manager.
Is this a database problem? Or a setting issue somewhere in ModX?
