Closed Bug 545140 Opened 15 years ago Closed 12 years ago

[shipping] Use User.message_set for signoff accept/reject messages instead of custom solution

Categories

(Webtools Graveyard :: Elmo, defect, P5)

Product:
Webtools Graveyard
Component:
Elmo
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: zbraniecki, Unassigned)

References

Details

Currently we use custom soluton for sending messages to the user. It would be nice to be able to use User.message_set, and with Django 1.2 it will become more flexible and fit our needs. It's a bug with TM=Future.
Any reference on the upcoming changes?
Summary: [dashboard]Use User.message_set for messages instead of custom solution → [dashboard] Use User.message_set for messages instead of custom solution
Reading the docs, I don't necessarily get where we could use that instead of something we did. django-notifications sounded more like it, IMHO. See bug 538288.
Depends on: 565358
No longer depends on: 565358
Priority: -- → P5
Summary: [dashboard] Use User.message_set for messages instead of custom solution → [dashboard] Use User.message_set for signoff accept/reject messages instead of custom solution
Depends on: 565358
Summary: [dashboard] Use User.message_set for signoff accept/reject messages instead of custom solution → [dashboard][shipping] Use User.message_set for signoff accept/reject messages instead of custom solution
Component: Infrastructure → Elmo
Product: Mozilla Localizations → Webtools
QA Contact: infrastructure → elmo
Summary: [dashboard][shipping] Use User.message_set for signoff accept/reject messages instead of custom solution → [shipping] Use User.message_set for signoff accept/reject messages instead of custom solution
Version: unspecified → 1.0
(In reply to comment #4) > http://docs.djangoproject.com/en/dev/ref/contrib/messages/ doesn't convince > me. What's wrong/missing with the builtin? I quite like it. The old one used to not have support for levels but the new one looks pretty good for that.
Well, I just rip out the non-builtin as part of killing signoff1. I don't think that the message framework does the right thing for the use cases. Think of having two tabs open, you sign off one one tab, then surf in the other to a bugzilla overview page, and it'll show a message that you signed off on something? At least that's how I understod the messages thing to work.
That message foo is gone, resolving WONTFIX.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Target Milestone: --- → 2.2
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.