Summary | Error: "Handler for action "dynamicinit" does not exist" after Horde logout |
Queue | IMP |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | |
Requester | ernied (at) lightspeed (dot) ca |
Created | 06/20/2014 (4034 days ago) |
Due | |
Updated | 11/03/2019 (2072 days ago) |
Assigned | 06/27/2014 (4027 days ago) |
Resolved | 07/26/2014 (3998 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
\"login.php\" does not exist.","type":"horde.error"}]}*/
No cure except to clear horde cache and restart browser.
Horde 5.2.22 and IMP 6.2.24
Handler for action "dynamicinit" does not exist
nicht behoben
herzlichen Gruß
Sigrid Philipps
State ⇒ Resolved
State ⇒ Feedback
Milestone ⇒
Priority ⇒ 1. Low
handling of session expiration in AJAX requests in all circumstances
(there were some fringe cases that didn't work well in 5.1).
Queue ⇒ IMP
Priority ⇒ 2. Medium
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒ 5.1.6
Queue ⇒ DIMP
Summary ⇒ Error: "Handler for action "dynamicinit" does not exist" after Horde logout
Type ⇒ Bug
browser, either DIMP doesn't handle it properly, or Horde doesn't
remove it properly when the client logs out and tries to log in again
with the same browser session. Attempting to read mail with DIMP after
logging back in results in a red Javascript box coming up at the
bottom of the page, reading "Handler for action "dynamicinit" does not
exist", and DIMP doesn't function at all past that point. Restarting
the browser fixes the problem, but this can be extra annoying if the
customer's login times out and forces them to log in again.
All other Horde applications (we use the Webmail suite, and we've
tested them all) work normally under these circumstances, it only
appears to affect DIMP.
This happens in every browser I've tried, on both Windows and Linux.