Problem/Motivation

Steps:

1. In Drupal 7.9, sign on as administrator.
1.5. Reports > Status report.
2. In result

Drupal core update status Out of date (version 7.10 available)
There are updates available for your version of Drupal. To ensure the proper functioning of your site, you should update as soon as possible. See the available updates page for more information and to install your missing updates.

Click "available updates" link.

Actual result:

Home » Administration » Reports » Available updates

Last checked: 20 hours 16 min ago (Check manually)

Your server does not support updating modules and themes from this interface. Instead, update modules and themes by uploading the new versions directly to the server, as described in the handbook.

Expected result: "Drupal core" in place of "modules and themes"

3. Click "handbook" link.

Actual results: Links to http://drupal.org/documentation/install/modules-themes
Expected results: Links to an article on upgrading from one Drupal minor release to another.

Steps to reproduce

Proposed resolution

Add link to update instructions on admin/reports/updates/update

Remaining tasks

Before making a patch, agree of the text to be added to the page.

User interface changes

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#31 Screenshot 2022-11-11 at 13-41-15 drupal 10.0.0-beta2.png42.2 KBquietone
#7 Issue_1377816_Screenshot4.png321.74 KBTransitionKojo
#6 core_update_linkfix-1377816-04.patch922 bytesTransitionKojo
#4 Issue_1377816_Screenshot1.png324.59 KBTransitionKojo
#4 Issue_1377816_Screenshot2.png210.96 KBTransitionKojo
#4 Issue_1377816_Screenshot3.png328.28 KBTransitionKojo

Comments

charles belov’s picture

charles belov
he/him
Primary language English
Location San Francisco, CA, US
commented

Omitted step 1.5:

1.5. Reports > Status report.

xjm’s picture

xjm
she/her
Primary language English
commented
Title: Wrong action path for status report warning to upgrade on minor core release » "Available updates" link gives instructions for modules/themes even if only core needs to be upgraded

Retitling a little for clarity.

xjm’s picture

xjm
she/her
Primary language English
commented
Version: 7.9 » 8.x-dev
Issue tags: +Usability, +Needs backport to D7

And tagging.

TransitionKojo’s picture

TransitionKojo commented
Assigned: TransitionKojo » Unassigned
StatusFileSize
new Issue_1377816_Screenshot3.png328.28 KB
new Issue_1377816_Screenshot2.png210.96 KB
new Issue_1377816_Screenshot1.png324.59 KB

This issue was recreated. See screenshot 1. Clicking the "available updates" link (circled) takes you to screenshot 2.

In screenshot 2, we can see that the upgrade message (which was part of the reason the issue was filed) of:

Your server does not support updating modules and themes from this interface. Instead, update modules and themes by uploading the new versions directly to the server, as described in the handbook.

has been changed to

Updates of Drupal core are not supported at this time.

(circled).

However, a link to the Upgrade Handbook is not included but should be. The logical target for this link would be "Update your Drupal site from one minor 7.x version to another minor 7.x version". However, this document is marked as Incomplete and referes to the Upgrade.txt document included in Drupal 7.x core. See screenshot 3. It is suggested that Upgrade.txt document included with Drupal Core 7.x should also be linked to via the above upgrade message.

TransitionKojo’s picture

TransitionKojo commented
Assigned: Unassigned » TransitionKojo
Issue tags: +Novice
TransitionKojo’s picture

TransitionKojo commented
Assigned: Unassigned » TransitionKojo
Status: Active » Needs review
StatusFileSize
new core_update_linkfix-1377816-04.patch922 bytes

Here's a patch that adds a link to the Update.txt mentioned in #1377816-04: Add link to update instructions on admin/reports/updates/update. Instead of the Update.txt for D7, as mentioned in the referenced comment, it links to the core Update.txt for D8.

TransitionKojo’s picture

TransitionKojo commented
StatusFileSize
new Issue_1377816_Screenshot4.png321.74 KB

Screenshot 4 is from update.manager.inc, (core/modules/update in D8; modules/update in D7. The marked lines (553 & 556) direct the user to the same URL: http://drupal.org/getting-started/install-contrib. This is despite the text strings being for two different (but similar) errors; a server not allowing the updating vs. installing of modules from the Admin UI. This 'discrepancy' was the main issue in the now-closed #1377966: Upgrade report for modules links to wrong documentation.

The question is this: do we want the user to be directed to the most specific page of the docs available, or to the proper section?

  • If most specific, then the links in lines 553 & 556 need to be changed.
  • If linking to the proper section is considered best practice, the links can stay the same. However, the error message could (and probably should) be updated to highlight the need to look for the proper section.

I personally think the second method is better over the long run. What say you, good Drupal-folk?

Comment edited for brevity. ;-)

xjm’s picture

xjm
she/her
Primary language English
commented

Other than the fact that this comment was too long. I'm working on that. ;-)

Haha, I hate to admit it, but that was my first thought. ;) "I'll look this over when I have time to read it more closely."

TransitionKojo’s picture

TransitionKojo commented

There was a nearly identical issue at #1377966: Upgrade report for modules links to wrong documentation that referenced this issue. I closed it as a duplicate, as it's solution (see the question raised at #1377816-7: Add link to update instructions on admin/reports/updates/update) can/should be combined with this issue.

star-szr’s picture

star-szr
he/him
Primary language English
commented

Closed #1377826: Notice of minor Drupal upgrade does not link to upgrade instructions as a duplicate of this issue.

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented

In reference to the question asked in #6, I think proper section. If the links are too granular, then they are too hard to maintain with changes to the handbook. ideally, that link is put into core once and then we don't need to change it, even though the docs underneath that link might get re-organized 50 times.

kscheirer’s picture

kscheirer
Primary language English
Location Vallejo
commented
Issue tags: -Usability, -Novice, -Needs backport to D7

#6: core_update_linkfix-1377816-04.patch queued for re-testing.

kscheirer’s picture

kscheirer
Primary language English
Location Vallejo
commented
Issue summary: View changes

Added step 1.5.

alansaviolobo queued 6: core_update_linkfix-1377816-04.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 6: core_update_linkfix-1377816-04.patch, failed testing.

dawehner’s picture

dawehner
Primary language German
commented
Component: base system » update.module
Issue summary: View changes

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

quietone commented
Assigned: TransitionKojo » Unassigned
Issue summary: View changes
Status: Needs work » Needs review
Issue tags: +Bug Smash Initiative
quietone’s picture

quietone commented
Title: "Available updates" link gives instructions for modules/themes even if only core needs to be upgraded » Add link to update instructions on admin/reports/updates/update

And a better title.

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Status: Needs review » Needs work

Since beside the title change there hasn't been comment since 2013 can someone please confirm the report issue still exists.

quietone’s picture

quietone commented
Version: 8.9.x-dev » 9.3.x-dev
Related issues: +#2745855: D8 Patch release update notes are hard to find

The closest thing to a link to update instructions on /admin/reports/updates/update is a link to the Release notes. Going there, you have to read down to the second section, 'Important update information' which has a heading 'Updating from Drupal 8'. In that paragraph there is a link to the update instructions. It could be a lot simpler, and I wonder if an admin would think of clicking 'release notes' when looking for 'update instructions'.

Changing to 9.3.x and adding related issue.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Issue summary: View changes
Status: Needs work » Closed (outdated)
StatusFileSize
new Screenshot 2022-11-11 at 13-41-15 drupal 10.0.0-beta2.png42.2 KB

The release notes page now has update instructions, so this is now oudated.

Cheers