Sister issue to #1112518: Output version for projects "In development".

That one is nice because it provides visibility into just what "In Development" means. However, now that that data's available, it's kind of annoying to not have it for "Available" modules too. :)

So here's a patch that doesn't totally work that attempts to do that. :P~ I'm currently just grabbing the key off last element in the $project['releases'] array which is often, but definitely not always, the latest D7 release.

CommentFileSizeAuthor
#1 upgrade_status-more-specific-available-1237652-1.patch912 byteswebchick

Comments

webchick’s picture

webchick
she/they
Primary language English
Location Vancouver 🇨🇦
commented
Status: Active » Needs work
StatusFileSize
new upgrade_status-more-specific-available-1237652-1.patch912 bytes

Patch.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

You know what? I've just granted you maintainer access. We didn't talk about it, but I (obviously) trust you to do the right things. ;) Naturally expecting the same workflows and treatment of issues and changes that would also apply vice-versa if I'd be co-maintainer for core. Details are documented.

On this patch / the release number, I'm pretty confident that we should have the version number of the recommended release per project in the $projects data already. Technically speaking, the release we're searching for is just simply the currently recommended release for a project. IIRC, the property is set one level up, next to 'releases', and contains the version string to use as key.

Lastly, btw,

+++ b/docroot/sites/all/modules/upgrade_status/upgrade_status.report.inc
@@ -119,7 +119,8 @@ function theme_upgrade_status_report($data) {
         $row .= '<span class="not-current">'. t('In development: %type', array('%type' => $type)) .'</span>';
...
+        $row .= '<span class="current">'. t('Available: %release', array('%release' => $latest_release)) .'</span>';

odd, did we really name the placeholder %type in the last patch? ;)

webchick’s picture

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

Wow!! Thanks a lot, sun! I promise to use this new permission only for awesome. Mwahahaha. ;)

I'll take another look. The $projects array seemed to only include "supported major" and "recommended major" rather than an explicit version being marked recommended, but I definitely could've missed something.

And yes, yes we did. :P~ I'll clean that up, too.

kristen pol’s picture

kristen pol
she/her
Primary language English
Location Santa Cruz, CA, USA
commented
Issue summary: View changes
Status: Needs work » Closed (won't fix)

Triaging all Drupal 6 Upgrade Status issues. As Drupal 6 is no longer supported by this module and the recommended versions are shown for "Available" projects in Drupal 7, closing this.