jdoe Posted July 14, 2022 Posted July 14, 2022 Hello, Just updated to Alfred version 5.0 [2057] and some off my old workflows for opening URLs aren't working. This seems to happen if my argument passed to the "Open URL" action contains a '/'. Looking at the debugger, the correct value seems to be passed to OPEN_URL but the browser just ends up opening a tab with about: blank. This workflow was working on Alfred 4 prior to me installing the version 5 today What you were doing when the issue happened Trying to run a workflow where a url containing a '/' was passed to Open URL Workflow is just a list filter where each option in the list points to a different URL. The urls containing '/' dont work. Whether you were able to replicate it a second time by performing the same action (Update any third-party apps and restart your Mac if relevant) Yes Include any screenshots that might help us Include the Alfred version & build number you are using Alfred 5.0 [2057] Include your macOS version MacOS Monterey 12.4 Include the version number of any third-party apps relevant to your issue Google Chrome 103.0.5060.114
vitor Posted July 14, 2022 Posted July 14, 2022 (edited) Welcome @jdoe, Could you share the Workflow in the screenshot (transfer.sh is good temporary storage) so we can test in context? See also the two new checkboxes in Open URL. Depending on how your Workflow is set up, you may need to uncheck one or both. Edited July 14, 2022 by vitor
jdoe Posted July 15, 2022 Author Posted July 15, 2022 Hi @vitor, Thank you for the quick response. Here you go - https://transfer.sh/0rs1qh/BrokenWorkflowExample.alfredworkflow.
vitor Posted July 15, 2022 Posted July 15, 2022 @jdoe Indeed, what’s happening is that your query is being escaped. Untick the Encode {query} placeholder checkbox in the Open URL and it works. For details on the change:
Andrew Posted July 16, 2022 Posted July 16, 2022 In the 5.0.1 pre-release, I've actually removed the / from the encoding character list. While the discussion above results in the "correct" use of the new options in the Open URL object, this tweak should make the encoding options more forgiving either way.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now