So I’ve had the price metadata enable, today I rebooted my computer and suddenly no price column were shown but I was still seeing the generate expense report function, but now with a blue Star…. Quitted the app and reactivated my licence and now the option for the expense report isn’t even there anymore?
What is happening? Are some functions removed from old version?
I’m 100% positive I was using the function no later then 48h ago… I’ve I lost all my metadata?
I’m not sure what is happening with your instance, but the metadata from custom metadata is stored in the extended attributes of each file, so the data is still there. I have not seen custom metadata disappear for me, so I suspect you’ve got corrupted preferences or some other issue happening.
I may not be able to help you with the other issue, but I do know that your data is not lost because of how it is stored.
According to your screenshots you registered the app with a license for DEVONthink’s Standard edition (prefix DT) but not the required Pro (DTP) or Server (DTS) license.
Yeah it’s weird… It does register as Pro (I don’t have standard).
When I’m pretty sure that when I register it says Pro on the activation window in the app, but I soon as I close and reopen, back the Pro no longer show Pro… Now I can’t do it anymore as it says it was registered less then 5 days ago so I can’t remove registration for now…
Delete the file ~/Library/Application Support/DEVONthink 3/Registration.plist
Launch the app
Enter your DEVONthink Pro license
Quit and relaunch DEVONthink
Is the app still registered? If not, then please download the app again from our website and replace the installed app with the downloaded one. Does this help?
So did the step above and managed to re-register the app with the pro licence but still did not have the data settings. Donwloaded the app again from the your account page and overwrote the app…
Now everything is back to normal, my price field is back and didn’t lose any data.
Not sure what went wrong and how but at least now it’s back to full use.
Most likely either a damaged installation or a broken code-signature due to e.g. modifications inside the application package (e.g. changes to localizations)