Thanks for the info.

My guess is that Quicksilver incorrectly deleted the core support plugin
from within Quicksilver.app as opposed to the one in your library support
folder.

If you follow these steps, do things work:

1. Delete the plugin in your library support folder
2. re-download and re-install Quicksilver from http://QSApp.com

2011/10/26 R <[email protected]>

> Hi -- I read this thread and did an experiment. I had a core plugin in
> my library support folder and after quitting quicksilver, deleted it.
> When I turned in quicksilver again, it started fine but could not read
> any of my custom catalog entries, and also seemed to be lacking many
> default entries in the 'catalog' section of the preferences. My custom
> entries were there, but unclickable. I quit and restarted QS a couple
> of times, but there was no improvement. Finally, I restored the plugin
> and it is working fine, again. FYI, the version number on my core
> plugin, as seen in the Finder info window, is 0.5.2.
>
> On Oct 25, 11:57 am, Patrick Robertson <[email protected]>
> wrote:
> > OK, great troubleshooting!
> >
> > It's brought up a problem I guess with deleting plugins. For the next
> > version, we need to incorporate a check before deleting plugins to make
> sure
> > they are NOT in Quicksilver.app.
> >
> > Could you make an issue along the lines of 'Quicksilver should check
> before
> > deleting plugins within Quicksilver.app (core support)'
> >
> > Thanks!
> >
> > On 25 October 2011 16:53, Guy Manchester <[email protected]> wrote:
> >
> >
> >
> >
> >
> >
> >
> > > Ok, so I've just re-downloaded Quicksilver β61 & it seems there is a
> Core
> > > Support plugin present in this App.
> >
> > > So that's another one explained. Well done all. Very curious that it
> was
> > > stripped out of the original App I downloaded. I was one of the first
> people
> > > who downloaded it as I was watching twitter when Phil announced it's
> > > release. I've never looked at the Contents of Quicksilver.app before so
> I'm
> > > sure I didn't remove it intentionally or accidentally. There's no check
> that
> > > runs at startup is there that looks to see if there's a Core Support
> plugin
> > > in ~Library/Application Support/Quicksilver/Plugins & if yes removes it
> from
> > > /Applications/Constents/Plugins I guess? Only thing I can think of.
> >
> > > On 25 Oct 2011, at 16:31, Rob McBroom wrote:
> >
> > > On Oct 25, 2011, at 11:06 AM, Guy Manchester wrote:
> >
> > > However there was a core support plugin in my main accounts QS Plugin
> > > folder & when I dropped that into the plugins folder in my Guest
> accounts
> > > Plugins folder & restarted everything loaded properly.
> >
> > > Any idea why it wasn't appearing originally just for me? I presume you
> guys
> > > tried what I was trying to make sure it was only affecting me & not
> every
> > > new user? Is the Core Support plugin meant to appear on QSApp.com or is
> it
> > > just me who can't see it there either?
> >
> > > The Core Support plug-in is part of the application and should only
> exist
> > > in /Applications/Quicksilver.app/Contents/PlugIns. You will likely have
> > > problems if there’s a copy in your user’s plug-ins folder.
> >
> > > You might see it on the list of plug-ins in the preferences, but it
> should
> > > be set so you can’t deactivate it.
> >
> > > To clarify, you may or may not have problems if Core Support is in your
> > > user’s plug-ins folder somewhere, but you should not have any problems
> if
> > > it’s missing from that location. It sounds like you’re seeing the
> opposite,
> > > which is strange. Can you confirm that it exists in
> > > /Applications/Quicksilver.app?
> >
> > > --
> > > Rob McBroom
> > > <http://www.skurfer.com/>
>

Reply via email to