I know that others have seen this problem before, based on the issues, but I'm experiencing it now and have been unable to figure out a way to address it. I have updated to 6.x-2.8 (even removing previous directory and downloading fresh), but it is stuck on 6.x-2.5. How can I fix this? Update.php doesn't show link at all. The database contains "6.x-2.5" in the info field for the module. Is there some kind of database or code hack that can fix this?

Comments

jcfiala’s picture

jcfiala commented
Status: Active » Postponed (maintainer needs more info)

That's an odd one. I don't have any control over the version that gets injected into the link.info file... can you do us a favor and attach the link.info file here?

ampersat’s picture

ampersat commented

The problem is not with the link.info file. That appears to be correct:

; $Id: link.info,v 1.2 2008/03/31 06:50:42 quicksketch Exp $
name = Link
description = Defines simple link field types.
dependencies[] = content
package = CCK
core = 6.x


; Information added by drupal.org packaging script on 2009-11-05
version = "6.x-2.8"
core = "6.x"
project = "link"
datestamp = "1257394550"

In the system database table, the info column that is associated with the link module is as follows:

a:10:{s:4:"name";s:4:"Link";s:11:"description";s:32:"Defines simple link field types.";s:12:"dependencies";a:1:{i:0;s:7:"content";}s:7:"package";s:3:"CCK";s:4:"core";s:3:"6.x";s:7:"version";s:7:"6.x-2.5";s:7:"project";s:4:"link";s:9:"datestamp";s:10:"1222062031";s:10:"dependents";a:0:{}s:3:"php";s:5:"4.3.5";}

I've tried manually changing it to the following (where version and datestamp are modified):

a:10:{s:4:"name";s:4:"Link";s:11:"description";s:32:"Defines simple link field types.";s:12:"dependencies";a:1:{i:0;s:7:"content";}s:7:"package";s:3:"CCK";s:4:"core";s:3:"6.x";s:7:"version";s:7:"6.x-2.8";s:7:"project";s:4:"link";s:9:"datestamp";s:10:"1257394550";s:10:"dependents";a:0:{}s:3:"php";s:5:"4.3.5";}

However, when I check for updates, it reverts back to the old data. I also tried other tweaks to the database that had no effect.

At this point, I don't know of anything else to try. Any suggestions are welcome.

ampersat’s picture

ampersat commented
Status: Postponed (maintainer needs more info) » Needs review

It occurred to me right after posting the last note that, since this is related to CCK, maybe there's something going on there. I found that, under the CCK module, there was a copy of the link module at versino 6.x-2.5. Replacing this version with 6.x-2.8 seems to have fixed the problem.

Is there anything wrong with taking this approach?

jcfiala’s picture

jcfiala commented

Hey, good job on figuring that out!

Personally, I like to keep all of my contrib modules in sites/all/modules/contrib/, at the same depth, so that it's easy for me (and whoever comes after me on a project) to find the modules and replace them. As you can see, not putting them where people expect to find the module can cause weird effects.

dropcube’s picture

dropcube commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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