I have the latest version of Custom Breadcrumbs installed ( 6.x-2.0-beta3).

I keep a local site where I make changes, then use GIT to push them to the live site (actually Git + a post-receive hook, but that's not the point).

On my local site, /admin/reports/updates shows that Custom Breadcrumbs is the 6.x-2.0-beta3 version.

On my live site, /admin/reports/updates shows that Custom Breadcrumbs is the 6.x-2.0-beta1 version.

I ftp'd into the live site and verified that the info file in the Custom Breadcrumbs module and each sub-module is 6.x-2.0-beta3.

On the live site, when I go to /admin/build/modules/list and expand the Custom Breadcrumbs section, Custom Breadcrumbs Identifiers shows it is 6.x-2.0-beta3, but the other associated modules say they are 6.x-2.0-beta1.

Breadcrumbs works correctly, it just is reporting the wrong version of the module as being installed.

I need to mention that to get my local site, I copied the files/database from the live site, then I made the repository and set up everything. This reporting the wrong module version has been this way since I took over the site in April 2010.

Any ideas or suggestions greatly appreciated.

Comments

zbricoleur’s picture

Is this site part of a multisite installation? If so, are there copies of this module in both /sites/all/modules and /sites/yoursite.com/modules?

mpruitt’s picture

Just one single site. Great thought, though.

mpruitt’s picture

I only have a single site, but the thought that multiple copies of a module would result in Drupal finding/using both for updates gave me an idea.

First, I disabled all of the modules for custom_breadcrumbs. Next, I backed up the database tables and then uninstalled them. Then I deleted the modules.

When I went to /admin/build/modules/list, I saw there were still 6 of 7 custom_breadcrumb modules (beta1 version) listed! So, now I knew there was another set of the module installed somewhere.

I'm using a Ubuntu server, so at the command prompt I typed:

find / -name "custom*"

I looked through the short list that was returned, found where the extra modules were, and removed them from my site.

Next, I re-uploaded custom_breadcrumbs, enabled the modules, and restored the relevant tables from the backup I did. After I ran the update.php script, I again went to /admin/build/modules/list, and this time, all of the custom_breadcrumbs modules were up to date!

So, zbricoleur, you didn't hit the nail right on the head, but it was a great nudge in the right direction. You get full street cred!

It appears that what happened is at sometime in the past, either myself or a co-worker misfired an ftp upload to the wrong directory.

Doh!