Thank-you, Thank-you Curtis !! That is exactly the problem. I had put these urls in urls.py and referenced view functions that have not been implemented yet. It had not caused a problem up until now, and I never thought to check the 'viewer' error message clue with my defined, but unimplemented views.
I had almost given up on getting a response, again thank-you. On Jan 31, 6:40 pm, Curtis <[EMAIL PROTECTED]> wrote: > I had the sameproblem. > > I think theproblemis that you are referencing a non-existent (view) > function named 'viewer' in your urls.py. This wasn't aproblemin > previous versions, but with the addition of the reverseurllookup, > non-existent views now cause problems. > > What I gather is happening is that on the first (admin) request, all > urls and consequently views are introspected. Since one or more of > the views (defined in the urls.py) don't exist an exception is > raised. However, the results are cached and subsequent loading of > thepagedon't cause an error (but the links are now incorrect). > > So check your urls.py and see if that clears up theproblem. > > -Curt > > On Jan 27, 12:43 pm, paceman <[EMAIL PROTECTED]> wrote: > > > > > I seem to be having aproblemwith the djangoAdminfacility. I have > > used it quite some time with no problems, however, I ran into a > >problemand it may relate to how I tried to solve some other > > problems. So here is some background that may be important. > > > Background: > > ***************************************************************** > > Initially, I was using Django 0.96 in Debian, but I wanted to reduce > > the amount of code needed to be written by using Generic Views - in > > particular the Create / Update / Delete (CRUD) Generic Views. > > > I found that using the 0.96 version did not facilitate automatic form > > creation (this is provided in newforms). So, I wanted to try what was > > described in the Django Book - Appendix D. I found Patch #3639 which > > modifies the above Generic View for use with newforms - and hence > > automatic form generation. It worked to a degree, but it did not > > produce select boxes in the form for some reason. > > > I installed the Django 0.97~svn6996-1 in Debian Experimental, then > > applied Patch #3639 to it, and the result was much better for the > > Generic View - select boxes are being rendered properly. However, a > > nigglingproblem(unrelated to thisproblem) is that the model foreign > > key to theAdminUser table is not rendering the User table in the > > Generic Update view - don't know how to do that yet (maybe you can't). > > > Finally, I get to theproblemthat hopefully I can get some help > > with. In progressing from 0.96 to 0.97 I carried patch #3185 with me > > - this allows theAdminfacility to be available in > > theurlashttp://mysite/myapp/admininsteadofhttp://mysite/admin. I liked it > > because it related theadminto the application in theurl- which is > > want the user sees. The django default is toreferencetheadminin > > the projecturl.py, not in the appurl.py. I had moved it to the app > > and applied the patch. It worked great in 0.96. However, in 0.97 > > when first accessed it fails with 'cannot find viewer in /mysite/ > > myapp: > > ******************************************************************** > > ViewDoesNotExist at /mysite/myapp/admin/ > > Tried viewer in module mysite.myapp.views. Error was: 'module' object > > has no attribute 'viewer' > > > Exception Location: /var/lib/python-support/python2.4/django/core/ > > urlresolvers.py in _get_callback, line 184 > > > Template error > > > In template /var/lib/python-support/python2.4/django/contrib/admin/ > > templates/admin/base.html, error at line 28 > > ****************************************************************** > > It refers to contrib/admin/templates/admin/base.html. Specifically, > > the line (and 2 similar ones below it): > > > <a href="{%urldjango.contrib.admin.views.doc.doc_index %}">{% trans > > 'Documentation' %}</a> > > > If you refresh theurlagain, it does not fail, but you find that the > > Doc, Change Password, and Logout does not work. The reason is that > > theurltemplate tag does not fully find theurlit only picks up / > > mysite/myapp/adminand misses the doc/ that should be on the end of > > it. > > > When I looked up the code on the Django site for base.html, it refers > > to Revision 3091, and says it was last modified 2 years ago by hugo. > > I notice that the corresponding line, line 23 contains a different > > href, not using theurltemplatetag, but just 'doc/'. I tried this > > modification, and the error dissappeared, but the Doc, Change > > Password, and Logout links only work in the topAdminpage. So, I > > know it is not really the solution. I checked the code in 0.96, and > > that is also how the href is done - only thing is it works in 0.96 > > regardless of whichAdminpageyou are on. > > > I realize that the svn versions of django are not guarenteed bug free > > - I tried to search for a similar bug, but could not find one. I also > > checked out the most recent Django version using svn and still got the > > sameproblem. Is anyone aware of this bug? Or, did I make some wrong > > assumptions in the above leading to aproblemof my own making? I > > know that the Django Book says that theurltemplate tag is undergoing > > reconstruction - could this be negatively affecting theAdmin > > facility? That code is a bit of a mystery to me. > > > I really appreciate any help offered. I have used this forum once > > before with amazingly helpful responses. Many thanks to those of you > > dedicating some of your valuable time to helping others.- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
