I'm not sure if this is a bug or a support request. After updating from 7.35 to 7.38, the Drupal modules page continues to report that I have Ubercart version 7.35. I don't have a second version of Ubercart anywhere in this instance of Drupal. However, this instance is being run off a subdomain (foo.bar.com) while the live version, a duplicate older instance of the site, is running off the main domain (bar.com).

I have deleted and re-uploaded the Ubercart module. I have run cron and cleared my cache.

Does anyone have any idea what this might be?

Comments

TR’s picture

Category: Bug report » Support request
Status: Active » Fixed

I'm going to mark this as fixed, meaning "answered". There's really nothing Ubercart could be doing here to cause this - that information is determined by the core Drupal Update module. There are various things that could cause Update to report the wrong information; the most likely is that you have a duplicate copy of Ubercart somewhere, but this error generally indicates something is wrong on your site. A look through the system table can help you to determine where the 7.x-3.5 version of the module is being found, and you should check this even if you're sure there are no duplicates.

Note that it's recommended that you *delete* all the old code when you update a module, don't just unzip the new version on top of the old, because if Ubercart files have been moved or renamed in the updated version you'll end up with a mixture of files from different versions of Ubercart.

Aside from a duplicate module, I don't know all the causes of this error, but it's a long-standing core issue that affects all modules, not just Ubercart. There are lots of threads in the core issue queues that discuss this if checking the system table doesn't help.

mlmoseley’s picture

I just set up a clean install of Drupal 7.34 with Ubercart 7.35, updated to 7.38, and Drupal reports it as 7.35. Try it yourself.

mlmoseley’s picture

I've been a Drupal themer and developer for five years. I know how to install a module and how to update one. If you could tell me what proof I could offer you that this bug exists, I will provide it.

mlmoseley’s picture

Status: Fixed » Active
TR’s picture

Status: Active » Fixed

No one is saying that you're not having a problem . But again, this is totally outside of Ubercart control. It is the core Update module that determines what versions (of ANY module) are installed and what new versions are available. It is the release packager which inserts the version numbers into the module .info files. There is absolutely nothing that Ubercart can add or subtract or change in our codebase that will affect this process. I offered some suggestions for things you could check, but if the problem isn't in your database and you don't have duplicate copies of modules then it's a problem on drupal.org or in update.module. I seem to recall that security updates (like 7.x-3.8) sometimes confuse the Update module, but as I said in #1 I don't know all the things that cause this error. However it IS a long-standing issue that affects ALL modules, and I'm surprised you have never seen mention of this before. It crops up like every week in the forums and on IRC.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.