Code

Opened 12 months ago

Closed 12 months ago

Last modified 12 months ago

#20319 closed Uncategorized (invalid)

errors in your isntructions

Reported by: anonymous Owned by: nobody
Component: Documentation Version: 1.4
Severity: Normal Keywords:
Cc: bmispelon@… Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

in reference to ticket #20318

I'm not going to type a long description because you seem determined to not want to deal with or even take the time to look at the issue that I was having..And you seem offended, for what I don't know... I'm am not having any difficulty with your tutorial, Its fairly easy (except when I follow it to the letter and it doesn't work; and I have to change things to make it work. As I did with this issue....

However there was a type O on my last ticket I mistakenly wrote settings.py instead of admin.py, But I guess you rather point out my mistakes in an email instead of looking at your web site and seeing your own.... So Ill make it easy for you and attache a picture. You can do as you wish.. Please do not reply as your condescending tone and intention on wasting both our time is becoming irritating.

Attachments (0)

Change History (3)

comment:1 Changed 12 months ago by dbshaw909@…

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

since i cant up load a jpeg I will cut an past again pleases look where the arrow is.

class Poll(models.Model):

# ...
def was_published_recently(self):

return self.pub_date >= timezone.now() - datetime.timedelta(days=1)

was_published_recently.admin_order_field = 'pub_date'
was_published_recently.boolean = True
was_published_recently.short_description = 'Published recently?' <----- Right here actually has to be

'was_published_recently'

comment:2 Changed 12 months ago by bmispelon

  • Cc bmispelon@… added
  • Resolution set to invalid
  • Status changed from new to closed

Hi,

Please don't open multiple tickets for the same issue: it's better to keep the discussion in one single ticket.

As Russell said in his comment on the other ticket, it's perfectly fine to reopen a ticket if you have more information to add to it.

Remember that django is a community project run by volunteers.

Communication on the internet is notoriously hard. I find that things go better if you assume that the person on the other end is trying to help you (which we are).

Thanks.

comment:3 Changed 12 months ago by russellm

What @bmispelon said;

Plus - You're mistaken. The text "Published recently?" does not need to be "was_published_recently". As the text describes, you're defining a label, and the label can be any text you want. "Published recently?" is an entirely valid string, and can be used as a label. If you're getting an error that says "was_published_recently" not defined, then you've done something else wrong.

I want to help you. I've offered to help you. But you need to meet me half way. I'm not psychic, and I can't work out what you've done wrong unless you show me what you've done. After three attempts, you've now finally shown us a piece of actual code. And I'm telling you that this piece of code is CORRECT as typed, and as written in the tutorial. If you're getting errors, then you've done something else wrong.

So - if you want to pursue this further, *please* don't open another ticket. Reopen *this one*, and provide more details. Or, head over to #django on irc, or the django-users mailing list, and someone will be able to help you.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.