I'd like to suggest the attached changes to the file that is in the installed drupal directory: UPGRADE.txt,v 1.12 open the file in your browser and you should see the changes in italics.

CommentFileSizeAuthor
#8 631758-8.patch2.07 KBldpm
UpGrade.txt5.65 KBHoly Harmonica

Comments

jhodgdon’s picture

Title: UPGRADE.txt,v 1.12 » Suggested changes to UPGRADE.txt
Project: Documentation » Drupal core
Version: » 7.x-dev
Component: Correction/Clarification » documentation
Category: task » feature

This file is distributed with Drupal, so if you would like it changed, this request needs to go into the Project = Drupal issue queue. Thanks for the suggestions...

It looks like you are suggesting adding a contents section at the top, and a few notes farther down... they look like reasonable suggestions to me.

jhodgdon’s picture

Issue tags: +Novice

It would be a good project for a new doc contributor to incorporate these suggestions (with spelling, capitalization, etc. fixed) into a patch for UPGRADE.txt

dww’s picture

jhodgdon’s picture

Status: Closed (duplicate) » Active

The two issues are not duplicates. This one is suggesting adding a table of contents. The other is suggesting that "contrib and custom" modules be clarified.

dww’s picture

Title: Suggested changes to UPGRADE.txt » Add table of contents to UPGRADE.txt

Then the titles should be made more specific... I just happened to notice them both while looking at the core queue and immediately thought they were dupes. Thanks.

jhodgdon’s picture

I changed the other one.

ldpm’s picture

Assigned: Unassigned » ldpm
ldpm’s picture

Assigned: ldpm » Unassigned
Status: Active » Needs review
StatusFileSize
new2.07 KB

Here is a patch to the UPGRADE.txt file incorporating the above items.

rickvug’s picture

Status: Needs review » Needs work

Needs work in a few areas:

* Capitalization on the list is wrong.
* Should be tar.gz, not tar.gzs
* The instructions here don't look right:

1. Download the new module tar.gz
2. Unzip them in your site>all>modules directory. Overwrite the older ones.

These instructions are specific to updating contrib modules, not Drupal core.

crotown’s picture

In #10, the last part that was added by the patch seems incorrect/misleading. The file permissions on update.php need to be that all can read, and 644 means that the owner can write it too, which is not necessary. But this whole item needs to be clarified, since there are two reasons for trouble accessing update.php. First, is that you can not log in to the Drupal site, and in this case you need to do the steps in #10. The other reason is that the web server cannot read update.php, in which case you to make sure that the permissions on settings.php are that all can read it.

vikingew’s picture

Status: Needs work » Closed (duplicate)

I think this now can be considered a duplicate in favour of #295255: Clean-up the upgrade path: UPGRADE.txt despite being a feature request. Just let's focus the energy to get this (important) document sorted once for all.