can't add an error message on top of listinfo page

Bug #413508 reported by Anna SdG
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Systers-mailman
New
Undecided
Unassigned

Bug Description

When creating a new list, an error message at the top of the create page can appear when, for instance, the input is wrong or information is missing.

It would be useful to have a simular solution for the listinfo page when the subscriber has entered wrong input or information is missing. Today, upon clicking the subscribe button one gets to a page displaying "Subscription results" including possible error messages. It is confusing to get the results when the subscription didn't go through. It would be better to get the error messages at the top of the page (in red).

Revision history for this message
Jennifer Redman (jenred) wrote :

Has this been fixed?

Revision history for this message
Anna SdG (anna-granudd) wrote : Re: [Bug 413508] Re: can't add an error message on top of listinfo page

No it hasn't.

Anna

On Mon, Nov 30, 2009 at 8:47 PM, Jennifer Redman <email address hidden> wrote:

> Has this been fixed?
>
> --
> can't add an error message on top of listinfo page
> https://bugs.launchpad.net/bugs/413508
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Systers Mailman Custom Modifications: New
>
> Bug description:
> When creating a new list, an error message at the top of the create page
> can appear when, for instance, the input is wrong or information is missing.
>
> It would be useful to have a simular solution for the listinfo page when
> the subscriber has entered wrong input or information is missing. Today,
> upon clicking the subscribe button one gets to a page displaying
> "Subscription results" including possible error messages. It is confusing to
> get the results when the subscription didn't go through. It would be better
> to get the error messages at the top of the page (in red).
>

Revision history for this message
Robin J (robin-jeffries) wrote :

This is really a mailman bug. We should find out if it has already been improved in MM3, and if not, can we contribute a solution.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.