Lost hundreds of redirects upgrading from 5.20 to 6.14
edg - October 30, 2009 - 02:27
| Project: | Path redirect |
| Version: | 6.x-1.0-beta4 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | fixed |
Jump to:
Description
Upgraded my production site at www.edinburghguide.com and lost hundreds of redirects. I noticed that by default the redirects were set to purge after 8 weeks of inactivity. I dont remember this setting in previous version of Path Redirect... could this be the reason?
#1
That's odd. The upgrade should make sure to put the timestamp of when the upgrade happens as the 'last used' field for all redirects. I certainly wouldn't want people's data to be lost because of a default value. I adjusted the default to not purge old redirects.
#2
Automatically closed -- issue fixed for 2 weeks with no activity.
#3
The same thing just happened to me. From 5.20 to 6.14! The tables and data are still in the db, but nothing shows up in the module and the redirects don't work. Please help.
#4
#5
im not trying to do smart... but that is why you should always create a backup before upgrading.
#6
I have a backup. Posting a problem here has nothing to do with having a backup or not. Everything else on my site works great after the upgrade. It would be great to have this module pull the info from the database like it should.
#7
So you're saying there is still data in your {path_redirect} table? Do you see them in your admin/build/path-redirect interface?
#8
Installed on 6.14 site. All redirects are created with last used date 0000-00-00 and they disappear in cron run. I then realised the path_redirect table existed from a previous test a long time ago. I uninstalled path redirect then reinstalled. last_used became int 10 and redirects stopped disappearing.
#9
So this appears to just be a random bug that was fixed a while ago. I see nothing in the current code that should make things go wrong now. If anyone is still having problems, my suggestion would be to restore the path_redirect table from a backup, then copy the {system}.schema value for the path_redirect module entry from the {system} table's backup, and run update.php.