Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This morning Updates reported:
Link 6.x-1.x-dev (2008-Nov-24)
Recommended version: 6.x-1.x-dev (2009-Feb-26)
After drush updating I tried to run update.php, receiving the following warning:link module can not be updated. Its schema version is 0. Updates up to and including 1 have been removed in this release. In order to update link module, you will first need to upgrade to the last version in which these updates were available.
I am not sure how to proceed (and I do not see a dev version in the project page). Please advise. Thank you
Comment | File | Size | Author |
---|---|---|---|
#26 | link.install.patch | 380 bytes | BWPanda |
#25 | linkupdate.patch | 1.12 KB | RobLoach |
#11 | link.tar_.gz | 16.7 KB | jcfiala |
Comments
Comment #1
quicksketchHmm, what version are you updating from? The update_1 function was the 4.7 to 5.0 upgrade I believe.
Comment #2
asb CreditAttribution: asb commentedConfirming, the same happened to me on two sites. Upgrade from 6.x-1.x-dev, neither drush nor update_status gives more details. Installed was, according to link.info:
After manually upgrading to 6.x-2.5 the problem was gone.
Greetings, -asb
Comment #3
skizzo CreditAttribution: skizzo commentedHaving just few link items configured, I just uninstalled and then installed 6.x-2.5 (2008-Sep-22) from
scratch. I did that manually, as drush would default to installing 6.x-1.x-dev. Is that intentional?
Comment #4
quicksketchIf you completely uninstall and then re-install the module, you shouldn't need to run update.php at all. It should simply start at the latest schema.
Comment #5
skizzo CreditAttribution: skizzo commentedyes. In #3 I just described what I did to fix the problem described in #1. I then wondered why I was running 6.x-1.x-dev in the first place (instead of 6.x-2): the reason is that on first installation "drush pm install link" picked up the latest 6.x-1.x-dev version. If that is the intended behaviour then please close the issue. Thank you.
Comment #6
quicksketchTo explain the second issue, link's tagging is a little screwed up. The release is tagged as a 2.x version, but the code is actually still in the 1.x CVS branch. It should be branched into the 2.x branch, but since it makes no difference to end-users (except those checking out from CVS) I haven't bothered to change it.
Comment #8
j0rd CreditAttribution: j0rd commentedSame issue. Just upgraded from 6.2.5 to 6.2.6-beta1
Comment #9
jcfiala CreditAttribution: jcfiala commentedInteresting - sorry, didn't know about this being there.
It sounds like I should try creating a link_update_1() function that doesn't actually do anything, for backwards compatibility. I'll look into it this week for inclusion in the actual 2.6 release.
Comment #10
giggler CreditAttribution: giggler commentedgot the same error when upgrading from 6.x-2.5 to 6.x-2.6-beta1. Luckily I still had a copy of 6.x-2.5.
Comment #11
jcfiala CreditAttribution: jcfiala commentedHere's a version of link that includes a noop link_update_1 - try this version and see if it updates for you?
Comment #12
jcfiala CreditAttribution: jcfiala commentedOkay, I've added a noop link_update_1() - it won't do anything, but should prevent this update warning problem.
Comment #13
searosin CreditAttribution: searosin commentedThere is still a problem with it. I can update the module from 6.2.5 to 6.2.6 - beta1, but on the status report page there is an error warning after update:
"Database updates Out of date
Some modules have database schema updates to install. You should run the database update script immediately."
I ran update.php several times, but nothing has changed.
I tried the original and the one in #11, same result.
Comment #14
sgriffin CreditAttribution: sgriffin commentedConfirmed, same issue.
Installing the dev version of Link causes a chronic "Database updates Out of date"
Comment #15
XerraX CreditAttribution: XerraX commentedsame problem here, waiting for a solution :-)
Comment #16
snorkers CreditAttribution: snorkers commentedI just did the same on a D6.11 site upgrading from 2.5 to 2.6beta1 - thank goodness for Time Machine - could not run update.php at all with the most recent download.
Comment #17
Dre the Enigma CreditAttribution: Dre the Enigma commentedI'm having the same problem with the latest security upgrade. Has there been any headway on this?
Comment #18
tizzo CreditAttribution: tizzo commentedSame issue, rolled back to the previous release and all is well.
Comment #19
jcfiala CreditAttribution: jcfiala commentedI'm aware there's a probelm with the beta1 for some people - I tried to fix this in the dev release that's on the page now, but it doesn't seem to fix all of the problem. I'm hoping to work on this soon, but unfortunately personal things have prevented me from following up yet.
Comment #20
Aibehn CreditAttribution: Aibehn commentedSame issue here
Comment #21
ravik CreditAttribution: ravik commentedgot the same error after upgrade from 6-2.5 to 6-.2.6-beta
Comment #22
vasikesubscribe
Comment #23
tim.plunkettCVS fails so hard on the link module. Please tag the DRUPAL-6--2 branch properly!
Comment #24
catofcheshir CreditAttribution: catofcheshir commentedWarning is gone when i comment out
function link_update_last_removed() {
return 1;
}
in link.install
Comment #25
RobLoachSubscribing and pushing to a critical bug. This helps, but more testing would be great.
Comment #26
BWPanda CreditAttribution: BWPanda commentedRob's patch from #25 didn't work for me (applied against 6.x-2.6-beta1)...
Made the attached patch instead...
Update.php runs properly after applying patch.
Comment #27
RobLoachSorry, I neglected to mention that the patch was built against DRUPAL-6--1.
Comment #28
luckysmack CreditAttribution: luckysmack commentedI had the same problem when upgrading from 6.5 to 6.x-2.6-beta1, applying the patch in #26 worked for me (did not apply patch in #25) and i have no errors when running 'drush updatedb' or running update.php in browser. Im marking as reviewed until patch is fixed and commited. thanks Rob & BWPanda
Comment #29
wickwood CreditAttribution: wickwood commentedI too had the problem when upgrading from 6.5 to 6.x-2.6-beta1. Since it was a new site with no content yet, I just did a complete uninstall and then installed the newer version.
Comment #30
jcfiala CreditAttribution: jcfiala commentedHey guys, thanks for all the help. I'm going to make a beta2 really quickly that contains this patch - I'm sorry for the delay on following up, but I sort of was blindsided by a big project here at work.
Comment #31
jcfiala CreditAttribution: jcfiala commentedThis is released as link-2.6-beta2, I believe this is fixed with the addition of the patches above.