Page 2 of 2

Posted: Tue Jul 25, 2006 8:52 am
by Bill H
The index.php has this already has some ini_set() calls, so I added that one to them. Still a blank page.

astions, did you make any changes in the config files? And where do you set the "cache expiration" time? The only time I saw was 10 minutes, so I can't imagine that is the problem.

I'm thinking one probably needs to tell it the mail server name, but I couldn't see where to put that for sure. (Several places that it might go, but none that I was clear that it should go.
:?

Posted: Tue Jul 25, 2006 9:16 am
by Benjamin
A blank page usually means display_errors is off in php.ini or .htaccess. Check your error log.

In the config dir you should have 2 files..

db.inc.php
main.inc.php

This is how I installed it..

1. Create database using phpMyAdmin or command line
2. Executed mysql.initial.sql located in the SQL directory
3. Removed the last file extension from the 2 files in the config directory, leaving me with..
db.inc.php & main.inc.php
4. Modify line 21 as follows in db.inc.php, then save it.

Code: Select all

$rcmail_config['db_dsnw'] = 'mysql://username:password@localhost/databaseName';
5. Pull it up in a browser http://192.168.1.***/dir/mail/
6. Type in mail username, password, smtp.serverAddress.com

Everything in main.inc.php is optional except to send mail I believe.

Posted: Tue Jul 25, 2006 12:41 pm
by Bill H
That's what I've done, but all I get is a blank page.
I added display_errer on with some other ini_set calls.
I'm not thinking the program is at fault, it's something I'm doing, but what?

Posted: Wed Jul 26, 2006 1:05 am
by RobertGonzalez
Can you mimic your server on your local machine? Before suggesting that you turn on display_errors on your production machine I would try setting it up on you local machine under tha same circumstances except with display_errors on so you can see what the fatal error messages are.

Also, have you made sure that you have the right version software for your version of PHP and your DB? I may have asked that before, but it may be something to look into some more if you have already.

Posted: Wed Jul 26, 2006 8:18 am
by Bill H
I think I'm giving up on this issue, as I think it's the server. The .htaccess doesn't work, the mail() function doesn't work, this webmail function doesn't work, and the tech support people just flounder around with no answers. They provide Horde webmail with so much advertising that I can barely find my email in all the clutter.

I'm hosted by a good friend of mine who just moved me to this server (he's a reseller), but pretty much nothing is working on it and from the conversations he reports with the tech support they are sixth-graders working out of a garage. Friendship or not, I'm about ready to move my site to one that I know to be professionally hosted.

Just as an aside, how do you do script development when error reporting is turned off?

Posted: Wed Jul 26, 2006 8:23 am
by Benjamin
Bill H wrote:Just as an aside, how do you do script development when error reporting is turned off?
Write code with 0 errors :D

Or access the apache error logs..

Posted: Wed Jul 26, 2006 8:43 am
by RobertGonzalez
Bill H wrote:Just as an aside, how do you do script development when error reporting is turned off?
Use a lot of error checking and error trapping. If you know what the expected result should be then check your expected value and if it is not what you think, throw an error.

I also usually create a custom error checker function that looks for whether you are on localhost or an actual domain, and if I am on localhost it actually shows a lot of information. If it is a production environment, then it errors but with little information. It also uses to die to prevent further execution of the script if the error could be a critical error.

And lastly, I always develop locally and upload. This way I can have all the error reporting directives throwing whatever I want locally so I can get as much information as possible before going live with it.

Posted: Wed Jul 26, 2006 9:54 am
by Bill H
Everah, your point is well made. There is a lot, however, about this new server that I do not like.