Jump to content

rhyd

Member
  • Posts

    47
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by rhyd

  1. Not seen that error message before. Bit of an odd one... are you running the python version of the workflow or the javascript version?
  2. @chowderresearcher Hi - yes, you need to run `find-of-db` as an Alfred command not from the command line. e.g.
  3. We're getting there... Next is: 1. Run Alfred command `find-of-db` to copy the path of the Omnifocus DB to your clipboard 2. Run Alfred command `set-of-db` and then paste (⌘-V) the database path as an argument and hit return then retry.
  4. Hi - no problem, this updated workflow has been more of a pain than the old version. It hasn't been a great user experience for everyone - apologies. Here's step by step instructions: Open terminal.app Type in `bash` and then press RETURN Type in `npm install -g alfred-search-omnifocus` and press RETURN You should then see a progress bar as the `npm` command downloads the required files and installs the workflow. If that doesn't work, let me know and I'll see if I can do something else to help. Screenshots to accompany each step above...
  5. I've updated the workflow to v1.0.12 so that it uses the latest versions of the packages it relies on to function correctly. Horror show complication errors seen before are now - as far as I can see - no longer happening. I've had issues with different versions of node and different shells on my Mac but I think if you switch to a bash shell before installing, the problems seen before won't happen: > bash bash-3.2$ node -v v18.12.1 bash-3.2$ npm install -g alfred-search-omnifocus ...
  6. Hi @jstncwlcx - thanks for raising this. I think I need to look at the latest version of better-sqlite3 and how that works with the latest version of node. Let me do this first and then - 🤞 - I can release an updated version of the workflow to solve this wretched issue... Cheers, Rhyd
  7. Ach! Yes, you’re right. Alfred won’t start up correctly with the preferences file synced via Maestral. ☹️
  8. Looks to be a Dropbox client issue. Using Maestral as an alternative downloads the file fine. Ignore me!
  9. Anyone seen this issue before and knows of a fix? I'm syncing my .alfredpreferences file to Dropbox from my primary Mac. Dropbox syncs the ~/Dropbox/Alfred folder without any issues but is not pulling down the Alfred.alfredpreferences folder into that folder (even though the file is available online via Dropbox). Selective Sync is disabled (everything should be stored locally since I'm on the free plan). Both MacBooks running Ventura. No sync issues reported by Dropbox. Full Disk Access enabled for Dropbox. 😫
  10. @jochi glad you found the answer at GitHub - sorry for the slow response here from me.
  11. @mike007 problem here is that macOS no longer supports python and therefore this workflow without some additional steps on your part. You can either: 1. follow Alfred's instructions to install a version of Python 2 to allow this workflow to continue working on Monterey 2. install my alternative Javascript version of the workflow (install instructions) I'd recommend #2 - let me know how you get on.
  12. Hi @mike007, sorry to hear you're having trouble running the workflow. Couple of questions: are you running macOS Monterey? which workflow are you using? The python workflow or the Javascript workflow? Can you: Show Alfred preferences (keyword 'alf') Click 'Workflows' in the tool bar Choose on the Search Omnifocus workflow from the list of workflows on the left Click on the 'Debug' to toggle debugging mode (see Alfred's help page for more info) Choose 'All information' from the Log dropdown Open Alfred and type the query that's not working Copy the debug output and post it as a response - I'll take a look.
  13. You don't seem to have node installed which this workflow relies on. 🤔 I'll update the instructions. See https://treehouse.github.io/installation-guides/mac/node-mac.html
  14. You need to run `npm install --global alfred-search-omnifocus` (you omitted the npm) To run an Alfred command you, just need to open Alfred (for me that's ⌘-Space) and type in the commands from the instructions
  15. I've created a new version of this workflow that doesn't rely on Python. It's still rough around the ages but available if you want to try it. More details available here.
  16. What @Vero said... Will post an update later this week on a replacement workflow.
  17. Thanks for the feedback. Searching completed tasks should be ok. I'll have a look and add into a future release.
  18. @Manaus Looks like Omnifocus 3.4.6 is almost a year old. If you upgrade to the latest version the problem above should be resolved. If you can't upgrade, then you could try installing v2.1.0 of the workflow to see if that solves the problem.
  19. Ok, spotted the problem. The workflow is using the wrong location to find the database because you're using an out of date version of the workflow. Can you download and install v2.1.2? I should've spotted that earlier 🤦‍♂️... Download v2.1.2 Cheers, Rhyd
  20. No worries. Can you: 1) open the folder below in the Finder (open a Finder window, press ⌘-⇧-G and paste the location below into the "Go to the folder" dialog) /Users/rlow/Library/Containers/com.omnigroup.OmniFocus3/Data/Library/Application Support/ 2) open the OmniFocus Caches folder and check if you can see a file called OmniFocusDatabase?
  21. Hi @rlow, thanks for getting in touch. To solve this, I'll need to know where your OF database actually is (or if it's in the expected place but the workflow doesn't have permission to access it). Can you: 1. Open Terminal.app and run this command: find ~/Library/ -name "OmniFocusDatabase" 2>&1 | grep -v "not permitted" 2. Copy and paste the result here Thanks, Rhyd
×
×
  • Create New...