[Tickets #9767] Re: Login tasks don't work

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9767
------------------------------------------------------------------------------
  Ticket             | 9767
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Login tasks don't work
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Horde Developers, Jan Schneider
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-10-05 13:53) wrote:

> PHP ERROR: Use of undefined constant HORDE_TEMPLATES - assumed  
> 'HORDE_TEMPLATES' [pid 5489 on line 44 of  
> "/home/jan/horde-git/horde/services/portal/index.php"]

> PHP ERROR: Use of undefined constant HORDE_TEMPLATES - assumed  
> 'HORDE_TEMPLATES' [pid 5489 on line 44 of  
> "/home/jan/horde-git/horde/services/portal/index.php"]

Don't see this.

And I am (again) out of ideas.  Because this works fine for me.   
Here's the code flow:

1. User login
2. Load initial application (for me it is imp)
3. On first application pushApp(), logintasks are called.
4. Horde_Core_LoginTasks::runTasks() checks to see if Horde logintasks  
have been performed yet.
5. In this case, horde logintasks have NOT been performed, so  
Horde_Core_LoginTasks::runTasks() are run for Horde.
6. (Assuming here that there are no user interactive Horde  
logintasks), #5 is completed and the remainder of #4 is performed -  
namely, performing IMP logintasks.
7. (Assuming here that there are no user interactive IMP logintasks),  
logintasks are complete and control is passed back to pushApp() to  
continue initializing imp.

Someone will have to figure out where this chain is broken.