We're satisfied with our evaluation of XOOPS on our Linux test bench and are ready to put it on our production Windows 2003 Server. I've followed these two how-to's on site migration:
https://xoops.org/modules/smartfaq/faq.php?faqid=193
https://xoops.org/modules/smartfaq/faq.php?faqid=150

Step by step, I've followed them almost exactly. My problem is that when I try to load my site after migration to the new Windows server (http://localhost/learningspaces) I am presented with a blank white page, nothing more. I have outlined the steps I followed below and would appreciate any help anyone can provide:

1) I FTP'd the XOOPS folder from the Linux server (/home/httpd/html/learningspaces) to the Windows server (C:\Program Files\Apache Software Foundation\Apache 2.2\htdocs\learningspaces)

2) I exported/dumped the database to .SQL using phpMyAdmin on the Linux server. I FTP'd this over to the Windows server and imported it using bigdump, (as phpMyAdmin complained that the file was too large and bigdump took care of this). Importing was successful.

3) I modified the mainfile.php on the Windows server to reflect the correct physical path, URL and database connection details.

The root path changed:
define('XOOPS_ROOT_PATH', '/home/httpd/html/learningspaces');

became

define('XOOPS_ROOT_PATH', 'C:\Program Files\Apache Software Foundation\Apache 2.2\htdocs\learningspaces');

The virtual URL remained the same:
define('XOOPS_URL', 'http://localhost/learningspaces');

The database username changed. On the Linux server it was student, but on the Windows server it is root:
// Database Username
// Your database user account on the host
define('XOOPS_DB_USER', 'student');

became

// Database Username
// Your database user account on the host
define('XOOPS_DB_USER', 'student');

4) I set the cache and templates_c directories in C:\Program Files\Apache Software Foundation\Apache 2.2\htdocs\learningspaces in the security tab of Windows properties to 'full control' for all users listed.

5) http://localhost/learningspaces produces a blank white page =(


EDIT 05/10/07 11:27
-------------------
Enabled debugging mode for Xoops

From a cmd terminal on the WS2k3 server, log into the database
--> MySQL -u root -h localhost – p (using k@ml00ps2)
--> use learningspacesdb;
--> update xoops_config set conf_value=1 where conf_name='debug_mode';
(Query ok, 1 row affected) --> ok!

but I'm still getting a solid white blank page without any debugging details...

I've just migrated XOOPS installation from 2.09 on freeBsd (MySql 4.1.1) to WinXP local Dev server (apache mySql 5.X) and then to SUSE (MySql 4.X. again) ... on the way, I had to change the database Charset from Latin1 into hebrew_general_ci with utf8_unicode_ci = collation connection ... and in the end I had to upgrade the Instalation into XOOPS 2.2.4 full of hacks and Hebrew Special Additions.
some more on the way, was upgrading newBB 1 to CBB 3, mylinks into weblinks, News (some old version) into 1.44 and more ...

Sound BAD ... I though so too, but it took less then a day and site is on the air (god, how I hate the 2.1.X admin ... especially block admin)

How many White screen of death ?
well, at least 10 in the way ..... Luckily I already got Bald (too much sun and sea-water), otherwise That migration would have done the job

No. 1 cause of white screens for me was Permitions, then it was MySql versions difference, and teplate_c + cache folders has to be cleaned every migration).
Win permitions system is doing it for me time after time .... always problems with it somewhere ...

And If you dump MySql, export-import it @ gzip file - not .sql file it working the best even with 30 MB database ...

Use forward slashes in the paths.



I use the router's DHCP address for XOOPS_URL, but localhost should do. Are you running MySQL as root without a password? I know you can , but just wondered if you had overlooked the PW.

Did you FTP the PHP files across in ascii mode? (as they should be). Using binary can cause problems cross-platform.

Also check there is no trailing space at the end of mainfile.php after the closing PHP tag.

Quote:

^^^
A combination of those two did the trick!! =D Thank you so much, you've spared me an afternoon of headache! Perhaps you should add these tricks to the current FAQ article 'Why do I have a blank white page on my site?' located here (https://xoops.org/modules/smartfaq/faq.php?faqid=80) (and give yourself some credit!)

Thanks again!

UPDATE 05/10/07 @ 16:57
-----------------------
It seems that the issue was not related to binary/ascii files after-all. It was the beta version of FileZilla I had been using =/

After transferring everything over as ascii, all graphics / logos were corrupt and obfuscated. I transferred them over as binary with the beta 3 FileZilla and noticed that all the directories weren't going over. It was acting really flaky! So I downgraded to the less recent stable version 2.2.32 and everything began to work just jiffy-pop fine transferred as binary.

Thanks everyone for the help!