To help new users, the admin/reports/updates page could include some help about how to upgrade modules.
I've attached a patch which adds the following text:

"To learn more about upgrading modules, see Upgrading Drupal modules."

CommentFileSizeAuthor
#7 update-276415-7.patch1.38 KBmcjim
update_link_to_upgrading_help.patch1.28 KBmcjim

Comments

dww’s picture

dww
we/he/they
commented

A) Seems like we should use a path alias for whatever page we're pointing to.

B) The status report shows you info about themes, too -- not sure if we need to do anything about that. The referenced page is clearly specific to modules. Seems like the upgrading-themes case isn't nearly as well documented anywhere, but perhaps it should be. Maybe the referenced page could explain both and the help text here could be edited?

Otherwise, I have no objections.

catch’s picture

catch
he/him
Primary language English
commented

6.x-7.x theme update documentation is here http://drupal.org/node/254940

Wouldn't be a bad idea to link to both from somewhere, although themes don't show up on this page do they?

dww’s picture

dww
we/he/they
commented

@catch: Themes show up on that page in D6 and beyond, now that themes have .info files, too. However, that page you link is the page for theme developers to port their themes to a new core API. This issue is about help for end users on how to upgrade a module or theme that's listed as out of date by Update status. ;)

catch’s picture

catch
he/him
Primary language English
commented

Ohhh, I thought that was a weird link to put in. Please ignore me :)

In that case, it'd definitely be a good idea to add theme upgrade information somewhere prominent in the handbook (if it's not there already), and have that on this page too. I imagine most users update themes much, much less frequently than modules, and hack them to pieces too, so would need to be worded carefully.

mcjim’s picture

mcjim commented

Using a path alias would be sensible.
Currently http://drupal.org/upgrade refers to upgrading Drupal itself. http://drupal.org/upgrade/modules is not in use, nor is http://drupal.org/upgrade/theme. http://drupal.org/update/modules and http://drupal.org/update/theme are in use and are for developers.

dww’s picture

dww
we/he/they
commented
Status: Needs review » Needs work

Seems like we should move http://drupal.org/node/250790 as a child of http://drupal.org/upgrade and give it a path alias of http://drupal.org/upgrade/module. Then, someone should add another child page there for info on upgrading themes, and we'll give that the /upgrade/theme alias. Either way, we should be consistent with the aliases (unlike the developer update docs!!!) so that it's always singular or plural, but not a mix.

mcjim’s picture

mcjim commented
StatusFileSize
new update-276415-7.patch1.38 KB

I've re-rolled the patch to include a link to (non-existent) http://druapl.org/upgrade/themes
The text now reads:

To learn more about upgrading modules or themes, see Upgrading Drupal modules or Upgrading Drupal themes.

I've stuck to using the plural for both, to match http://drupal.org/project/modules and http://drupal.org/project/themes

So, now the aliases need to be set up, and in the case of themes, the documentation needs to be written.

vlad.leo’s picture

vlad.leo commented
Status: Needs work » Closed (fixed)

I think that users can understan how install new modules
And path admin/reports/updates for Available updates only

dww’s picture

dww
we/he/they
commented
Status: Closed (fixed) » Closed (won't fix)

We haven't added help about upgrading modules and themes to admin/reports/updates. If you're arguing we don't need to add such help, then the proper status for this issue is "closed (won't fix)" since we decided not to add this feature. I tend to agree. It's obviously not going to happen in D6 due to the string freeze. D7 has an update manager to just automate the process for users who don't know how to do it themselves from the command line.

Cheers,
-Derek