Vero

Vitor, thanks a lot for this and all the other work you have been putting out and sharing over the years!
I've learned a lot from how you code around problems, especially in shell scripting which I absolutely love.
I'm currently working to implement the Oneupdater in my first workflow work in progress (https://github.com/haakonstorm/transfred) which is working at the moment but not quite ready for primetime

Usage

Search through thousands of Netflix genres via the flixgen keyword. ↩ to open in the default web browser.



⤓ Install on the Alfred Gallery | Source
 

@Ariamis Welcome to the forum.
 
Could you please take a look at Console next time this occurs and see whether you're seeing the message referred to in the post below?
 
 
This only seems to affect a handful of Alfred users on Monterey, so if your issue is the same, please let me know and I'll close this thread, so that we can keep any updates on the topic in a single thread.
 
Cheers,
Vero
 

@pontus Shortcuts integration is definitely on Alfred's roadmap  More to come in the near future!

I'm not sure exactly what you're asking for. It sounds like you just need to add a Fallback Search trigger to a workflow and connect it to an Action in Alfred. Like this: https://deanishe.net/alfred-workflows/Universal Actions Fallback.alfredworkflow
 
Then add that trigger to your fallback searches under Features > Default Results.

Usage

Compress PNG, JPEG, and WebP images with TinyPNG via the Universal Action.



Alternatively, find images with the tinypng keyword.



⤓ Install on the Alfred Gallery | Source
 

@brank87 While it's unlikely this would happen, here's a workflow I use as scratchpad. 
 
It just creates a new file in my Documents folder if it doesn't exist, otherwise appends my current clipboard content to it with today's timestamp before it, either by using the keyword "scratch" or a hotkey. It's become automatic to bring it up with the hotkey combo every time I start a phonecall, knowing I'll probably need to scribble something.
 
https://www.dropbox.com/s/ehql878e1y80bwh/Scratchpad for taking notes.alfredworkflow?dl=0
 
Of course, modify it as you wish if you'd prefer it created a new file every time, overwrite the previous one, don't paste in clipboard content, etc...
 
Cheers,
Vero

Yes, you can open your Powerpack preferences, view your license and click "Deactivate" to remove your license from a Mac you no longer want to use
 
 
While it's not possible to cross-grade from one license type to another within the same version, if you opted for the Single User license, you'd be presented with upgrade options to the Mega Supporter when the next version of Alfred is announced
 
Cheers,
Vero

I paid for a Powerpack and signed up for this forum just to say thank you for releasing this. I'd be manually running the terminal command for months until recent releases couldn't even force Spotlight to index Google Drive.
 
This has drastically improved my day to day. I was spending so much time trying to reset search, find files I need to be effective at work, find files I need for personal reasons - it's baffling Google screwed this up when their old product worked, but whatever. Thank you, again for this.

This doesn’t seem to be possible. I didn’t find any API to access that information.
 
That is not surprising. It is the type of thing Apple would keep for themselves and their apps to give themselves an edge. And possibly for privacy reasons: you say the feature is extremely accurate, so imagine an unscrupulous ad exchange (pleonasm) getting constant access to your data.

Thank you guys, I feel less doofy now, it's such a pleasure whenever I have the great fortune to interact with regulars on this forum

@Floating.Point Thank you for pointing this out, and no need to feel like a doofus!  I've updated the page to be a little more explicit about indexing issues (and will keep an eye out for anywhere else I might make it more obvious too as I update more pages in the next few weeks)
 

 
This should make it a little clearer
 
Cheers,
Vero

For anyone who hasn't done so yet, please rebuild your Mac's index properly, as this may be all that's needed, as seems to have been the case with some users.
 
Even if you believe you've already reindexed, please follow the steps below specifically (as it involves deleting a cache first and ensuring Terminal has suitable permissions).
First, please pop open System Preferences > Security & Privacy > Privacy > Full Disk Access and add Terminal Once you've done this, go to Alfred's Advanced preferences, choose "Rebuild macOS Metadata" Ensure that you check "Delete .Spotlight-V100 before reindex" Follow the steps in Terminal, and keep a close eye for any error messages relating to your index. Please let me know if there are any errors. Otherwise, if it proceeds smoothly, you may need to wait up to an hour for the reindex to complete. Once this is done, make your searches again and see if your results are more as expected.
 
Do let us know how you get on

@seamush In that case, can you please provide as much information as you can? 
 
The first steps to follow when results seem unexpected is to rebuild your Mac's metadata. It's usually because the data being provided by macOS is incorrect (even if it appears correct in the current Spotlight cache), and rebuilding ensures that all this information is refreshed by the OS.
 
Even if you believe you've already reindexed, please follow the steps below specifically (as it involves deleting a cache first and ensuring Terminal has suitable permissions).
First, please pop open System Preferences > Security & Privacy > Privacy > Full Disk Access and add Terminal Once you've done this, go to Alfred's Advanced preferences, choose "Rebuild macOS Metadata" Ensure that you check "Delete .Spotlight-V100 before reindex" Follow the steps in Terminal, and keep a close eye for any error messages relating to your index. Please let me know if there are any errors. Otherwise, if it proceeds smoothly, you may need to wait up to an hour for the reindex to complete. Once this is done, make your searches again and see if your results are more as expected.
 
