Re: Problems with turning on the Admin

Sorry but I still can't see the problem here. You are by the way using an old Django version and an old Python version. That's the only thing I can think about right now.

-- 

Vincenzo Prignano

Sent with Sparrow

On Saturday, November 9, 2013 at 6:53 PM, Keith Edmiston wrote:

Bumping this up once more just in case someone may have any thoughts...still a problem that has me stumped. Thanks, in advance, for ideas. 

Keith

On Friday, November 8, 2013, Keith Edmiston wrote:

bus/certs/urls.py:

from django.conf.urls import patterns, url, include
from django.conf import settings
from bus.certs.views import index

from django.contrib import admin
admin.autodiscover()

urlpatterns = patterns('',
                       (r'^apps/bus/certs/$', index),
                       (r'^apps/bus/certs/index$', index),
                       (r'^apps/bus/certs/listing/', include('bus.certs.listing.urls')),
                       (r'^apps/bus/certs/application/', include('bus.certs.application.urls')),
                       (r'^apps/bus/certs/admin/', include(admin.site.urls)),
                       )

bus/certs/listing/urls.py:

from django.conf.urls import patterns, url, include
from django.conf import settings
from listing.views import listing

# Uncomment the next two lines to enable the admin:
# from django.contrib import admin
# admin.autodiscover()
urlpatterns = patterns('bus.certs.listing.views',
                       (r'^$', listing, {}, 'listing'),
                       )

bus/certs/application/urls.py:

from django.conf.urls import patterns, url, include
from django.conf import settings
from application.views import application_view, application_submit, application_update

# Uncomment the next two lines to enable the admin:
#from django.contrib import admin
#admin.autodiscover()

urlpatterns = patterns('bus.certs.application.views',
                       (r'^(?P<app_id>\d+)/$', application_view, {}, 'application_view'),
                       (r'^update/(?P<app_id>\d+)/$', application_update, {}, 'application_update'),
                       (r'^submit/$', application_submit, {}, 'application_submit'),
                       #(r'^admin/', include(admin.site.urls)),
                       )

On Fri, Nov 8, 2013 at 12:20 PM, Vincenzo Prignano <vincenzo.prignano@gmail.com> wrote:

Can you post the line in urls.py that is calling the view function?

On Friday, November 8, 2013 6:48:28 PM UTC+1, Keith Edmiston wrote:

Sorry...I was trying to be careful of not putting so much info in the email that it became too much.

My project structure is (in part):

--bus/certs

    |_ application

      |_ __init__

      |_ models.py --> empty, using common/models.py & bus_models/models.py

      |_ urls.py

      |_ views.py

    |_ bus_models (svn: externals)
      |_ __init__

      |_ models.py --> Person

    |_ bus_shared_common (svn: externals)
      |_ __init__

      |_ static (css, js, etc.)

      |_ templates

    |_ common
      |_ __init__

      |_ models.py --> Program, Status, Application, Notes, Action, Correspondence

    |_ listing

      |_ __init__

      |_ models.py --> empty, using common/models.py & bus_models/models.py

      |_ urls.py --> only one regex so far..."listing", which calls "listing" in views.py

      |_ views.py --> "listing" function

So, in answer to your question Vincenzo, bus.certs.listing does not make a call to any model just yet.  Thanks for suggesting I look though.

Keith

On Fri, Nov 8, 2013 at 10:39 AM, Vincenzo Prignano <vincenzo...@gmail.com> wrote:

'bus.certs.listing' is this entry in your installed apps referring to the "Listing" models perhaps? We can't really help you with much more info btw.

On Friday, November 8, 2013 4:55:04 PM UTC+1, Keith Edmiston wrote:

Hi,

I am building a new site in Django 1.4 and I'm using the South migration tool to keep my dev MySQL database in sync with changes made to my models. It should be said that I use one MySQL database account to serve various Django projects/apps (confusing, yes). It all seems to be working fine until I attempt to open up the Admin site from the project currently in development (bus/certs/admin/).

It *appears* that the autodiscover is trying to find a model "Listing" that is no longer in existence, but did exist in earlier development stages. I deleted that model and have since run a South migration to extend that deletion to the database.  That seems to have worked fine. What did not seem to happen is the removal of references to the "listing" table in the django_content_type and auth_permission tables, so I removed those manually thinking the autodiscover might be "seeing" those entries and subsequently attempting to find the model in "bus_models.models". That seems to have made no difference, the error still exists.

Not sure if this matters or not, but I had initially used the admin up in a separate project ("deans" vs. "certs") and it still works.  It even still lists the "Bus_models.Listing" model and only fails once I click on that link...gives me a "Table does not exist" error, as I would expect. This does make me think, however, that there is a lingering pointer somewhere that I'm unable to locate.

I can reliably cause this error to occur and go away again by uncommenting/commenting the following lines in my bus(app)/certs(proj)/urls.py file:

from django.contrib import admin
admin.autodiscover()
(r'^apps/bus/certs/admin/', include(admin.site.urls)),

Here is the traceback of the error page that shows up when the above are uncommented (no matter what url I use):

Environment:


Request Method: GET
Request URL: https://local.utexas.edu:8000/apps/bus/certs/application/125

--
Keith Edmiston
(512)970-7222

--
Keith Edmiston
(512)970-7222

--
You received this message because you are subscribed to a topic in the Google Groups "Django users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/django-users/kP88FP75liE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAP_gv7Kw0ZO95QyOgP6ucoYrbYoWbzQ-Krj0Pzn35e71AyXzUw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/624E3C8506094DF5AAD85DA8CAD1A028%40gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.