I am having trouble installing 9.x

I was able to install it just fine on my home computer running (Knoppix) Debian and XAMPP, but when I attempt to install it on my ISP's server, it spits out strange garbled text (for lack of a better term). If you try with IE, it attempts to save a file.

//edit - removed the links

My ISP's support suggested that I check to see if any strange headers are being set, but I haven't noticed any.

Hopefully noone else has had this problem, but hopefully someone know what I need to do to remedy it. CPG-NUKE looks promising, but only if I can get it installed.

thanks in advance

did you edit config.php by Notepad?

Yes, well, no, not with Notepad.

I untar'ed directly on the server and edited config.php with VI.

Also, followed all of the install/chmod instructions, etc. Failure is occuring when I try to load install.php in the browser.

very odd indeed... I would assume you have tried the old trash and re-upload? and maybe redownload the package... Possibilities of file corruption?

its really a UTF-8 Problem.

OK, I am somewhat code retarded... what is this UTF-8 I hear so much about, and why is it being such a problem?

Yes, I tried deleting everything and trying again with a fresh install a few times. I even tried v8.2c, which also failed, but a little further down the line.
I would say it looks like an encoding issue, but I don't know what UTF-8 is either.
Is there something else I should be reading and can also show to the ISP to have them make the necessary changes?

thanks.

Perhaps the problem is arising on your server in the untar process - I assume the tarball was okay to start with.

Have you tried extracting to your PC and uploading via ftp?

thanks, phoenix. I tried re-extracting the tarball I used to test install on my home Debian machine where the install worked, and then put the files up on my ISP's server. but I continue to get the same results; the garbled text, or is it encoding?

If I, for example, change the dbpasswd in config to something incorrect, I do get the error page to display properly.

I guess I will keep trying to isolate at what point it is failing as well as investigate for unusual headers being sent or anything else out of the ordinary.

Any other suggestions on where to look for potential problems would be apprecisted.

Thanks

Yes check with your host about UTF-8 encoding issues with the software on the server. Since you didn't post exact version numbers in your profile you'll have to check this for yourself and ENSURE all versions are UTF-8 compliant. This includes your text editor and your FTP program.


HTH,

Thanks, I will check with the ISP.

Here are the versions on the ISP's server:
Linux Kernel 2.4.21-4.0.1.ELsmp
Apache 1.3.33 (Unix)
PHP 4.3.10
MySQL 4.0.18-standard
CPGNUKE 9.0.1 (Dragonfly901.tar.gz)
VIM 6.3.46

Compared to the versions on my home system:
Linux Kernel 2.4.24-xfs
Apache 2.0.49 (Unix)
PHP 4.3.5
MySQL 4.0.18
CPGNUKE 9.0.1 (Dragonfly901.tar.gz)
VIM 6.2.214

I've been moving the files around with scp. I will try again with ftp, but could that really make the difference?

I have this installed now.

Line 68 of includes/cmsinit.inc

I changed GZIPSUPPORT to be defined as false.
//define('GZIPSUPPORT', extension_loaded('zlib'));
define('GZIPSUPPORT', false);

Checking the versions of gzip on the ISP's server vs. my home machine.
ISP's gzip = 1.3.3
My gzip = 1.3.5

Is it the case that gzip > 1.3.3 is required or is there still something going on with UTF-8, or is this a bug of sorts?

Thanks to all who helped including a shout out to Daniel at thehostingcompany.us for helping to figure out where the problem was.

For obvious reasons, the links in the first post will no longer be active.

Looking forward to setting up the new install.

Strange.. I decided to wipe the 9.0.1 install and start over with the 9.0.1.1 and no "garbled text" issue and no need to define GZIPSUPPORT as false.

I guess that's a good thing.

hmm, perhaps your host corrected something

it could have been a header problem.
when PHP outputs data BEFORE the cms system comes into play (like empty lines above '<?php') PHP will ignore to send specific header() lines.

When this happens the "Content-Type: gzip" is never send and browsers like IE don't detect the file properly.
FireFox autodetects and still should show the content properly.