sheepcore wrote on Mar 17^th, 2013 at 3:49pm:

Thank you for the diligent work, sheepcore.

I noticed that funky checkbox myself for the first time this morning.  But since it was not switched ON for me, and our plugin worked fine for me, I didn't mention it.  It turns out that this checkbox is another recent security addition to Chrome, and apparently you have some combination of security settings and possibly the first web page that opens when Chrome launches which disallows plugins unless they are specifically always allowed.  Or something like that.  I began reading Google's  documentation on this topic,

http://support.google.com/chrome/bin/answer.py?hl=en&answer=142064

but my head began to spin, because there are so many settings it would take quite a while to construct the tree of possibilities, if that was even possible.  Rather than do that, since we know that Google's security meisters tend to re-tweak stuff like this frequently anyhow, we added some code to the next version of BookMacster such that BookMacster now switches ON the setting underlying this Always allow checkbox as part of its plugin installation.  And it removes it as part of uninstallation.  In other words, we're brute-forcing it.

Other users should therefore not have this problem after BookMacster 1.14 is published.  Thanks again.

EDIT [2013-Mar-19]  BookMacster 1.14 is now published and is available to users subscribed to beta builds.

sheepcore wrote on Mar 17^th, 2013 at 7:06am:
It's only enabled if not installed, or after a test failure.

sheepcore wrote on Mar 17^th, 2013 at 7:06am:
Very strange.  First of all, let's see if Chrome thinks the components are installed.  Please activate Chrome and verify that we're in the list of Extensions and Plugins, as shown here…



If those are OK, then see if our plugin is presenting its port.  To do that,

• Leave Chrome running.
• Activate Finder.
• Click in the menu: Go ▸ Utilities.  A window will open.
• Find and doubleclick to launch Terminal.app.
• Copy and paste this command into the window…
   sudo launchctl bstree | grep sheep
• Enter an administrator password when prompted.
• Verify that the system indicates our ToClient port is active by printing A followed by its name…
   A  com.sheepsystems.BookMacster.ExtoreChrome.Default.ToClient
Thanks again.  Let us know what you find.  Copy and paste in that whole result from Terminal.app if you get any.

Hi,

The install button is not enabled, only uninstall and test, the plugin says '84 (Ok)'.

Uninstalling the plugin, quitting Chrome and testing it again it fails again with "No response from Chrome" and the plugin saying '84 (Ok)', extension

I then again uninstalled plugin, extension and toolbar icon and reinstalled each ... 15 (Ok) (Not Loaded), 11 (Ok), 84 (Ok) ... still the test fails with the same result as before when Chrome has been opened and the test executed.

:/

Having updated Bookmacster (1.13.6) and the Chrome (OS X 10.8.3 / 25.0.1364.172 release version) extensions to the latest version the Browser addons test from Bookmacster still fails ...

• 'Waiting for Chrome ...'
• 'Quitting Chrome ...'
• 'No response from Chrome'

Let me know if any additional info might help you to repro and fix the Chrome sync.

sjaakaq wrote on Feb 22^nd, 2013 at 6:46pm:
I think that probably the export to Chrome is succeeding, while Chrome is quit, and the error occurs after Chrome is relaunched, and BookMacster needs to ask if there are any other changes, or maybe it occurs much later.

Since you only have one profile, I don't know of any issues that would cause the plugin to constantly fail.  But in a couple days we're going to publish BookMacster 1.13.6 which replaces both the extension and plugin, fixing a number of issues, and conforming to Google's September 2013 Content Security Requirements.  Please import from and export to Chrome manually, with Chrome quit, until then.

Thanks!

sjaakaq wrote on Feb 22^nd, 2013 at 6:46pm:
Hello, sjaakaq.  Well, our Chrome Plugin is definitely not working for you.  Besides the test failure, that is also indicated by the "Port Send Failed" error.

sjaakaq wrote on Feb 22^nd, 2013 at 6:46pm:
We need to distinguish between Chrome and Google Bookmarks.  These come out of different buildings over in Mountain View.

How many choices in the Clients popup begin with the word Chrome?

Each Chrome choice should be followed by a profile name, which is in parentheses.  What Chrome profile names do you see, besides First user?