Hi - has this (search) stopped working right for anyone else int the last couple of days?
@Daniel_Stieber thanks for creating it, couldn’t live without it!
1 Like
@Andrew_Mason I missed to update the workflow to the new CodaPHP library version. So CodAlfred tried to use the old Coda API version which was turned off during the last days.
I’ve just updated CodAlfred to version 0.0.3 .
Just open the file and click “update” to make it work again 
Let me know if you still face problems.
4 Likes
Thanks for maintaining this. I use it roughly a billion times a day.
5 Likes
Great to hear, that means a lot to me @DSB Thanks!
1 Like
Hi @Daniel_Stieber not sure if you still actively work on this but I love it and the Monterey beta has an issue. Any plans to create a v0.0.4?
"Reason: launch path not accessible
/usr/bin/php
Check that the selected language exists on your system.
If you’re syncing Alfred’s preferences, also check that all related workflow files exist locally.
Related Workflow Info…
Name: ‘CodAlfred’
Folder:/Users/MyUserName/Library/Application Support/Alfred/Alfred.alfredpreferences/workflows/user.workflow.88E7A5CF-74F9-4D2E-9AA2-D148245FB269"
1 Like
Hey, @Tim_Richardson
thanks for mentioning!
This is a known issue with Alfred in OSX12, because Moneterey does not ship with PHP anymore ( 
) . So EVERY Workflow relying on PHP will no longer work out of the box.
To make it work from my side, I’d have to rewrite it in another language…
But there is an official “fix” from Alfred side: Using PHP on Monterey (macOS 12)? - Discussion & Help - Alfred App Community Forum
How it should work (not tested from my side yet):
To make it work again you’d have to:
- Install PHP via Homebrew
– Go to Der fehlende Paketmanager für macOS — Homebrew to see how to install Homebrew
– Enterbrew install phpin your console to install PHP - Update to Alfred pre-release
– Open Alfred and go to Updates page. Select “Automaticall check for pre-release” in bottom right corner.
– Update to Alfred 4.6 Pre-release
– Pray
If you test it, maybe you can share if this has worked for you. I might be able to set up a Monterey Dev machine on the weekend to test it by myself.
1 Like
Thank you for your extremely fast solution! I did as you said and now the workflow works great. Thank you for the fix!
1 Like
Oh cool! Thanks for trying and letting me know 
2 Likes
Works for me too, thanks so much!
1 Like
@Daniel_Stieber, wanted to mention that I’ve just posted CodaAlfredJS, which takes much, much inspiration from your CodAlfred but written in JavaScript. I’ve also been a fervent CodAlfred user — thank you so much for making it — but I haven’t been able to surmount the various issues after macOS stopped pre-installing PHP. I have been learning about both the Coda API and JavaScript while building a similar module for the Drafts program, so I thought I’d give porting it over to Alfred a try.
Again, thanks so much for CodAlfred, and here’s a direct link to my CodaAlfredJS workflow if you’d like to take a look: https://github.com/brianseidman/codaalfredJS/releases/download/v1.0.1/CodaAlfredJS.alfredworkflow
1 Like
Hey @Brian_Seidman
thats wonderful! Thanks for making that and of course thanks for the many references. I was not maintaining CodAlfred, so I will set it to deprecated and link to yours.
I just realized I’m using Alfred 4, while there is already Alfred 5. Alfred 4 has no user configuration prompt, so in case anyone needs: the name of the variable for the api key in CodaAlfredJS is: ‘api’.
While I got it to run in Alfred 4 quickly, I had some issues in Alfred 5 because of a problem with my icu4c versions. Fixed it with this and now it works supernice.
1 Like
@Daniel_Stieber, thanks very much for your feedback. I’m going to add a note to the README regarding how to modify the workflow for Alfred 4.
Regarding the icu4c issue, I admit that’s a bit outside my present understanding, but just to check, does it have anything to do with the Alfy and related dependencies in the workflow? Those dependencies are included within the CodaAlfredJS workflow itself, but when I was uploading the raw files to Github, I saw a notice that I should omit the node_modules and just include the package-lock.json and package.json files instead. But, I’m not sure if I did that right or if I omitted anything I ought have included.
Anyway, I might be on the wrong track entirely, but if there’s something I should modify in this workflow so that others don’t have that icu4c issue, please let me know. Thanks!
To be honest, I have no idea at all 
it is my local development machine with node, PHP and lots of stuff and maybe not representative for the regular user. Might be some kind of a conflict there and only on my machine. But I don’t know anything about the issue itself, just googled and found help.
Maybe you find a chance to test you workflow on a clean mac setup.
1 Like