Re: Attribute error

tanks for this, it was helpfull On Thu, 13 May 2021 at 15:31, Ryan Nowakowski wrote: > It's likely that your instance of OrderItem has a product field that's > null. > > On May 12, 2021 3:50:42 AM CDT, Peter Kirieny > wrote: > >can somebody help with this please, am building an ecommerce web

Re: Attribute error

It's likely that your instance of OrderItem has a product field that's null. On May 12, 2021 3:50:42 AM CDT, Peter Kirieny wrote: >can somebody help with this please, am building an ecommerce web and >when i >want to view my cart i get this error >AttributeError: 'NoneType' object has no

Re: Attribute Error

Have you tried putting a print statement in views.py RegisterStudent to get to an output in the server. Perhaps the problem is in the template and the get isn't even coming to the view Sent from my iPad > On 17-Feb-2020, at 6:30 PM, Adam Mičuda wrote: > > Hi, > you have to return instance of

Re: Attribute Error

Pleas provide the code for clickjacking.py On Mon, 17 Feb 2020 at 14:50, Ernest Thuku wrote: > Hello guys please help on the error. I have been stuck for days now. > I am Ernest from Kenya. > please look into these files below > > -- > You received this message because you are subscribed to the

Re: Attribute Error

Hi, you have to return instance of `django.http.HttpResponse` class from you view `RegisterStudent` instead of string: *line 98* and *line 99*. see https://docs.djangoproject.com/en/3.0/ref/request-response/#django.http.HttpResponse Regards. Adam po 17. 2. 2020 v 13:49 odesílatel Ernest Thuku

Re: attribute error

HI, You are trying to include a view that is called views from the module home in the app jobs. I think what you mean is : path('', jobs.views.home, name='home') Try that instead. Regards, Andréas Den tis 28 aug. 2018 kl 13:35 skrev Imran Sharief : > hi every one i am new to django am

Re: Attribute error

The date = models.DataTimeField() should be date = models.DateTimeFild() ? https://docs.djangoproject.com/en/2.0/ref/models/fields/#datetimefield Caleb Bryson 于2018年5月31日周四 上午9:45写道： > I am getting a attribute error when i try to run my server. does anyone > know what i can change in this code

Re: Attribute error

The f in field should be capitalized On Wed, May 30, 2018, 20:10 Caleb Bryson wrote: > it is still saying "AttributeError: model 'django.db.models' has no > attribute 'Charfeild' > > On Wednesday, May 30, 2018 at 10:04:04 PM UTC-4, Mike Dewhirst wrote: >> >> On 31/05/2018 11:45 AM, Caleb Bryson

Re: Attribute error

I think it was because i did not use camel casing so CharField instead of Charfield. I will continue the tutorial and see if that works On Wednesday, May 30, 2018 at 10:04:04 PM UTC-4, Mike Dewhirst wrote: > > On 31/05/2018 11:45 AM, Caleb Bryson wrote: > > I am getting a attribute error when

Re: Attribute error

it is still saying "AttributeError: model 'django.db.models' has no attribute 'Charfeild' On Wednesday, May 30, 2018 at 10:04:04 PM UTC-4, Mike Dewhirst wrote: > > On 31/05/2018 11:45 AM, Caleb Bryson wrote: > > I am getting a attribute error when i try to run my server. does > > anyone know

Re: Attribute error

On 31/05/2018 11:45 AM, Caleb Bryson wrote: I am getting a attribute error when i try to run my server. does anyone know what i can change in this code to fix that? Try indenting the __str__ method so it is within the scope of the Post class from django.db import models class

Re: Attribute error at /admin/ by Django

On vrijdag 6 april 2018 09:05:20 CEST Hamroz Jumaev wrote: > http://dpaste.com/2GDFCG8 No middleware. -- Melvyn Sopacua -- 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

Re: Attribute error, with a very basic banking app

Thanks for that Michal, I see what you mean. I've bookmarked it. Thanks to everyone for all the detailed replies it really helps make sense of CBV :) On Fri, Aug 26, 2016 at 3:48 PM, Michal Petrucha < michal.petru...@konk.org> wrote: > On Fri, Aug 26, 2016 at 10:29:16AM -0400, Andromeda

Re: Attribute error, with a very basic banking app

I can help with this one. But I m not ready to write code over weekend. It is a nice to have used django auth model. You can extend it and this can cut a lot of your code. Early versions had a problem with correct author model but now situation is better. Try to catch me at the beginning of the

Re: Attribute error, with a very basic banking app

