[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bricolage-bugs
Subject:    [Bug 1331] Checkin and Publish Animations Ignore Errors
From:       bugzilla-daemon () exclupen ! com
Date:       2008-04-29 19:53:42
Message-ID: 20080429195342.A8F1FD33B7 () mail ! exclupen ! com
[Download RAW message or body]

http://bugs.bricolage.cc/show_bug.cgi?id=1331





--- Comment #1 from David Wheeler <david@kineticode.com>  2008-04-29 15:53:42 ---
Marshall, this is the one bit of the Ajax revisions that I noticed that doesn't
have an easy fix that I can just jump in and make myself. And it concerns me a
bit. The overarching issue is that, for those forms where there is an Ajax
submission (desk moves/shelves/publishes, element editing, I'm sure there's
more), if there is an error on the back end where the user's changes don't
take, there is nothing to tell the user such.

So if I try to publish a story from a desk by double-clicking the icon or
selecting "Publish" from the dropdown menu, and there is a problem publishing
the story, the story should not disappear and I should get an alert of some
kind telling me that it failed.

Similarly, if I try to add one too many fields to an element, it properly fails
and nothing changes, but there is no alert to tell me that that's happened.
Granted, this is hard to do because you can't find fields that are already at
the max num in the "Add Element" but we should still account for this.

Where else do you have Ajax submissions where we should try to account for
errors and properly notify the user? Can you take a look at this stuff?

Thanks,

David


-- 
Configure bugmail: http://bugs.bricolage.cc/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]