Re: Reload Admin interface after model changes

[Dirk Eschler]

Am Samstag, 7. Oktober 2006 02:57 schrieb Matt:
> It is probably number 2. I'm using apache2 w/ mod_python. I'll check
> when I'm back at work next.
>
> As for what I did to dump the old app, I deleted the application folder
> and then recreated everything using manage.py startapp.
>
> Thanks for the quick reply. I'll post here again to confirm that it was
> a problem with not restarting apache.
>
> Matt

Hi Matt,

like mentioned in the docs, for a development server you should 
set "MaxRequestsPerChild 1" in your Apache config. That worked for me.

http://www.djangoproject.com/documentation/modpython/

Best Regards,
Dirk Eschler

-- 
Dirk Eschler 
http://www.krusader.org

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: Re: Reload Admin interface after model changes

[Russell Keith-Magee]

On 10/7/06, Matt <[EMAIL PROTECTED]> wrote:
>
> It is probably number 2. I'm using apache2 w/ mod_python. I'll check
> when I'm back at work next.
>
> As for what I did to dump the old app, I deleted the application folder
> and then recreated everything using manage.py startapp.

Keep in mind that unless you are using sqlite, deleting the
application folder and starting from scratch won't clear the database
of any tables that were created the first time around.

> Thanks for the quick reply. I'll post here again to confirm that it was
> a problem with not restarting apache.

Glad to be of help.

Yours,
Russ Magee %-)

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Re: Reload Admin interface after model changes

[Matt]

It is probably number 2. I'm using apache2 w/ mod_python. I'll check
when I'm back at work next.

As for what I did to dump the old app, I deleted the application folder
and then recreated everything using manage.py startapp.

Thanks for the quick reply. I'll post here again to confirm that it was
a problem with not restarting apache.

Matt


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---

Reload Admin interface after model changes

[Matt]

Hey. I'm a Django. I've got in installed and I've created a model and
tested out the admin interface. Then I wanted to make some changes to
the model and reload the change to the DB and the admin console.

After searching around for a bit, I haven't found a good way to do
this, although it appears to be something that is being worked on. I
was able to use sqlreset to change the DB, but I wasn't able to the
changes to occur in the admin console. Instead I get errors indicating
that it is still trying to use the old DB model.

I ended up dumping the old app and creating it again (with the same
name). However, the admin interface is still trying to use the old DB
model.

What can I do to reload the admin interface so that it uses the new
models?

Matt


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~--~~~~--~~--~--~---