Closed (fixed)
Project:
Redirect
Version:
7.x-1.0-rc3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
28 Jul 2015 at 13:27 UTC
Updated:
13 Feb 2020 at 00:16 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidCommitted some changes to redirect_update_7101() to make it compatible with running more than once. Try the 7.x-1.x-dev version in a couple of hours to see if this resolves it.
Comment #3
hayzer commented7.x-2.x-dev worked. I will test again with 7.x-1.x-dev once available.
Comment #5
hayzer commented7.x-1.x is working.
Comment #7
breezeweb commentedI'm still seeing this problem with 7.x-1.x-dev.
Update: I can confirm that the latest patch committed does indeed fix it after all.
Comment #8
sonicthoughts commentedComment #9
dave reidComment #10
yan commentedI had the same problem with 7.x-1.0-rc3, but 7.x-1.x-dev does work. I hope there will be a new release some time soon. Thanks Dave Reid.
Comment #11
carolpettirossi commentedI had the same issue using the 7.x-1.0-rc3 module. When I used 7.x-1.x-dev worked properly.
Comment #12
philsward commented+1 for a new RC release
Comment #13
paulvandenburg commented+1 for the new RC release
Comment #14
paulvandenburg commentedIgnore this.
But I'm adding the commit from #4 as a patch here.
Because d.o does not allow me to create a release of my distribution, see #3089916: Fix redirect issue where the update hook fails forever if a status field is already present since the git.drupalcode.org domain is not trusted.
I'll open a infrastructure issue for that but in the mean time I can continue with this. If others are strugling similarly see attached ;)
This is just a download of the plain commit diff here: https://git.drupalcode.org/project/redirect/commit/c00142f39ebb25678edfd...
Comment #15
joshuautley commentedRegarding #14 - Is an uninstall recommended in order for this patch to work?
Comment #16
paulvandenburg commented@joshuautley an uninstall should not be necessary. If you encounter the problem of this issue this update hook should never complete. So after applying the fix it should reattempt this update hook which should now be fixed.
So it should just work if you apply the fix here (either apply patch #14 or update to a release that includes this fix).
Comment #17
joshuautley commentedRe: #16 It only works if I uninstall the module and then reinstall after I've applied the patch. Prior to that I applied the patch yet the error continues to be displayed each time I run update.