#4796: Accessing admin pages as a logged in user crashes under apache + fcgi
--------------------------------------+-------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: reopened | Component: Admin interface
Version: newforms-admin | Resolution:
Keywords: fcgi unicode __proxy__ | Stage: Unreviewed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
--------------------------------------+-------------------------------------
Changes (by Jeff Forcier <[EMAIL PROTECTED]>):
* status: closed => reopened
* resolution: invalid =>
Comment:
I'm getting this too, as of SVN changeset 5677, with databrowse. Fairly
stock Apache2 + mod_python setup, Python 2.5, Linux.
In my situation, I'm just trying to use databrowse on a brand-new app with
three simple model classes, and get a similar error. The offending `lazy`
object is one of my Model objects' '''nonexistent'''
Meta.verbose_name_plural - in other words, the databrowse template is
trying to access `MyModel._meta.verbose_name_plural` (which is not
defined), and at least in the Python shell, that attribute results in a
`lazy` object. My other two classes in the same file '''do''' define
verbose_name_plural, and accessing the attribute on them results in
regular strings.
I've toyed around in the shell and read over the debug page and can't
figure out exactly what's going wrong. It appears that in normal usage,
calling `force_unicode` or `unicode` on a lazy object works as you'd
expect (i.e. it takes the output of the stored function and makes it into
a Unicode string); even when I `del` a lazy object's `__unicode__`
attribute/method, `unicode` still works by returns a string representation
of the object, i.e. `u'<django.utils.functional.__proxy__ object at
0x8606a2c>'`.
--
Ticket URL: <http://code.djangoproject.com/ticket/4796#comment:6>
Django Code <http://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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
