#8590 closed (fixed)
Add some information in comment upgrade guide
| Reported by: | Julien Phalip | Owned by: | Jacob |
|---|---|---|---|
| Component: | Documentation | Version: | dev |
| Severity: | Keywords: | ||
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
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)
Change History (7)
by , 16 years ago
| Attachment: | 8590.comment-upgrade-doc.diff added |
|---|
comment:1 by , 16 years ago
by , 16 years ago
| Attachment: | 8590.comment-upgrade-doc-2.diff added |
|---|
comment:2 by , 16 years ago
Thanks Malcolm, I've updated the patch following your recommendations and removed the note about subversion.
comment:3 by , 16 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Ready for checkin |
comment:4 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
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.