If you can't get to the administration page, but have access to mysql, try the query "UPDATE xoops_config SET conf_value=1 WHERE conf_name = 'debug_mode'". Be sure to make sure "xoops_config" matches the name of the config table in your installation.

Bender wrote:
Quote:

If you can't get to the administration page, but have access to mysql, try the query "UPDATE xoops_config SET conf_value=1 WHERE conf_name = 'debug_mode'". Be sure to make sure "xoops_config" matches the name of the config table in your installation.

Not sure if i missed it but did you already try this on the site?

Any errors listed in the error.log of your server once you get a blank page?

skenow wrote:
One suggestions I have not seen you respond to - Have you verified ALL the files are in their proper folders? Files may have been missed or restored improperly by your host.

In addition to that, have you VERIFIED your physical path on the new host? Getting a XOOPS error page is a pretty good sign it is correct, but it doesn't hurt to check. Upload a new file to your root folder (call it test.php) that contains the following.

<?php phpinfo(); ?>

After you have done that, point your browser at that file - you should see a lot of information about your server. The last section is a list of PHP variables. Look for one called _SERVER["SCRIPT_FILENAME"], that will help you identify your physical path. Make sure your mainfile.php is correct.

Lastly, when you do log into phpmyadmin, what username and password are you using? Do they match what is in your mainfile.php?

skenow wrote:
Let's see if I can follow you -

1. This all started with moving to a new host and the error page says you have DB connection issue. No..... The sites have been moved since March. They were running fine until just before my first post

2. You can connect to your new site via FTP, cpanel and phpmyadmin YES

3. You have confirmed your XOOPS_DB_HOST, XOOPS_DB_NAME, XOOPS_DB_USER, XOOPS_DB_PASS, and XOOPS_DB_PREFIX in mainfile.php and they all correspond to your phpmyadmin db host, db name, username, password, and prefixes for your XOOPS tablesYES

4. You have confirmed your physical path for XOOPS_PATH (and it appears to be working because you get a XOOPS error page)YES

5. You have emptied out your cache folder and templates_c folder on your server and verified they have proper permissions setYES

6. Your PM said you were installing another site - can you access that site? Yes, visit Polen Family Reunion

skenow wrote:
At this point, I'd say you pretty much need to follow Biteronboard's advice - use phpmyadmin to backup your database; uninstall (delete) XOOPS from your host; upload XOOPS and modules, same versions as before; reinstall XOOPS and modules; restore data from backup.