| Summary | custom_login.php uses default server rather than server info listed in form |
| Queue | IMP |
| Queue Version | 4.0.3 |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | |
| Requester | liamr (at) umich (dot) edu |
| Created | 05/06/2005 (7441 days ago) |
| Due | |
| Updated | 05/07/2005 (7440 days ago) |
| Assigned | |
| Resolved | 05/07/2005 (7440 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
regular login screen, then IMP isn't doing anything wrong - you just
need to modify custom_login.php to send different information.
in servers.php isn't sufficient?
My form gets populated with the info for the server field I want.
Providing the $server_key variable to populate the form and then
ignoring the information that gets POSTed and just using the first
server anyway seems kinda wrong.
State ⇒ Not A Bug
/* Use the first server defined in servers.php. */
// CUSTOMIZE THIS
It's an example script, you need to taylor it to your needs.
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ custom_login.php uses default server rather than server info listed in form
Queue ⇒ IMP
instances. If I use the default horde login screen, it the preferred
mechanism works fine.
If I use the custom login screen, the form seems to be populated
correctly. I get all of the correct server information from
imp/config/servers.php, but I get logged into the default (first)
entry in the servers file. It seems to ignore all the information
that's getting posted to redirect.php