6.0.0-beta1
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
11/5/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#9767] Login tasks don't work
*
Your Email Address
*
Spam protection
Enter the letters below:
. ,.__ .__ .__ . . \./ | \[__)[__)| | | |__/| \| |__|
Comment
> 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.
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers