On Jun 27, 8:06 pm, Karen Tracey wrote:
> On Sun, Jun 27, 2010 at 1:54 PM, derek wrote:
> > File "/usr/local/lib/python2.6/dist-packages/django/contrib/admin/
> > options.py" in change_view
> > 900. change_message =
> > self.construct_change_message(request, form, formsets)
> > F
On Sun, Jun 27, 2010 at 1:54 PM, derek wrote:
> File "/usr/local/lib/python2.6/dist-packages/django/contrib/admin/
> options.py" in change_view
> 900. change_message =
> self.construct_change_message(request, form, formsets)
> File "/usr/local/lib/python2.6/dist-packages/django/c
On Jun 26, 3:39 pm, Karen Tracey wrote:
> On Sat, Jun 26, 2010 at 3:48 AM, derek wrote:
> > Caught TypeError while rendering: coercing to Unicode: need string
> > or buffer, NoneType found
>
> The typical reason for this message is a __unicode__ method for a model that
> is not returning unicod
On Sat, Jun 26, 2010 at 3:48 AM, derek wrote:
> Caught TypeError while rendering: coercing to Unicode: need string
> or buffer, NoneType found
>
The typical reason for this message is a __unicode__ method for a model that
is not returning unicode. The traceback would help to reveal whether tha
I am having some problems with inline displays, since I upgraded to
1.2. The example here seems representative so I present as much
information as seems relevant.
I have set up the user & userprofile in a standard way - as per the
"recipe" given by James Bennett here:
http://www.b-list.org/weblog
5 matches
Mail list logo