On Wed, Oct 8, 2008 at 3:11 PM, NoviceSortOf <[EMAIL PROTECTED]> wrote:
>
> > Of the other two, one claims to be Django 1.0 and one claims to be
> > Django SVN trunk. Assuming they are what they claim to be, which one
> > is the latest depends on whether the trunk checkout is from before or
> > a
> Of the other two, one claims to be Django 1.0 and one claims to be
> Django SVN trunk. Assuming they are what they claim to be, which one
> is the latest depends on whether the trunk checkout is from before or
> after 1.0. You might get a clue by looking at django/__init__.py in
> both and che
On Oct 8, 3:28 am, NoviceSortOf <[EMAIL PROTECTED]> wrote:
> These 3 directories seem to contain many redundant files.
>
> /var/www/Django-1.0/django/
> /var/www/django-trunk/django/
>
> /usr/lib/python2.3/site-packages/django/
>
> How do I determine if one of these directories
> contains a duplic
On Wed, Oct 8, 2008 at 3:28 AM, NoviceSortOf <[EMAIL PROTECTED]> wrote:
>
> > What version of Django are you running? These two patterns are from
> > different Django versions. The first, with the include of
> > 'django.contrib.admin.urls' was the old one -- that file does not exist
> in
> > Dja
> What version of Django are you running? These two patterns are from
> different Django versions. The first, with the include of
> 'django.contrib.admin.urls' was the old one -- that file does not exist in
> Django 1.0. The 2nd pattern, referring to 'admin.site.root', is what should
> be used
On Tue, Oct 7, 2008 at 10:50 AM, NoviceSortOf <[EMAIL PROTECTED]> wrote:
>
>
> Yes I restarted, but I also noticed in urls.py
>
> 2 distinct suggested admin url patterns...
>
> (r'^admin/', include('django.contrib.admin.urls')),
> # (r'^admin/(.*)', admin.site.root),
>
> Commenting out the second
Yes I restarted, but I also noticed in urls.py
2 distinct suggested admin url patterns...
(r'^admin/', include('django.contrib.admin.urls')),
# (r'^admin/(.*)', admin.site.root),
Commenting out the second entry seems to correct
the admin_urls problem.
Why does the documentation suggest
(r'^a
On Tue, Oct 7, 2008 at 6:17 AM, NoviceSortOf <[EMAIL PROTECTED]> wrote:
> Thanks the link did the trick.
>
> The admin page though still loads rough, sometimes
> taking 3 screen refreshes to get past a
> "No module named urls" error - then it finally loads.
>
Did you restart Apache after making t
Thanks the link did the trick.
The admin page though still loads rough, sometimes
taking 3 screen refreshes to get past a
"No module named urls" error - then it finally loads.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
ADMIN_MEDIA_PREFIX is set incorrectly. It should be a URL, not a
filesystem path. If you want the admin media files served at
http://myhost.com/media/, set the value to '/media/' (which is the
default). To serve the admin media, just create a softlink to the admin
media files on disk in your we
I'm using Linux Fedora, Apache and mod_python.
I have 3 dashboard.css candidates on my system but Django admin will
not see any of them...
-
# locate dashboard.css [RETURNS]
/var/www/Djan
11 matches
Mail list logo