If your issue persists, please provide the following information:
Your diagnostics file, by typing ?diagnostics into Alfred (You can email this to our info@ address, including a link back to this thread) Examples of the File Troubleshooting reports for the files you cannot find using Alfred Details of exactly what you're typing into Alfred and what results you are expecting to see The more information you can provide, the more likely we'll be able to help you establish what's happening on your Mac specifically.
 
Cheers,
Vero

The error message usually makes it easy to identify which application has locked secure input. If Alfred reports that "loginwindow seems to be preventing text expansion by locking secure input" or a random process number, it's likely that Alfred is unable to tell which application is using secure input.

This can be because macOS itself has left the secure input enabled (e.g. when you've recently logged into your Mac, or after waking your computer and typing your password). This can be resolved by restarting your Mac, or logging out fully and logging back in.

If the issue occurs frequently, try launching a minimum number of apps/services on your Mac, and re-launching apps one by one, allowing you to establish which app or service is locking secure input by process of elimination. Note that browser plugins (e.g. password managers) can be the cause, so enable plugins one at a time to test them.
 
Cheers,
Vero

@maxromanovsky Yes, provided you're the sole user of that Mac and it's within the alloted number of Macs for your license, you can activate on your work device
 
Cheers,
Vero

For anyone who hasn't done so yet, please rebuild your Mac's index properly, as this may be all that's needed, as seems to have been the case with some users.
 
Even if you believe you've already reindexed, please follow the steps below specifically (as it involves deleting a cache first and ensuring Terminal has suitable permissions).
First, please pop open System Preferences > Security & Privacy > Privacy > Full Disk Access and add Terminal Once you've done this, go to Alfred's Advanced preferences, choose "Rebuild macOS Metadata" Ensure that you check "Delete .Spotlight-V100 before reindex" Follow the steps in Terminal, and keep a close eye for any error messages relating to your index. Please let me know if there are any errors. Otherwise, if it proceeds smoothly, you may need to wait up to an hour for the reindex to complete. Once this is done, make your searches again and see if your results are more as expected.
 
Do let us know how you get on

Hi,
 
first poster here. I usually blog about email and automation. Recently, it occurred to me to use Alfred for automation. I've used Alfred for a couple of years. But I never used it for automation.
 
I've first made a blog post about using Automator with a keycombo (didn't like it very much): http://www.mothsoftware.com/executing-an-applescript-with-a-keycombo-using-automator
 
Today I posted a really basic guide to make a workflow with AppleScript: https://www.mothsoftware.com/getting-started-with-alfred-workflows-with-applescript
 
I read that it's recommended to use osascript instead of NSAppleScript. I'm going to discuss this in another blog post.

Welcome!
 

If possible, please consider making the change in that post, since it’s relatively simple. Because your tutorial is geared to absolute beginners, it’s important to instil good habits instead of something which may bite them later.
 
NSAppleScript is the kind of tool which should be used only “when you know what you’re doing” and novices (by definition) don’t. Plus, you have two lines of boilerplate (for a one-like script) which wouldn’t be there in a Run Script.
 
That aside, thumbs up for contributing to the demystification of code through Alfred, and showing to people who are afraid of programming that it’s possible to do something with little.

@pontus Shortcuts integration is definitely on Alfred's roadmap  More to come in the near future!

Yes.
 
 
If memory serves, when the previous versions didn’t get a match they wouldn’t allow searching for the current query and would instead return nothing. Except if you use Fallback Searches, you might be seeing those anyway. But because I tried to be helpful and present a “no results” message when nothing matched, it counts as a result thus the Fallback Searches aren’t triggered.
 
Either way, doesn’t matter. What matters is we can get the best of both worlds by making it search for your query when no results are found. Download the new versions for a quick fix back to your preferred behaviour. I’ll send these to @Vero too.

@pontus Shortcuts integration is definitely on Alfred's roadmap  More to come in the near future!

@archelium (and anyone else who finds this thread from now on) We've created a page explaining what's happening and how workflow creators can update their workflows to no longer use Python 2 in a future update:
https://www.alfredapp.com/help/troubleshooting/monterey-alfred-4-python-2-popup/
 
In short, you can click "Ok" and you shouldn't see the notice again. We've tested and it doesn't re-appear after you restart your Mac, so is currently just a one-time notice that workflows you're using are using a deprecated version of Python.
 
Cheers,
Vero

@pontus Shortcuts integration is definitely on Alfred's roadmap  More to come in the near future!

@Chris Messina We've created a page to let users know what's happening; In short, and much as you and @deanishe have deduced, this is a notification from macOS that a workflow uses Python 2. Clicking "OK" makes it go away, the workflows work and you shouldn't be notified again.
 
As this notification is being shown outside of Alfred, and somewhat opaquely by macOS, Alfred can't treat this scenario in the same way he does with PHP (which is essentially a missing binary). If python was missing altogether, you'd see the same kind of dialog you see with PHP. In all likelihood, we will add a warning dialog closer to the time this becomes a larger issue, but for now, click "OK" once and continue as usual.
 
Cheers,
Vero