Summary | portal handling of HTTP connection errors sub-optimal |
Queue | Horde Groupware Webmail Edition |
Queue Version | 5.0.2 |
Type | Bug |
State | Resolved |
Priority | 1. Low |
Owners | Horde Developers (at) , mrubinsk (at) horde (dot) org |
Requester | jmozdzen (at) nde (dot) ag |
Created | 01/10/2013 (4549 days ago) |
Due | |
Updated | 12/17/2013 (4208 days ago) |
Assigned | 01/15/2013 (4544 days ago) |
Resolved | 11/22/2013 (4233 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | 5.2 |
Patch | No |
commit 447a8809ea95984ceeeb75d91f783c399e6849ed
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Thu Nov 21 23:42:07 2013 -0500
First stab at
Bug: 11942.Use HordeCore for Ajax-y block actions. Existing blocks work as-is
except for the Weather block's location change text input - which
is currently broken anyway and in need of refactoring.
framework/Core/js/hordeblocks.js | 27 ++++++++++++++++++
.../Core/lib/Horde/Core/Block/Layout/View.php | 29
+++++++++-----------
horde/lib/Ajax/Application/Handler.php | 21 ++++++++++----
3 files changed, 55 insertions(+), 22 deletions(-)
http://git.horde.org/horde-git/-/commit/447a8809ea95984ceeeb75d91f783c399e6849ed
Assigned to Michael Rubinsky
Milestone ⇒ 5.2
http://lists.horde.org/archives/commits/2013-November/022198.html
Milestone ⇒ 5.1
State ⇒ Assigned
Assigned to
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ portal handling of HTTP connection errors sub-optimal
Queue ⇒ Horde Groupware Webmail Edition
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
user-friendly messages.
Affected portal blocks I see are
- webmail newest unseen
- webmail summary
- horde current time
Steps to reproduce the symptoms:
- log in to H5 and open portal view (need to bbe configured for auto-refresh)
- open i.e. mail inbox in another browser tab
- log off in the "inbox" tab
- wait until portal blocks refresh
The message display is
"/*-secure-{"msgs":[{"message":"\/horde\/login.php?url=%2Fhorde%2F&horde_logout_token=91b3AoIOkEq4Jhw86y2hzg5&logout_reason=6","type":"horde.ajaxtimeout"}],"response":false}*/"
A more user-friendly message seems in order. Alternatively, the portal
should switch to the login page as other apps do...
Regards,
Jens