Bearing in mind the OS landscape was different in 2011, yes I would say that advice could be considered obsolete. I would suggest creating a folder for your databases in the root of your User Account instead of Documents. This way they would be in a safe place should you decide to turn on the disk management feature of Sierra, or if the next macOS release they decide it’s not a Users’ choice to make.
(And yes, if they decide to sync all our data without our choice, (1) we’ll have some more work to do, and (2) I will stop using Macs )
would you or other staff-members kindly and simply answer those questions put forward here, namely:
For many of us DTPO is the trusted system of our workflows.
But all of the sudden important features are broken (e.g. handling and displaying PDFs) and thus reported as broken … and no-one of the staff-members so far (at least as far as I see) has stood up and stated clearly what to do and what not to do (in order to avoid data-loss e.g. due to scan-snap problems) and most importantly communicate reliable information when DTPO update 2.9.5 (which seems to be supposed to fix all this) is going to be available. It was to be released last month, i.e. September(!) - as some of the staff-members wrote in this thread.
So guys. Get your act together and tell us when DTPO 2.9.5 ist going to be available?
Devonthink was too important to me to risk an upgrade to Sierra until the .1 or .2 release. Glad I didn’t.
I have however installed it on one of my mac minis to test Every app I have that relies on pdfkit for anything but display seem borked in some way. Most are unlikely to get fixed either because the cost of working around pdfkit’s bugs is not worth for the limited return for small developers.
I wonder if the changes to pdfkit came very late in the Beta or wasn’t properly documented because it seems to have caught every developer off guard (Fujitsu only warned of the problems the day before the final release.)
Every app I have that relies on pdfkit seem borked in some way. Most are unlikely to get fixed either because the cost of working around pdfkit’s bugs is not worth it for the limited return for small developers.
Apple took one of the most stable frameworks in the OS and broke it (without seemingly documenting what they broke)I think its rather unfair to call out DT developers on this especially with the brilliant release of DTTG and when they have said they are working on a fix. I doubt the fixes are straightfoward from Christian’s comments on these forums and from what I have heard from other developers.
First thing I noticed though is that it is no longer possible to remove single pages from a PDF; the menu item is greyed out.
I use this function quite often (I even made a keyboard shortcut for this).
Will this function come back anytime soon or will it be necessary to use preview.app for this?
Generally, they kindly respond to actual technical questions. You do not have a right to an answer on this one. It’s irrelevant to you how they go about things internally, only the public facing outcome is of importance. Betas are shifting targets.
Furthermore it’s a trick question:
Answer “yes, we did” -> so how did you miss this, what kind of devs are you?
Answer “no” -> What kind of devs are you?
Answering this is a lose/lose situation for the DT folks.
Why are people upgrading critical production machines to Apple’s latest and greatest on day one, even week one? And they even get quite offended and scornful when something doesn’t work under an OS beta release.
While I upgrade iOS typically within a few weeks after release (when it is clear that there is no major “bricking” scenario, or a fatal incompatibility with my personal killer apps), OS X is much trickier and I wait it out to a “.1” release or so. Users with a large installed app base generally face numerous issues, not just DT. Some of the biggest offenders are sometimes Apple apps. With El Capitan, Mail was unable to migrate my 30 GB mail folder to the “new format”. Totally screwed up. I had to revert to the Yosemite install swiftly. After two months and some minor releases, that finally worked. Or the way the /usr/local/ folder was migrated in the Yosemite upgrade, causing update times of nearly a day for people with large TeX installations.
The PDFKit code in the OS has been stable for a long time, and used by many Mac apps to create/view/edit PDFs. Changes to PDFKit in Sierra broke the some of the ability of many third party apps to manage PDFs, in some cases, as noted by Fujitsu, resulting in modification or even data loss in some previously scanned files.
Apple provided developers prereleases of Sierra as well as a public beta program prior to the final release, with many changes during that period including a second Gold Master version. Apple received feedback from developers and beta users, including problems with PDFs. IMHO, the feedback should have indicated to Apple that inclusion of the revised PDFKit code in the first release of Sierra would be premature. It resulted in too many problems for a number of apps, without adequate time to resolve them.
DEVONthink 2.9.5 is not a Sierra-only release. It remains compatible with recent versions of OS X, and includes a number of features useful to users still running OS X (as I am, until ScanSnap Manager is updated) as well as to users under Sierra. That means, with respect to PDFs, that it works with the previous code of PDFKit and the new code – which is important. It also means extra work for the developer. While many PDF issues in Sierra are resolved in this release, some issues remain.
Yes, communication is important. I always recommend reading the release notes for a new version of DEVONthink, and that is especially important in this case. Please look at Help > Release Notes in DEVONthink. (There’s also critically important information for those using Sync, related to the location of DEVONthink databases.)