Thank you, Pat. I reproduced the problem and found good and bad news.
The good news is that I immediately realized what the problem was and fixed it in 5 minutes. We have now built and published BookMacster 2.0.1 which has the issue fixed. Anyone with BookMacster 2.0 can get 2.0.1 by clicking in the BookMacster's menu: BookMacster > Check for Update.
The bad news is that the fix was to disable a
new security feature introduced by Apple which is effective for apps built with their latest tools (which BookMacster 2.0 is but BookMacster 1.x was not) when running under OS X 10.11 (which apparently you are). Apple does not like the idea of apps visiting "non-secure" websites. "Non-secure" means any website whose URL begins with
http: instead of
https:. The way I fixed it was to, uh, add a "key" to the BookMacster package indicating that BookMacster is
opting out of this new feature.
Yuck. This is not a good long term solution, given the fact that Apple's pattern with new security "features" is to initially make them opt-in, then the next year make them opt-out, then the next year it's Apple's way or the highway.
Actually, Apple's idea is not a bad one. Nowadays, many websites, even our little sheepsystems.com for instance, have upgraded and can accept https: connections. I mean, you can get to us using either
http://sheepsystems.com or
https://sheepsystems.com. So maybe we should combine the old Verify feature with a new feature to
upgrade your bookmarks, by, well, adding an "s" after "http". Sites which cannot accept https will need to be skipped during Verify. Well, anyhow, we've probably got a year or so to think about it.