quicksilver / GoogleChrome-qsplugin

Quicksilver Google Chrome plugin
17 stars 3 forks source link

Not working with new Beta 71 version. #13

Closed stephenturner closed 11 years ago

stephenturner commented 11 years ago

Updated today, no longer works with the new beta 71 version. My workaround is using Xmarks to sync to Firefox, then use the Firefox module. Looks like the catalog entry for the plugin is empty.

Screen Shot 2013-01-23 at 12 19 33 PM

Screen Shot 2013-01-23 at 12 19 48 PM

ndreas commented 11 years ago

This might be the same problem as described here: https://github.com/quicksilver/Quicksilver/issues/1266

Could you try and download a more recent plugin from here: http://cl.ly/1Y0e1s0E0V2h and tell me if it works for you. A warning though, that version of the plugin causes hard crashes of Quicksilver for some users. It was actually released publicly last week, but retracted again when it was clear it caused crashes.

stephenturner commented 11 years ago

Andreas- the new version works for me and now indexes my chrome bookmarks. So far no crashes. Please let me know when a stable version is released. Thanks.

Stephen

On Wed, Jan 23, 2013 at 12:48 PM, Andreas Johansson < notifications@github.com> wrote:

This might be the same problem as described here: quicksilver/Quicksilver#1266https://github.com/quicksilver/Quicksilver/issues/1266

Could you try and download a more recent plugin from here: http://cl.ly/1Y0e1s0E0V2h and tell me if it works for you. A warning though, that version of the plugin causes hard crashes of Quicksilver for some users. It was actually released publicly last week, but retracted again when it was clear it caused crashes.

— Reply to this email directly or view it on GitHubhttps://github.com/ndreas/GoogleChrome-qsplugin/issues/13#issuecomment-12612325.

sulrich commented 11 years ago

@ndreas thanks for the more recent plugin. that worked for me as well.

markf commented 11 years ago

Worked for me as well.

studgeek commented 11 years ago

@ndreas, could you bump the version info in the manual 1.1.5 so Quicksilver doesn't always prompt to install 1.1.1 over it? Thanks!

ndreas commented 11 years ago

I'll see if I can find some time do fix the bump tonight. I have another fix to do, so I'll probably make a 1.1.6 with the proper build number. I'll post it here when it's done.

ndreas commented 11 years ago

1.1.6 can be found here: http://cl.ly/0x151z3B402R

It has a build number that won't make QS prompt to install 1.1.1.

bumpux commented 11 years ago

Awesome. Thanks @ndreas

stephenturner commented 11 years ago

Looks like this isn't indexing bookmarks again. Any idea?

ndreas commented 11 years ago

Strange. Are you sure that you're running 1.1.6, and do you see anything in Console.app that relates to Quicksilver and the bookmarks?

You can force a rescan of the bookmarks if you open Quicksilver preferences and go to Catalog->Plugins->Google Chrome and press the refresh button in the bottom right corner of the window. When you do that, errors, if any, should appear in Console.app.

bumpux commented 11 years ago

1.1.6 appears to be running well for me and is indexing bookmarks.

stephenturner commented 11 years ago

I just downloaded 1.1.6, renamed the file to .qsplugin, opened it, but it doesn't appear to have installed. Not sure what to do here.

stephenturner commented 11 years ago

Went back and downloaded 1.1.5 and that worked for me. I'm afraid it will try to "upgrade" me back to 1.1.1 though.

stephenturner commented 11 years ago

Sorry for multiple posts. This came up in console:

2/15/13 3:49:32.726 PM Quicksilver[35236]: Failed to install plugin /Users/sdt5z/Downloads/GoogleChrome-qsplugin.1.1.6/GoogleChrome.qsplugin, no bundle ID

ndreas commented 11 years ago

You shouldn't need to rename anything. I seem to recall someone having this problem before. Try this zip file instead: http://cl.ly/3E2u0s2q121j

I think the problem is that something is not extracting both the bzip2 and the tar archive.

stephenturner commented 11 years ago

Works perfectly. Thanks. Strange - was decompressing with unarchiver instead of tar.

ndreas commented 11 years ago

Great. I think I need to ditch my Linux heritage and do the releases using zip files instead :)

Since everyone seems OK with the changes in 1.1.5/1.1.6, I'll close this. Thank you all for the feedback, I really appreciate the help.

studgeek commented 11 years ago

I may be the one who had a similar problem, it came from which tool I used to uncompress the file. When I switched tools (to the QS one) it worked.