Thanks Tim for your help, What Tim has said is indeed correct; it's worth ensuring your Dropbox folder is located within your home folder (the folder named your username). This is what Dropbox recommends.
If it is already located there, then I suggest you un-tick then re-tick the option to place your keychain in the Dropbox folder (if you are using the Mac App Store version of 1Password) or re-selecting the Dropbox folder if you are using a non-Mac App Store version of 1Password. If this still does not solve your problem, then please do let me know: a) which version of 1Password you are using (Mac App Store or not) b) The exact location of your keychain (right click and select 'get info' and see the 'where' section) c) the file located at ~/Library/Preferences/ws.agile.1Password.plist (if it exists) -- I suggest you don't share this with the group, but feel free to email me directly on patrick [at] qsapp.com I will most likely be unable to help further until after the 12th of January as I am away at the moment, but I hope this helps! On 28 Dec 2011, at 16:05, Tim Lawson wrote: > Keith - > > Open 1Password's prefs and, with the 'general' tab ticked, you should see > that your iPassword keychain is stored at ~/Dropbox per the screenshot below: > > <General.jpg> > > Then open your Dropbox app. prefs. and, on the 'Advanced' pane, you can see > where to change the location for your Dropbox. I remember reading something > somewhere about the need for it to be in the users folder root (if that's the > right expression) per my own as you'll see from the screenshot below. > > <Advanced.jpg> > > On 28 Dec 2011, at 12:00, Keith Kastorff wrote: > >> Running OS X 10.7.2, B63. New install of QS on this machine. I'm getting -- >> >> Quicksilver: Unable to determine 1Password keychain path. Assumed it was in >> /Users/username/Library/Application >> Support/1Password/1Password.agilekeychain, but file not found. >> >> The 1Password keychain is located in a 1Password folder at the root of my >> Dropbox folder. 1Password functions normally. >> >> I haven't found a place to specify the path for the plugin. Solution? >
