Closed (duplicate)
Project:
Drupal core
Version:
7.x-dev
Component:
documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Nov 2009 at 09:44 UTC
Updated:
12 Oct 2010 at 19:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
jhodgdonThis 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.
Comment #2
jhodgdonIt 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
Comment #3
dww#228598: upgrade.txt should explain what contrib/custom modules means
Comment #4
jhodgdonThe 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.
Comment #5
dwwThen 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.
Comment #6
jhodgdonI changed the other one.
Comment #7
ldpm commentedComment #8
ldpm commentedHere is a patch to the UPGRADE.txt file incorporating the above items.
Comment #9
rickvug commentedNeeds 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:
These instructions are specific to updating contrib modules, not Drupal core.
Comment #10
crotown commentedIn #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.
Comment #11
vikingew commentedI 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.