Jump to content

Stefan Kleineikenscheidt

Member
  • Posts

    19
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Stefan Kleineikenscheidt's Achievements

Helping Hand

Helping Hand (3/5)

4

Reputation

  1. @vitor thanks for trying to clarify, but I think you don't fully understand what I mean. It's about the difference between an empty default value and an undefined default value. Let me I try to explain what I mean on more time (will be the last try): As a workflow developer, I have two options: I can define a default value (as empty or any other string) - OR - I can not define a default value (ie. leave it unspecified). What I am asking for is to reset to the default value only, if the default value is defined. Or vice versa: If I've not defined a default value, it should just not be reseted (after all there is no default value, isn't it?). That way workflow developers could decide which fields should be handled in which way when users "Reset to Defaults". PS: About your comment on support: An empty API token field will lead to an error message just as a wrong API token. Error cases like that need to be handled at runtime anyway, and should generate an understandable error message.
  2. Not sure if understand correctly what you mean by "default contains no entry"? What I am proposing is a different handling depending on whether the default value is set to empty (reset to defaults β†’ field should be emptied), or if it is defined not at all (field should be let as is).
  3. Hi Alfred team, when a user clicks, Reset to Defaults, all fields get reseted, even the ones that don't have a default value. This means that in the example below from the Confluence Quicksearch workflow URL, Email and API Token are getting deleted, even if a user only want to reset the default content-types for search. In my opinion resetting to defaults makes sense, if a user can return to a state that makes everything work again. However, if a field is required, but has not default value, emptying it doesn't revert to a working state. So my proposal: Reset only those fields that have a default value. Hope that makes sense?! Cheers, -Stefan
  4. Hi! I hope it's ok that I am sharing a workflow again that has been around for a while. However, it's a complete rewrite to finally support macOS 12.3 with some nice new features: Super simple configuration thanks to the new Workflow User Configuration in Alfred 5. Limit to search to single spaces by adding -s <spacekey> to the search terms Limit to search to content types by adding -t <contentTypes> to the search terms (<contentTypes> is a comma-separated list of page, blogpost, attachment, e.g. page,attachment) Directly edit pages when selecting a search result with ⌘Enter Copy Confluence page URL with ⌘C More Info: https://github.com/skleinei/alfred-confluence/discussions/16 Download: https://github.com/skleinei/alfred-confluence/releases/tag/2.0.0 🚨 Please note: I haven't implemented support for Confluence DataCenter/Server yet. Please let me know on Github, if you need it. Confluence Quicksearch only works with Alfred 5 (because it uses the Workflow User Configuration I hope you find the new version useful.
  5. Great suggestion @Brooke Kuhlmann and I have to say I also like the the user configuration UI (just used it to finally update my Confluence Quicksearch workflow). However I'd really want to have the password field to store its content safely too. I guess what I mean: πŸ’― for @Andrew's internal ticket. πŸ™‚
  6. Hi @osi, thanks for that! Does it require users to install Node, or does it work with macOS "out-of-the-box"? FYI: But I am happy that I've just released a new, rewritten version, that works on macOS 12.3/Monterey and (hopefully) beyond. More Info: https://github.com/skleinei/alfred-confluence/discussions/16 Download: https://github.com/skleinei/alfred-confluence/releases/tag/2.0.0
  7. Important Announcement: With the new 2.0.0 release, I've activated Discussions section on Github. Please post your questions and issues on Github: https://github.com/skleinei/alfred-confluence/discussions/categories/q-a
  8. Hey @daearcdo, I've just released a new major version of Confluence Quicksearch for Alfred, which used API tokens that should work for your case as well. Read more: https://github.com/skleinei/alfred-confluence/discussions/16 Download: https://github.com/skleinei/alfred-confluence/releases/tag/2.0.0 Hope this may be of help for you!
  9. Hey Tom, it looks like the Confluence URL is set to an int. Can you try to configure it with a config file (in ~/.alfred-confluence.json) and post that here? Thanks, -Stefan
  10. Hey @Corina and everyone else, I finally got around to look into the issue – and hopefully fix it with release 1.0.3. Please give it another try. Attention Confluence Cloud users: Please make sure to use an api token as password (more info: https://confluence.atlassian.com/cloud/api-tokens-938839638.html), as passwords won't work anymore. Also make sure to login through a browser in case you have an authentication error. Confluence may display a CAPTCHA. Let me know it that helped. Cheers, -Stefan
  11. @Corina, can you send the debug output from alfred, like doctorwho did? Are you on Confluence Cloud or Server? Btw, @all: For all the authentication issues - it seems that the alfred-confluence isn't working on Confluence Cloud these days. Cheers, -Stefan
  12. Also, we have gzip encoding enabled on our wiki and it still works. This still looks like an authentication problem, when the actual call to the Confluence Quick Search is made. When I have some spare time, I'll add some more logging to better understand what is going on.
  13. Mike, not sure how the authentication works, but I'm afraid that's beyond what I can support (if at all possible). Sorry! -Stefan
  14. Hey Shiram, confluence_baseurl should not have a trailing slash, have you removed it? (look up /Users/myuser/Library/Application Support/Alfred 3/Workflow Data/com.k15t.labs.alfredapp.confluence.quicksearch/). It should look like this: { "__workflow_last_version": "1.0.2", "confluence_baseUrl": "https://mycompanyname.jira.com/wiki", "confluence_username": "shriram@mycompanyname.com" } Cheers, -Stefan
  15. Hey Doctorwho, it looks like you have configured https://mycompanyname.jira.com/wiki as Confluence Base Url, which is most probably not right. Please delete the ~/.alfred-confluence.json file and follow the step #3 from the getting started guide and make sure to use the correct Confluence Base URL. If you cannot get this to work, please create again the ~/.alfred-confluence.json file and post its contents here. -Stefan PS: Matt, I believe you experience the same issue. Pls. try to do as describe above too.
×
×
  • Create New...