If you patch a module locally to fix an issue, there doesn't seem to be anyway of marking this satisfactorily. I append '-patched' to the version string in the .info file so I know it's been done, but then Update Status tells me to download the current version (the one that's been patched, very often). It would be nice if there were some way of doing the following:

* If the patched version matches the latest version apart from the suffix, mark the entry as having been patched.
* if there's a newer version, mark the entry as requiring an update and possible reconciliation.

Comments

As If’s picture

As If commented

I do something similar with the Description string in the info file, this shows up on the Modules page so later proggers can tell which modules will need special attention before upgrading. But the Update Status report is another place that needs a similar note. The best solution for now is to do a theme override on theme_update_report(), which you can find in update.report.inc. Since I happen to use three asterisks (***) as my notes indicator, my overriding function includes this conditional output:

if (substr_count($project['info']['description'],"***")) {
  $row .= '<br><span class="debug">*** MODIFIED/DO NOT UPGRADE</span>';
}

Edit as desired to create a handler for your own notes. You probably want to put it between lines 91 and 107 (from the original function). That's the "project" div.

But still - it would be GREAT if the module could do this internally. Or alternately, it would be nice if we could set the Notification Threshold differently for different modules.

dww’s picture

dww
we/he/they
commented
Status: Active » Closed (works as designed)

There's a "Settings" tab on the Available updates report page, you know? ;) That let's you ignore specific versions or entire modules, and it gives you a space to write a note to yourself about why you're ignoring it (which is displayed on the available updates report).

I don't understand what else y'all are asking for here...

As If’s picture

As If commented

These individuated module specification features must be new in 6.12, and they do sound like what I was asking for. I don't see any module-specific controls under the "Settings" tab in 6.10 (the version I was building on when I posted on March 4). But I also note that the original poster was talking about D5.

dww’s picture

dww
we/he/they
commented

In D5 the features lived directly in update_status module.

As this code was moved into D6, Dries complained that these settings were "too complicated" for core, so they continue to live in contrib:

http://drupal.org/project/update_advanced