To be clear this isn't exactly a bug but it also isn't really a new feature.

Usage/background/reasoning:
Client has a site with a module, that has a bug that has been fixed in git but hasn't had a fix released yet. The client is adept enough to run upgrades etc. but not to apply patches and is uncomfortable with installing stuff from git. So client gets me (or other developer) to install version from git or just apply the specific patch of import. Then I change the version number so that anyone who has a bug knows that it is not as shipped. Fine however that leaves two choices: disable updating for that module or have to make sure that all users that may have updating permissions know not to update it and remember.

So what I've been doing is (for example) adjusting version number to 7.x-1.0-PatchNW instead of 7.x-1.0. Then update manager wants to update that to 7.x-1.0 which is clearly not an update. So what I've done on a lot of the Drupal installations I manage is the attached patch. Basically instead of checking if the current_version equals latest version it checks if the current version is greater than or equal.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

NWOM’s picture

Status: Active » Needs review
solideogloria’s picture

Category: Bug report » Feature request