upgrade.txt should explain what contrib/custom modules means [#228598]

Comment	File	Size	Author
#9	228598.patch	788 bytes	nvahalik
#8	228598.patch	789 bytes	nvahalik
#7	228598.patch	791 bytes	nvahalik

Comment #1

keith.smith commented 29 February 2008 at 23:35

Title:	Suggested revisions to Upgrade.txt for version 5 and 6	» Suggested revisions to Upgrade.txt
Project:	Documentation	» Drupal core
Version:		» 7.x-dev
Component:	Installation	» documentation

Moving to Drupal core (documentation) as this contemplates a change to UPGRADE.txt. And, resetting the version to 7 -- patches are first worked out in the current HEAD version and then backported as necessary.

Log in or register to post comments

Comment #2

keith.smith commented 29 February 2008 at 23:42

On the need for the change itself, does the confusion in the first case arise from not knowing what is or is not a "contributed module"? UPGRADE.txt says that all contributed modules should be disabled; by definition, no core modules (either required or optional) are contributed modules. But, I can see this possibly be confusing to someone -- as the issue you referenced indicates -- that is not familiar with the Drupal usage of "core" and "contributed".

On the Clean URLs issue, I'm not aware of an issue here with upgrading (but there may well be one). If there is a concrete issue that you can point to, then we should possibly handle it in a separate issue (and keep this one specific to your first item).

Log in or register to post comments

Comment #3

Thomasr976 commented 1 March 2008 at 00:04

Keith,

Thanks for the prompt response.

I think that anyone who is relatively new may not fully appreciate the distinctions between Core and Contributed modules. I guess what confused me was the idea of Core - Basic and Core - Options. I was having problems with my upgrade. As you know, when that happens, one slows down and scrutinizes everything. The upgrade.txt is the bible for me and should have the necessary specificity for several audiences including newbies.

I still consider myself a newbie even though I have been learning Drupal for a couple of months. So anything that is very specific is helpful and will be beneficial. Some will have very little experience and want to upgrade to a different version just to see how easy it is.

Whatever you think is appropriate with the second issue is fine.

On the issue of Clean URLs, that seems to be relevant only when one is upgrading and moving site to another location. See http://drupal.org/node/220600#comment-726297. As I have not done this yet but will soon, I thought it might be a relevant.

thanks

Log in or register to post comments

Comment #4

jhodgdon

she/her

English

commented 15 March 2010 at 16:33

Clean URLs and moving to a different site -- that is not relevant to upgrade.txt, which is discussing how to upgrade to a new version of Drupal on the same site.

Regarding disabling modules... The Drupal 7 version of UPGRADE.txt says:
5. Disable all custom and contributed modules.

It sounds like there could be confusion because people don't know what "custom and contributed" means. I think this is valid, since the Modules pages talks about "Core - required" and "Core - optional" but doesn't say "contributed" on other modules. So we could change that to

Disable all custom and contributed (non-Core) modules.

Or just

Disable all non-core modules.

Thoughts?