[Tickets #13329] imp is not accepted as initial application
noreply at bugs.horde.org
noreply at bugs.horde.org
Tue Jul 8 12:35:35 UTC 2014
BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE
E-MAIL-ADRESSE WERDEN NICHT GELESEN.
Ticket-URL: http://bugs.horde.org/ticket/13329
------------------------------------------------------------------------------
Ticket | 13329
Erstellt Von | piper at hrz.uni-marburg.de
Zusammenfassung | imp is not accepted as initial application
Warteschlange | Horde Base
Version | 5.2.0RC2
Typ | Bug
Status | Unconfirmed
Priorität | 1. Low
Milestone |
Patch |
Zuständige |
------------------------------------------------------------------------------
piper at hrz.uni-marburg.de (2014-07-08 12:35) hat geschrieben:
With 'Mail' set as initial application, horde 5.2 will always start
with the 'portal'-page. Allthough changing 'initial_application' to
any other app (eg. 'Calendar' or 'Addressbook') results in starting
with the chosen app. In Horde 5.1.6 'Mail' as the initial_application
was accepted w/o problems.
On hunting this down, I came to the solution to hand over
'Horde_Perms::SHOW' with 'hasPermission' in horde/index.php (line 64):
$registry->hasPermission($initial_app, Horde_Perms::SHOW))
as the function hasPermission in php/Horde/Registry.php on line 1699
has a default of "HordePerms::READ" but checks on 'Horde_Perms::SHOW'
I do not understand what is going on here, especially as the
hasPermission-code seems not to be changed from 5.1.6, but would my
solution be correct?
Thanks for any hint,
Andreas
More information about the bugs
mailing list