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

* Your Email Address
* Spam protection	Enter the letters below: .___. .. ..__ . . \| \|\|__\|[ __\|_/ \| \__\|\| \|[_./\| \
Comment	>>> 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. > > After updating this morning, I don't see those errors anymore. But I > tried to further track down why the login tasks are never run for me. > And it turns out that the code to run the tasks at the bottom of > pushApp() is never reached, because neither horde or imp are ever > pushed with $checkPerms being true. My current authentication is > setup is LDAP auth in Horde and hordeauth in IMP.
Attachment
Watch this ticket

Saved Queries