Summary | Can not login after upgrade |
Queue | Horde Groupware Webmail Edition |
Queue Version | 1.2.7 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | |
Requester | samuel.wolf (at) wolf-maschinenbau (dot) de |
Created | 10/04/2010 (5393 days ago) |
Due | |
Updated | 02/15/2011 (5259 days ago) |
Assigned | |
Resolved | 10/05/2010 (5392 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
and where my working config contains
$conf['cookie']['path'] = '/intranet/webapps/horde'
The config AFTER upgrade contained
$conf['cookie']['path'] = '/horde'
And thus I could not login. Good that I puzzled about this last time
so I slowly recalled what took me a day to figure out last time.
As much as I love Horde compared to the MANY webapps I've installed
over time, IMHO a focus should lie in easier install. I realize it's a
complex piece of software, but not having a simple install drive
potential users away from this great app. Where can I help to improve
other than filing a bug?
relevant section of Horde's configuration page. If you need further
help, please ask on the mailing list.
Works fine, thank you for the update.
State ⇒ Not A Bug
Priority ⇒ 1. Low
relevant section of Horde's configuration page. If you need further
help, please ask on the mailing list.
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Can not login after upgrade
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Authentication backend is a IMAP server.
/tmp/horde.log says "Oct 04 20:59:08 HORDE [notice] [imp] Login
success for ..."
After press of the login button the horde loginpage reload and the
input field of username and password are empty again.
Delete browser cache and tested with a different browser as well.