[5.0 Beta] Data directory migration problem
This discussion was created from comments split from: [5.0 Beta] Data directory migration not finishing.
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
{"sourceDir":"[ExternalDriveDataDir]","automatic":true}
I could close Zotero, move my data directory back to the external drive, restart and all was good.
BTW: I use my own version of the WinPenPack launcher, so that the profile and data directory for Zotero are mapped to the external drive no matter what the drive letter is allocated to the external drive. This is the first time that the data directory has been changed on me.
First, Zotero shouldn't perform an automatic migration if your data directory was in a custom location, only if it was in the Firefox or Zotero profile directory. But I'm not familiar with WinPenPack, so I don't know what effect that has.
But if it does perform the migration, it certainly should then open the database in the location it just migrated it to. Are you saying that's not happening?
Should there be a warning that the data directory will be moved and to where? And should there be the ability to cancel, accept, or choose a location? The data directory (mine is ~6 GB) could be moved to a SSD without the capacity to hold the data. What would happen then?
BTW: winPenPack works like PortableApps, in that it customises the launch of an application so that it can be made portable. When using winPenPack or PortableApps the location of the data directory would point to the original data directory after re-opening Zotero, even though Zotero moved the location on install/upgrade. So long as it is known that Zotero moves the data directory when it is in the profile directory, this can be accounted for so that the data directory is first moved by winPenPack or PortableApp rather than by Zotero.
We definitely don't want to prompt in the default case, but we may be able to detect when the Firefox profile directory is on a different drive from the home directory (which could also be done with a symlink) and skip the automatic migration in that case.