| Summary | Wrong backend loaded after selection on login.php |
| Queue | Gollem |
| Queue Version | 1.0.1 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | Michael Slusarz <slusarz (at) horde (dot) org> |
| Requester | jpolansky (at) lsit (dot) ucsb (dot) edu |
| Created | 01/18/2006 (946 days ago) |
| Due | |
| Updated | 01/18/2006 (946 days ago) |
| Assigned | 01/18/2006 (946 days ago) |
| Resolved | 01/18/2006 (946 days ago) |
| Attachments | gollem-h3-1.0.1-change_backend_fix.patch ![]() |
| Milestone | |
| Patch | No |
Summary ⇒ Wrong backend loaded after selection on login.phpF
State ⇒ Resolved
Assigned to Michael Slusarz
Summary ⇒ Wrong backend loaded after selection on login.php
Type ⇒ Bug
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Queue ⇒ Gollem
New Attachment: gollem-h3-1.0.1-change_backend_fix.patch
backend when changing backends via the dropdown on login.php. Our
environment consists of 3 hordeauthed/autologin backends all using FTP.
The problem seems to be that when a previously logged into backend is
selected from the login screen dropdown(calling the gollem_reload js
function) the variable "change_backend" is not defined. This causes
the backend to not be switched, even though
$_SESSION['gollem']['backends'][$backend_key] exists (because the
backend was previously logged into). We have handled this by removing
the conditional check for "change_backend" in login.php:68. From what
we can tell, you always want to change the backend at this point in
the code, as otherwise the user is returned to the file manager with
the backend they were last using.
The patch I have attached removes the conditional check on
"change_backend" in login.php. This seems to resolve our issue.
I'd appreciate any comments about how to better deal with this issue
or if others have experienced it as well.
--Jonathan