Ubercart Version 5.x-1.6 reports as 5.x-1.01 if uc_ratequote is installed.
naught101 - December 29, 2008 - 09:49
| Project: | Update Status |
| Version: | 5.x-2.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | by design |
Jump to:
Description
The update status module reports version 5.x-1.6 as 5.x-1.01. This means that it's constantly in need of a "security update", even though it's really 5.x-1.6 (I upgraded it twice, to be sure).
There are a large number of .info files that come in this package, and most of the have different version numbers, so it's hard to know what to change..
it would be good if all the .info files gave the same version (i.e. if one module is updated, update the version on all modules.
if this is fixed, a re-release would be good - 5.x-1.6.1 perhaps?
#1
I don't think this is a problem with Ubercart. The download of the 1.6 release contains only the correct version in its .info files. Do you have any other modules, possibly in the contrib folder that might be confusing the Update Status module? Drupal version numbers aren't supposed to have leading zeroes, nor should they have three separate version levels (like 1.6.1). And since drupal.org puts the version numbers in the .info files when a release is made, there shouldn't be any variations across all of the different contrib modules.
Try downloading the tarball again, and when you go to extract it, delete the ubercart folder first. That ought to remove any conflicts in that section, at least.
#2
If someone can point to a cause for this that we need to fix, you can reopen this issue. It looks like just a fluke to me, though.
#3
Actually, this was caused by the uc_ratequote module, which is a ubercart contributed module, and is currently at version 1.01. We had it installed in a separate directory, but it's .info file said it was part of the "Ubercart" package, so update_status was reporting the whole package as version 1.01. When we commented out the "package" line for the uc_ratequote .info file, the problem was fixed, although uc_ratequote doesn't appear in update_status now.
This is a fairly minor bug, and probably won't affect many people, but perhaps update_status's methods for determining the installed version need to be re-assesed, perhaps based on directory structure?
#4
update_status uses the 'project' attribute in the .info files, not the 'package' attribute. it can't possibly just rely on the directory tree, it has to have the right data in the .info file. That data is correct if you use an unmodified tarball that was packaged by the drupal.org packaging script, or if you deploy from CVS and use cvs_deploy. If you modify your .info files after you get them, update_status can't help you.