Yes, right now I'm using 0.96 Is error_class a 0.97 feature?
Thanks Karen. I can redo my css =P to revert to ul and li it's not that big of an issue. On Jan 20, 11:26 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Jan 20, 2008 10:42 AM, Roboto <[EMAIL PROTECTED]> wrote: > > > > > The definition for loginForm can be found at the bottom of this > > pastebin > > >http://pastebin.com/m79fa445e > > OK, since loginForm doesn't override __init__ then it the error must be > coming from Django code. Are you using 0.96? It doesn't look like the > error_class parameter existed there. Although I don't see a note in the > current doc mentioning that this is new in the development version, it's > also not mentioned at all in the 0.96 docs: > > http://www.djangoproject.com/documentation/0.96/newforms/ > > It looks like you need to either upgrade to an svn checkout of Django or > restrict your code to what was available in 0.96. > > Karen > > > > > On Jan 20, 12:39 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > > On Jan 20, 2008 12:31 AM, Roboto <[EMAIL PROTECTED]> wrote: > > > > > whoops - here is the re-edited pastebin > > > > >http://pastebin.com/m225477f8 > > > > So is loginForm coming from beta.website.forms? It's the definition of > > > loginForm that would be most helpful to see. > > > > Karen > > > > > On Jan 19, 11:36 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > > > > On Jan 19, 2008 2:02 PM, Roboto <[EMAIL PROTECTED]> wrote: > > > > > > > I've made my own custom error list and the response I continue to > > get > > > > > > is this when I try to use it. > > > > > > > TypeError at /login/ > > > > > > __init__() got an unexpected keyword argument 'error_class' > > > > > > Request Method: POST > > > > > > Request URL: http://beta.ready-ready.org/login/ > > > > > > Exception Type: TypeError > > > > > > Exception Value: __init__() got an unexpected keyword > > argument > > > > > > 'error_class' > > > > > > Exception Location: > > /home/advanced/rchan/lib/python/beta/website/ > > > > > > views.py in viewLogin, line 22 > > > > > > > I can't figure it out... did I code something wrong? or is django > > not > > > > > > being able to recognize the error_class arguement? > > > > > > > here is my views.py > > > > > >http://pastebin.com/m7a1ce7fb > > > > > > > here is my custom error list from my forms.py > > > > > >http://pastebin.com/m6d4c1c03 > > > > > > > any ideas would be greatly appreciated! > > > > > > The exception is being reported at line 22 but the file at pastebin > > has > > > > only > > > > > 19 lines. Did you chop off the top, like maybe the include's? They > > > > would > > > > > have been helpful to see, not only because it would have been easier > > to > > > > > identify the line causing the error but because it would have > > revealed > > > > where > > > > > loginForm came from. Where does it come from? It's the one that > > > > doesn't > > > > > seem to be expecting error_class as a keyword argument, so its code > > > > would be > > > > > helpful to see. > > > > > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