I've read the tutorial but I didn't fully appreciate how useful CBV are. Amazing as well that sometimes you can write almost no code. Thanks a lot for explaining that. On Fri, Aug 26, 2016 at 3:29 PM, Andromeda Yelton < andromeda.yel...@gmail.com> wrote: > In my experience, CBVs are useful when

Re: Attribute error, with a very basic banking app

On Fri, Aug 26, 2016 at 10:29:16AM -0400, Andromeda Yelton wrote: > In my experience, CBVs are useful when the view you want to write is > basically a create, read, update, or delete operation on a single database > item, or a bunch of instances of the same model (...and it turns out a lot > of

Re: Attribute error, with a very basic banking app

In my experience, CBVs are useful when the view you want to write is basically a create, read, update, or delete operation on a single database item, or a bunch of instances of the same model (...and it turns out a lot of web app pages are just that). And they're useful because they let you do

Re: Attribute error, with a very basic banking app

heh heh. I don't fully appreciate the usefulness of CBV at the moment. Getting a simple example working helps as much as reading the tutorial. Thanks again for your help, Neil On Fri, Aug 26, 2016 at 2:24 PM, Sergiy Khohlov wrote: > Never mind. > Few year ago I was

Re: Attribute error, with a very basic banking app

Never mind. Few year ago I was thinking that moving to CBV is bad idea, but suddenly BUUUHHH !! in my head and everything was clear. Many thanks, Serge +380 636150445 skype: skhohlov On Fri, Aug 26, 2016 at 3:40 PM, Neil Hunt wrote: > Hello Serge, > > I can't believe

Re: Attribute error, with a very basic banking app

Hello Serge, I can't believe that's all I have to add to get the class based views to work. It seems easier to get it to work than I thought it would be. Now that you've explained it. Thank you so much for that. Kind regards, Neil On Fri, Aug 26, 2016 at 11:46 AM, Sergiy Khohlov

Re: Attribute error, with a very basic banking app

Hello Neil, It is nota problem to use Class based view. Could you please update your views.py with next code. Look like you would like to have detail of the deposit in this case add next string to the header from django.views.generic import DetailView from models import Account1, Person

Re: Attribute error, with a very basic banking app

Thank you so much Andromeda. I didn't know you could use class based views. I'll have a look at the documents. I don't know why I was trying to use them when I didn't need to. On Thu, Aug 25, 2016 at 4:23 PM, Andromeda Yelton < andromeda.yel...@gmail.com> wrote: > The stacktrace is helpful,

Re: Attribute error, with a very basic banking app

The stacktrace is helpful, thanks! The specific message with the AttributeError is helpful here: `AttributeError: 'module' object has no attribute 'DepositView'` The line above it is ` File "/home/soupdragon/DJapps/banking/mybank/banking/urls.py", line 8, in url(r'^deposit/$',

Re: Attribute error, with a very basic banking app

Thanks for your speedy reply, I've attached the stack trace On Thursday, August 25, 2016 at 4:00:16 PM UTC+1, ludovic coues wrote: > > Could you share the full stack trace you get when trying to run the server > ? > The attribute error should come with a ton of information like the > file and

Re: Attribute error, with a very basic banking app

Could you share the full stack trace you get when trying to run the server ? The attribute error should come with a ton of information like the file and the line where the error occur. 2016-08-25 16:57 GMT+02:00 Neil Hunt : > I've beem working on a simple banking app based on

Re: Attribute error

Capitalize class names. class Wish(models.Model): the_wish = models.CharField(max_length=100) On Apr 30, 4:26 pm, Pulkit Mehrotra wrote: > changed the name but nothing happened > the django version is 1.3 -- You received this message because you are subscribed

Re: Attribute error

changed the name but nothing happened the django version is 1.3 -- 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

Re: Attribute error

On Sat, Apr 30, 2011 at 3:45 PM, Pulkit Mehrotra wrote: > 'module' object has no attribute 'CharField' > > What does this error means ??? > > View for this is: > from django.shortcuts import render_to_response > from django.http import HttpResponseRedirect,HttpResponse

Re: Attribute error

class wish(models.Model): wish=models.CharField(max_length=200) what's your django version On Sun, May 1, 2011 at 3:45 AM, Pulkit Mehrotra wrote: > AttributeError at /mysite/wishlist/ > > 'module' object has no attribute 'CharField' > > What does this error

Re: ATTRIBUTE ERROR

On Tue, Nov 2, 2010 at 11:08 AM, sami nathan wrote: > If i am doing anything wrong forgive me i am newbe > > > MY error is > Exception Type:         AttributeError > Exception Value: > > 'str' object has no attribute 'resolve' > > Exception Location: >        

Re: ATTRIBUTE ERROR

Hi, I feel there are some places which need to modify: 1. urlpatterns should be (r"^wap/di/sub/$", current_datetime), 2. It seems that the view function is endless loop... 2010/10/28 sami nathan > My occured Error is > > Exception Value: > > 'str' object has no

Re: Attribute Error when doing a syncdb.

//I'm doing a little blog app and I'm going to be using tagging in it. So I wen to the google code page and downloaded it, named it tagging (instead of tagging-0.2.1), and then ran the install.// Does the unzipped folder had a directory 'tagging' inside with the app rests? Please include that

Re: Attribute Error: 'NoneType' object has no attribute 'get_field_sets'

Molly, You are on windows. So $ is not applicable to you. Go to command prompt and type python manage.py validate Anyway, I have sent you a mail that points to one of Django documentation page. See if you have the admin class defined. If you are new to programming/python/django, I would

Re: Attribute Error: 'NoneType' object has no attribute 'get_field_sets'

My bad, I mean I have to import all of the errors it gives me when I got to run the site.. What do you mean "Have you tried $ python manage.py validate?" I put that into the cmd if that's what you mean, and it gave me an error for the $ sign, it said "'$' is not recognized as an internal or

Re: Attribute Error: 'NoneType' object has no attribute 'get_field_sets'

What do you mean with "importing your models"? Do you mean syncing them with the database? Have you tried $ python manage.py validate? 2008/6/18 Molly <[EMAIL PROTECTED]>: > > I am creating an app to be run on the desktop, > > I am in the process of importing my models, and I got this error: > >

Re: Attribute Error on Dumpdata

Added ticket http://code.djangoproject.com/ticket/6155 with patch. Still need to write tests. Michael On Dec 7, 2007 3:15 PM, Karen Tracey <[EMAIL PROTECTED]> wrote: > > On Dec 7, 2007 2:31 PM, Empty <[EMAIL PROTECTED]> wrote: > > > > > > > > > Seems dumpdata is coded to require a Manager named

Re: Attribute Error on Dumpdata

On Dec 7, 2007 2:31 PM, Empty <[EMAIL PROTECTED]> wrote: > > > Seems dumpdata is coded to require a Manager named 'objects' for the > Models > > it dumps, even though (as described here: > > http://www.djangoproject.com/documentation/model-api/#manager-names), > Django > > does not require that a

Re: Attribute Error on Dumpdata

> Seems dumpdata is coded to require a Manager named 'objects' for the Models > it dumps, even though (as described here: > http://www.djangoproject.com/documentation/model-api/#manager-names), Django > does not require that a Manager named objects exists for all Models. > Whether this is just an

Re: Attribute Error on Dumpdata

On Dec 6, 2007 8:01 PM, ttk <[EMAIL PROTECTED]> wrote: > > I think I found my problem... > > I failed to add "objects = models.Manager()" into my models which > would explain why that attribute isn't found. > > I'll try this out but if anyone has additional suggestions, I'm all > ears. Seems

Re: Attribute Error on Dumpdata

I think I found my problem... I failed to add "objects = models.Manager()" into my models which would explain why that attribute isn't found. I'll try this out but if anyone has additional suggestions, I'm all ears. cheers, -ttk --~--~-~--~~~---~--~~ You

Re: Attribute Error

Guys I spent quite a while yesterday reading through the newforms section of the docs, and thought I'd taken everything in. As a python novice, I wrote a test script and couldn't replicate the error, so was beginning to wonder whether I was cracking up! After reading Malcolm's (comprehensive)

Re: Attribute Error

On Sun, 2007-08-19 at 14:30 -0700, MikeHowarth wrote: > I'll take a look at that. > > Even commenting that line out and attempting to access self.title I'm > still getting an attribute error thrown: 'Register' object has no > attribute 'title' Doug Ballanc has explained how you should be

Re: Attribute Error

I think you've got some misconceptions about newforms. http://www.djangoproject.com/documentation/newforms/ should give you the info you need. Something more like this: def save(self): #set up the objects we are going to populate user = User() # you want a new -instance- not another

Re: Attribute Error

I'll take a look at that. Even commenting that line out and attempting to access self.title I'm still getting an attribute error thrown: 'Register' object has no attribute 'title' On Aug 19, 10:22 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > As a first guess I'm not sure that user =

Re: Attribute Error

As a first guess I'm not sure that user = User is doing what you would want. I think instead you want to instantiate a new User object. All you are doing right now is creating an alias user for User. On Aug 19, 3:16 pm, MikeHowarth <[EMAIL PROTECTED]> wrote: > Hi I was wondering whether anyone