Thanks for the help, much appreciated.
On Jan 13, 1:28 pm, Brian Neal wrote:
> On Jan 13, 12:06 pm, Ty wrote:
>
>
>
> > I've started creating a photo blog project to get familiar with Python
> > and Django. I'm using Python 2.6.1 and Django 1.0.2. I'm working on
> > the models and the administr
On Jan 13, 12:06 pm, Ty wrote:
> I've started creating a photo blog project to get familiar with Python
> and Django. I'm using Python 2.6.1 and Django 1.0.2. I'm working on
> the models and the administration first, before I tackle the front end
> side of the site. I have everything working fine
I've started creating a photo blog project to get familiar with Python
and Django. I'm using Python 2.6.1 and Django 1.0.2. I'm working on
the models and the administration first, before I tackle the front end
side of the site. I have everything working fine, for the exception of
an image upload f
# Cache the app label.
opts.app_label = app_label
Extending admin interface now works, but it's configuration process is a bit
tricky, as you mentioned before. After this change I had to execute
the following to update the database:
% django-admin.py sqlreset authors | perl -p
Post the code after making the recommended changes.
On Tue, Aug 30, 2005 at 08:13:34PM -0500, Adrian Holovaty wrote:
> Regarding the error, you'll need to make sure your __init__.py file
> contains "myapp" in its "__all__" variable, assuming "myapp.py" is the
> name of your model module. See
> http://www.djangoproject.com/documentation/model_api/#
On 8/30/05, Adam <[EMAIL PROTECTED]> wrote:
> I haven't seen that error, but one thing I noticed about your model is
> that I don't think you can just add things to the admin interface (like
> you're trying to do with 'Extra info'). You have to copy the admin
> section of auth.User if you want eve
I haven't seen that error, but one thing I noticed about your model is
that I don't think you can just add things to the admin interface (like
you're trying to do with 'Extra info'). You have to copy the admin
section of auth.User if you want everything that's already there to
also show up. For in
On Tue, Aug 30, 2005 at 09:56:42AM -0500, Adrian Holovaty wrote:
> Yeah, whoever created that wiki page did it before the model syntax
> changed. Here's an official example of subclassing models:
>
> http://www.djangoproject.com/documentation/models/subclassing/
I have seen that already, but it
Yeah, I didn't update the wiki page because you told me the page you
pointed to was coming. I'll replace the previous wiki page with a link
to http://www.djangoproject.com/d ocumentation/models/subclassin g/
Adam
On 8/30/05, Igor Goryachieff <[EMAIL PROTECTED]> wrote:
> > http://code.djangoproject.com/wiki/ModelInheritance
>
> This code doesn't work. Is it connected to ticket #122?
Yeah, whoever created that wiki page did it before the model syntax
changed. Here's an official example of subclassing model
On Tue, Aug 30, 2005 at 02:21:23AM -0700, asrenzo wrote:
> I guess this could help you :
>
> http://code.djangoproject.com/wiki/ModelInheritance
This code doesn't work. Is it connected to ticket #122?
--
Igor Goryachieff
Jabber: [EMAIL PROTECTED]
http://goryachev.org/
On Tue, Aug 30, 2005 at 02:21:23AM -0700, asrenzo wrote:
> I guess this could help you :
>
> http://code.djangoproject.com/wiki/ModelInheritance
It seems to helpful for my purposes. Thanks!
--
Igor Goryachieff
Jabber: [EMAIL PROTECTED]
http://goryachev.org/
I guess this could help you :
http://code.djangoproject.com/wiki/ModelInheritance
Regards,
Laurent.
Hello, guys!
Is there a good solution to extend admin interface (including
additional fields for users table) without hacking Django sources?
In example I want to add extra fields for users table such as site,
birthdate, jabber and so on and manage it from admin interface.
Thank you!
--
I
15 matches
Mail list logo