Jump to:
| Project: | Pontomail Webmail Client |
| Version: | master |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
Under fresh cvs (11/10/2006) install of Pontomail I will get the following error after trying to update account:
* Unable to connect to this server.
* warning: Invalid argument supplied for foreach() in /home/vbabye/public_html/drupal-4.7.3/sites/www.v-baby.ee/modules/pontomail/pontomail.module on line 1062.
* warning: imap_getmailboxes(): supplied argument is not a valid imap resource in /home/vbabye/public_html/drupal-4.7.3/sites/www.v-baby.ee/modules/pontomail/IMAPService.inc on line 92.
* warning: imap_getsubscribed(): supplied argument is not a valid imap resource in /home/vbabye/public_html/drupal-4.7.3/sites/www.v-baby.ee/modules/pontomail/IMAPService.inc on line 109.
* warning: Invalid argument supplied for foreach() in /home/vbabye/public_html/drupal-4.7.3/sites/www.v-baby.ee/modules/pontomail/pontomail.module on line 1183.
* warning: Invalid argument supplied for foreach() in /home/vbabye/public_html/drupal-4.7.3/sites/www.v-baby.ee/modules/pontomail/pontomail.module on line 1243.
* warning: Invalid argument supplied for foreach() in /home/vbabye/public_html/drupal-4.7.3/sites/www.v-baby.ee/modules/pontomail/pontomail.module on line 1278.
* warning: Invalid argument supplied for foreach() in /home/vbabye/public_html/drupal-4.7.3/includes/form.inc on line 655.
I am using PHP version 4.4.4. under Apache 1.3.37 (Unix)
Comments
#1
Just to describe the problem further -- I have looked at issue. http://drupal.org/node/80423 and this batch IS ALREADY applied into my pontomail.module. Should we reopen this closed issue instead?
#2
I was debugging in yesterday, and I found solutin for my problem (the reason was in wrong server connection settings), but I still believe that a REAL solution for this problem needs a patch for the reasons below:
1. Server connection settings are not actually tested when a new account has been set up. So user does not get any notification about the error in the settings and wrong server configuration is entered into the database.
2. When user now tries to update/edit/contact the server, an error will be engaged due to connection error and this account will become automatically disabled in Pontomail.
3. There is no way to enable this account again trough user interface (through php debbuger). The reason is, that although server update panel has checkbox for enabling a server again, this $_POST(ENABLED) setting will become overwritten in the code from the database queried db_query(DISABLED) value, once the Update button is pressed.
4. No message on the later fact will be given to the user. So user may actually play around with different server settings to solve connection error problem. But these settings are actually never applied. So the user won’t find the configuration problem.
5. The on way to correct the situation trough user interface is to delete disabled server and add new server with different settings.
You can replicate the first part of the behaviour by entering intentionally improper connection settings (enable TLS, Validate Certificate, or smth.) and then trying to correct these settings trough “account edit”.
You can replicate just the later part of the behaviour by disabling perfectly working account in e-mail accounts window (first checkbox under General Settings). There is now no way to enable this account again.
So the patch should contain two things:
1. Server configuration testing prior entering the account into database at the first place.
2. Bug-fix on fixing enabling/disabling behaviour in “account edit”.
Will see, if I can come up with something within couple of days :)
#3
Sorry, in point 3 I wanted to say in parenthesis "(TESTED trough php debbuger)"