[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            |
+Version            | Git master
  Type               | Bug
-State              | Assigned
+State              | Feedback
  Priority           | 3. High
  Milestone          |
  Patch              |
  Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-05-24 05:15) wrote:

I don't see this.  Picking an example task (e.g. IMP's delete  
attachments monthly), and setting the interval to "EVERY", I always  
get the confirmation page and I can verify that execute() is called in  
that class if the task is confirmed.

Hmmm... I think I found the issue.  It seems that *Horde* logintasks  
would be lost if the first application authenticated to did not have  
logintasks run.  This is because the Horde logintasks are always  
associated with the first application to load.

Solution (I think): Don't initiate a LoginTasks object until we are  
sure we are going to call runTasks() on it.  Seems to fix things for  
me (I now see things like last login/test.php warning notifications).

This probably would have broke when we added something like  
setupNotification() - this would have potentially caused other  
applications to be initialized before the login app is.