[allura:tickets] Re: #6777 Create a site-wide notification mechanism

[Cory Johns <ma...@users.sf.net>]

I assumed we would only have one active notification at a time and that we wouldn't be changing them all that often.  I did consider putting it in the user session, but figured that they would fill up the user session faster than the multiple cookies would cause a problem for the browser.

I can switch it to use a single cookie, though, since the query logic already assumes only one active notification at a time.


---

** [tickets:#6777] Create a site-wide notification mechanism**

**Status:** in-progress
**Created:** Fri Oct 18, 2013 09:37 PM UTC by Cory Johns
**Last Updated:** Mon Oct 21, 2013 08:43 PM UTC
**Owner:** Cory Johns

It's sometimes useful to present some information to all users in a semi-persistent fashion, related to the site as a whole.  Create a mechanism to store and present these notifications.

The notifications should be semi-persistent, unlike the existing flash messages.  The notifications should be closable; once closed, they should not show up for that user again until a new message is in effect.  The notifications should also support a (per message?) configurable number of impressions per user; after the user has seen the message the specified number of times, it should no longer be shown to that user.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.