I purchased the license upgrade to DEVONthink4 and rushed into downloading it and installing it. I noticed v3 is still present, how can I remove it without loosing any customisations I did?
For example I have a lot of own templates saved into
So, I also rushed into installing the beta but want to keep the v.3. They can’t co-exist? If not, then what is the best procedure to uninstall v.4? I was asked to allow some Dropbox sync feature when installing beta, which I did. I’m not sure if I’ve already messed something up.
Note: you do not want to start running any kind of uninstaller utilities.
If you would rather not use the beta, you can just quit it and delete the DEVONthink application. NOT the DEVONthink 3 application, the one named DEVONthink.
Jim, I’ve paid for the upgrade, but I won’t install DT4 right now because I’m short on time for testing. Could you please explain the process for upgrading from DT3 to DT4 after its release? Will I just click on DT3 and upgrade it?
When the final version is available, you would just download 4 and launch it. If you were previously running version 3, you could merely delete the DEVONthink 3 application and reboot the machine.
In this case, is there a process to manually migrate the templates from v3 to v4?
Also what about the other items that I might have created in v3? For example, smart rules or smart groups?
You’re welcome.
Click the plus (+) button at the bottom of the Navigate sidebar in DEVONthink 4 and choose Add Default Smart Groups/Rules to reinstall our built-in ones.
After upgrading from DT3 pro to DT4, the settings in DT3 are not carried over. For example, under Files->Markdown, the Style Sheet reference, the Import images to group, etc.
Sorter, OCR settings, etc just to name a few.
How can I have the settings in DT3 move to DT4? I did a backup of DT3 before upgrading. So, if I need to copy any files from DT3, I should have a copy.
Only the most improtant settings are currently migrated, e.g. label & highlighting colors, imprinter configurations, sync setup. Custom metadata preferences unfortunately aren’t migrated due to a bug. Everything else has to be set up again, I’m afraid.