Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

[2012-02-29] Better user feedback on faulty Ajax responses #344

silverstripe-issues opened this Issue Apr 3, 2013 · 2 comments


None yet
4 participants

created by: @chillu (ischommer)
created at: 2012-02-29
original ticket: http://open.silverstripe.org/ticket/6872

Provide better visual feedback on application errors, which can occur by loading a new page/panel,
but also on other user actions, most of them involving Ajax (e.g. reordering tree nodes).

Currently we use the jQuery.notice plugin for this (http://code.google.com/p/jquery-notice/wiki/Implementation). It shows up as a grey box (like the growl plugin for OSX). It doesn't indicate an error well, and is a bit "out of sight" (top right). Those messages are triggered through the global statusMessage() and errorMessage() methods.

We have two "types" of alerts, "good" and "bad". I suggest that we follow
the Twitter Bootstrap conventions here (http://twitter.github.com/bootstrap/components.html#alerts)
and use "error", "success" and "info" instead, each with their own styling.

I suggest that we center the message, fade out after 3 secs, give the user an option to close explicitly.
The fadeout should be disabled if the user hovers over the item, to give him a chance to read the whole text.
The text is usually a handful of words, but particularly in development mode might
be much longer (up to an A4 page of text).

Note: An easy way to simulate a server error is to add "throw Exception('My exception')'"
in the first line of the show() method in LeftAndMain.php, and try to open a page from admin/pages.

comment by: @sminnee (sminnee)
created at: 2012-06-05

Removing milestone; trimming milestones down to bare essentials in the lead-up to launch. By all means work on this if you wish, I'm just trying to get a sense of what we can't live without.

@simonwelsh simonwelsh added the 3.1 label Mar 16, 2014

@simonwelsh simonwelsh added this to the 3.2 milestone Mar 16, 2014

@sminnee sminnee modified the milestone: 3.3, 3.2 Jul 13, 2015

@tractorcow tractorcow closed this Jan 22, 2016

@chillu chillu referenced this issue in silverstripe/silverstripe-campaign-admin Jun 1, 2017


On successful submission of create campaign form, there's no success message #16

11 of 11 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment