#18018: MessageFailure in Django 1.4 admin
-------------------------------------+-------------------------------------
     Reporter:  Simon                |                    Owner:  nobody
         Type:  Bug                  |                   Status:  reopened
    Component:  Uncategorized        |                  Version:  1.4
     Severity:  Normal               |               Resolution:
     Keywords:  admin, messages,     |             Triage Stage:  Accepted
  failure                            |      Needs documentation:  0
    Has patch:  0                    |  Patch needs improvement:  0
  Needs tests:  0                    |                    UI/UX:  0
Easy pickings:  0                    |
-------------------------------------+-------------------------------------

Comment (by akaariai):

 I still think there is problem. If you installed admin by the docs of 1.3:
 {{{
 Add 'django.contrib.admin' to your INSTALLED_APPS setting.
 The admin has four dependencies - django.contrib.auth,
 django.contrib.contenttypes,
    django.contrib.messages and django.contrib.sessions. If these
 applications are not in your INSTALLED_APPS list, add them.
 Determine which of your application’s models should be editable in the
 admin interface.
 For each of those models, optionally create a ModelAdmin class that
 encapsulates the customized admin
    functionality and options for that particular model.
 Instantiate an AdminSite and tell it about each of your models and
 ModelAdmin classes.
 Hook the AdminSite instance into your URLconf.
 }}}
 I think you will get a non-functioning site in 1.4. 1.4 docs has this
 addition, and it is not mentioned in release notes.
 {{{
 Add django.contrib.messages.context_processors.messages to
 TEMPLATE_CONTEXT_PROCESSORS and MessageMiddleware to MIDDLEWARE_CLASSES.
      (These are both active by default, so you only need to do this if
 you’ve manually tweaked the settings.)
 }}}

 Of course, the proper test is to install Django + admin using 1.3 docs,
 upgrade to 1.4 using release notes and see if the admin still works. I
 haven't done that, but the above suggests there could be a problem.

 Note that I am not saying that the dependency should be removed, just that
 the release notes should mention this.

-- 
Ticket URL: <https://code.djangoproject.com/ticket/18018#comment:9>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Reply via email to