Hmmm, something must have happened when I messed with my urls.py. Now I get the exact same issue with my admin link.
Caught ViewDoesNotExist while rendering: Tried logout_user in module hcp.views. Error was: 'module' object has no attribute 'logout_user' Request Method: GET Request URL: http://localhost:8000/myapp/admin/ Django Version: 1.3.1 Exception Type: TemplateSyntaxError Exception Value: Caught ViewDoesNotExist while rendering: Tried logout_user in module myapp.views. Error was: 'module' object has no attribute 'logout_user' Exception Location: /Library/Python/2.6/site-packages/django/core/urlresolvers.py in _get_callback, line 170 Python Executable: /usr/bin/python Python Version: 2.6.1 On Sun, Mar 11, 2012 at 12:01 PM, Scott Macri <[email protected]> wrote: > Django version is 1.3.1 final. > > If I call /accounts/password_reset/ I get the following error: > > Request Method: GET > Request URL: http://localhost:8000/myapp/accounts/password_reset/ > Django Version: 1.3.1 > Exception Type: ViewDoesNotExist > Exception Value: > Tried logout_user in module myapp.views. Error was: 'module' object > has no attribute 'logout_user' > Exception Location: > /Library/Python/2.6/site-packages/django/core/urlresolvers.py > in _get_callback, line 170 > Python Executable: /usr/bin/python > Python Version: 2.6.1 > > Here is my current url setting: > url(r'^accounts/password_reset/$', > 'django.contrib.auth.views.password_reset', name='password_reset'), > > It's not even seeing password_reset. I've even tried importing it and > replacting the url with password_reset. > > from django.contrib.auth import password_reset > url(r'^accounts/password_reset/$',password_reset, name='password_reset'), > > I'm not sure where the logout_user nonsense is coming from. I only > have one url pointing to password_reset. I get the same exact error > for the password change view. I finally got fed up and wrote my own > password change functionality, but would rather use the built in > stuff. Especially for the reset pwd. > > On Sun, Mar 11, 2012 at 7:06 AM, ajohnston <[email protected]> wrote: >> Out of curiosity, which version of Django are you using? >> >> Which message to you get when ViewDoesNotExist is raised?: >> "Could not import %s.%s. View is not callable." % >> "Could not import %s. View does not exist in module %s." % >> "Could not import %s. Parent module %s does not exist." % >> >> Alan >> >> >> On Saturday, March 10, 2012 6:56:30 PM UTC-5, hack wrote: >>> >>> Strange. The same issue occurs with the password_reset view as well. >>> >>> On Sat, Mar 10, 2012 at 5:05 PM, Scott Macri <[email protected]> wrote: >>> > That's exactly what I was thinking. So I changed >>> > 'django.contrib.auth.views.change_password' to >>> > 'django.contrib.auth.views.bullfrog' in the urlconf. It renders a >>> > completely different error. Something to the effect of bullfrog not >>> > existing. >>> > >>> > On Sat, Mar 10, 2012 at 3:12 PM, Bill Freeman <[email protected]> wrote: >>> >> I would expect ViewDoesNotExist to not be sensitive to the template. >>> >> It >>> >> sounds like the urlconf is specifying a view function that does not >>> >> exist >>> >> (at least in the way and in the place that it is specified). >>> >> >>> >> On Sat, Mar 10, 2012 at 3:07 PM, Scott Macri <[email protected]> >>> >> wrote: >>> >>> Even explicitly setting the template name causes a ViewDoesNotExist >>> >>> error to occur. >>> >>> url(r'^accounts/password/change/$', >>> >>> >>> >>> 'django.contrib.auth.views.password_change',{'template_name':'registration/password_change_form.html',}), >>> >>> >>> >>> Anyone have any ideas? Thanks. >>> >>> >>> >>> On Fri, Mar 9, 2012 at 1:32 PM, Scott Macri <[email protected]> >>> >>> wrote: >>> >>>> Being new to django I am having trouble getting the built in views to >>> >>>> work. After several hours I finally got the login/logout views to >>> >>>> work, now I am not able to get the profile, or any other built in >>> >>>> views working. I am attempting to configure the change_password >>> >>>> view. >>> >>>> >>> >>>> I have a custom urls.py file in myapp directory. The main url points >>> >>>> to the one in myapp. I don't have any trouble getting any of my own >>> >>>> custom views working. However, when I try to access the change >>> >>>> password view I keep getting a view does not exist. I'm not sure why >>> >>>> this is happening. >>> >>>> >>> >>>> Here is what I have: >>> >>>> main urls.py >>> >>>> urlpatterns = patterns('', >>> >>>> url(r'^myapp/',include('myapp.urls')), >>> >>>> ) >>> >>>> >>> >>>> In the myapp folder in urls.py I have a bunch of views like this: >>> >>>> urlpatterns = patterns('', >>> >>>> url(r'^accounts/login/$', 'django.contrib.auth.views.login'), >>> >>>> url(r'^accounts/logout/$', >>> >>>> 'django.contrib.auth.views.logout'), >>> >>>> url(r'^accounts/out/in/$', >>> >>>> 'django.contrib.auth.views.logout_then_login'), >>> >>>> url(r'^accounts/password/change/$', >>> >>>> 'django.contrib.auth.views.password_change'), >>> >>>> url(r'^index/?','hcp.views.index'), >>> >>>> ) >>> >>>> >>> >>>> Attempting to access the following link works perfectly: >>> >>>> http://localhost:8000/myapp/accounts/login/?next=/myapp/home >>> >>>> >>> >>>> However, attempting to access any of the other built-in-views, such >>> >>>> as: >>> >>>> http://localhost:8000/myapp/accounts/password/change/ >>> >>>> >>> >>>> renders a ViewDoesNotExist error when logged in as the user....... >>> >>>> >>> >>>> I've followed the directions on the django site and created the >>> >>>> registration/password_change_form.html file in my templates directory >>> >>>> right next to my login.html file. >>> >>>> >>> >>>> I'm not sure what I can do, I've been struggling with getting these >>> >>>> views to work for most of the day again today. >>> >>>> >>> >>>> When I try to access the logout_then_login via the following link: >>> >>>> http://localhost:8000/myapp/accounts/out/in >>> >>>> >>> >>>> everything works perfectly. >>> >>>> >>> >>>> What could be some possible issues causing this problem? Thanks. >>> >>>> >>> >>>> -- >>> >>>> Scott >>> >>> >>> >>> -- >>> >>> You received this message because you are subscribed to the Google >>> >>> Groups "Django users" group. >>> >>> To post to this group, send email to [email protected]. >>> >>> 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. >>> >>> >>> >> >>> >> -- >>> >> You received this message because you are subscribed to the Google >>> >> Groups "Django users" group. >>> >> To post to this group, send email to [email protected]. >>> >> 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. >>> >> >>> > >>> > >>> > >>> > -- >>> > Scott A. Macri >>> > www.ScottMacri.com >>> > (571) 234-1581 >>> >>> -- >>> Scott A. Macri >>> www.ScottMacri.com >>> (571) 234-1581 >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django users" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/django-users/-/dSOpzDqSvHYJ. >> >> To post to this group, send email to [email protected]. >> 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. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. 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.
