Code

Opened 6 years ago

Closed 6 years ago

Last modified 3 years ago

#8590 closed (fixed)

Add some information in comment upgrade guide

Reported by: julien Owned by: jacob
Component: Documentation Version: master
Severity: Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:

Description

Some users seems to have trouble upgrading to the newcomments contrib app, as in #8571 and http://groups.google.com/group/django-users/browse_thread/thread/eb5db61766a5dc07

Also, as I was going to upgrade to the new system, I jumped straight away to the "Upgrade" page. Then, running the SQL command wouldn't work because I had forgotten to run syncdb to create the new tables. I think this might potentially be a trap for a lot of users.

The attached patch attempts to fix those two issues.

Attachments (2)

8590.comment-upgrade-doc.diff (1.1 KB) - added by julien 6 years ago.
8590.comment-upgrade-doc-2.diff (860 bytes) - added by julien 6 years ago.

Download all attachments as: .zip

Change History (7)

Changed 6 years ago by julien

comment:1 Changed 6 years ago by mtredinnick

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

Up to Jacob to decide if he wants to include this in general, but you can fix at least part of the patch: we never include information about "if you are running from subversion". The documentation is written for people using a release and that sort of very temporal change will rapidly go out of date. If you're running from subversion you're expected to know how to debug problems of that nature, or at least know enough to check on the mailing list.

Changed 6 years ago by julien

comment:2 Changed 6 years ago by julien

Thanks Malcolm, I've updated the patch following your recommendations and removed the note about subversion.

comment:3 Changed 6 years ago by jacob

  • Owner changed from nobody to jacob
  • Status changed from new to assigned
  • Triage Stage changed from Unreviewed to Ready for checkin

comment:4 Changed 6 years ago by russellm

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [8652]) Fixed #8590: Added clarification that you need to install the new comments system before trying to port data. Thanks to julien for the report.

comment:5 Changed 3 years ago by jacob

  • milestone 1.0 deleted

Milestone 1.0 deleted

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.