Tickets :: [#2987] Login tasks fail to run

6.0.0-alpha12

6/9/25

Summary	Login tasks fail to run
Queue	IMP
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	leena.heino (at) uta (dot) fi
Created	11/17/2005 (7144 days ago)
Due
Updated	03/12/2006 (7029 days ago)
Assigned	11/17/2005 (7144 days ago)
Resolved	03/12/2006 (7029 days ago)
Milestone
Patch	No

03/12/2006 06:32:59 PM	Michael Slusarz	Comment #6 State ⇒ Resolved	Reply to this comment
Fixed in HEAD and 4.1.1.

03/12/2006 08:32:56 AM	Michael Slusarz	Assigned to Michael Slusarz

11/28/2005 03:07:00 PM	Jan Schneider	Version ⇒ HEAD

11/28/2005 03:06:00 PM	Jan Schneider	Type ⇒ Enhancement State ⇒ Accepted Priority ⇒ 1. Low

11/17/2005 02:56:43 PM	Chuck Hagenbuch	Comment #5	Reply to this comment
But what do people think about a preference callback that automatically enables maintenance in Horde if changing maintenance settings in IMP? Makes sense.

11/17/2005 02:10:44 PM	Jan Schneider	Comment #4	Reply to this comment
Would it be possible to show the status of horde's do_maintenance prefs setting in the application settings for logon tasks. No, that's not possible with the Prefs code. But what do people think about a preference callback that automatically enables maintenance in Horde if changing maintenance settings in IMP?

11/17/2005 01:49:09 PM	leena (dot) heino (at) uta (dot) fi	Comment #3	Reply to this comment
What exactly do you mean? Maintence tasks work fine here. Or does this only happen to users that configured IMP to run the tasks without confirmation? Logon task confirmation is forced. But it seems that there is some user interface confusion. The horde preference of do_maintenance is false by our default settings. When user goes to the Imp's login task settings she does not see that the horde do_maintenance prefs setting is off and these tasks wont be run. Would it be possible to show the status of horde's do_maintenance prefs setting in the application settings for logon tasks.

11/17/2005 01:14:16 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
What exactly do you mean? Maintence tasks work fine here. Or does this only happen to users that configured IMP to run the tasks without confirmation?

11/17/2005 12:57:44 PM	leena (dot) heino (at) uta (dot) fi	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Login tasks fail to run Queue ⇒ IMP State ⇒ Unconfirmed	Reply to this comment
We have gotten several reports from our users that login tasks eg. purge old messages from trash folder does not run automatically.