Your best friend for file transfer.

Fetch application logoFetch

Missing Shortcuts after upgrading to v5.3 (4 posts)

  • Started 9 years ago by cyguy
  • Latest reply 9 years ago from Scott McGuire
  • cyguy Member

    I'm noticing that when I select "Show Shortcuts" after upgrading to v5.3 from v5.0.5, I don't see existing shortcuts. To correct this I've had select "Show Shortcuts", open "Fetch Shortcuts" located in ~/Library/Preferences by double clicking this file, drag and drop all shortcuts to the window opened through the menu bar. Is this how this is supposed to work? Am I missing something?

    Thanx,
    Cyrus

    Posted 9 years ago #

  • Scott McGuire Administrator

    Hi Cyrus,

    No, that is not the expected behavior. If your shortcuts were showing up in the Fetch Shortcuts window in Fetch 5.0.5, they should automatically show up in Fetch 5.3.

    We did change the format of shortcuts between 5.0.5 and 5.3, and they are automatically converted and upgraded the first time you run Fetch 5.3. So there may be something slightly amiss in the original shortcut file that is causing the automatic conversion to fail; I apologize for the problem.

    I assume, once you drag and drop all the shortcuts into Fetch 5.3, they show up automatically the next time you open Fetch 5.3? That is, you don't have to re-import the shortcuts each time you open Fetch?

    Also, Fetch 5.3 stores the shortcuts in a different file than 5.0.5. The new shortcuts file is named ~/Library/Preferences/com.fetch.fetchsoftworks.Fetch.plist . As I recall, you maintain a group of Macs, so I assume your goal is to get the shortcuts properly propagated to all the Macs in your lab once you install 5.3 on them. So, what you could do is, once you fix the shortcuts on one Mac, you could then copy the com.fetch.fetchsoftworks.Fetch.plist file to the rest of the Macs, instead of having manually import them again each time. (Be sure to quit Fetch 5.3 in order to save changes to the shortcuts file before copying it elsewhere.)

    If you would like to send us the Fetch Shortcuts file, we'll take a look and see if we can figure out why the conversion is failing. However, any bug fix we make as a result of that wouldn't be available to you until the next version of Fetch is released, so it wouldn't immediately solve your problem. We could send you back a fixed shortcut file, but as I described above, it sounds like you already have a way of creating a fixed shortcut file for distribution.

    Please let me know if this helps, or if you have additional questions.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

  • cyguy Member

    Hi Scott.

    This makes perfect sense, I think. Since I packaged v5.3 using Casper's Composer which includes two plists, ...Fetch.plist and ...Fetch.Shortcuts.plist, my guess is that the client machines are skipping the conversion process you are speaking of on their first launch of Fetch.

    Can I assume you meant ...Fetch.ShortCuts.plist and not Fetch.plist for where shortcuts are being stored now?

    Unfortunately we don't have a centralized Shortcuts list, each user has their own. I wonder if this can be corrected by removing ...Fetch.Shortcust.plist from my package. Will this force the conversion the first time Fetch v5.3 is launched when users are upgraded? I'll test this out as soon a I have a chance but thought I get your input on this.

    Thanx,
    Cyrus

    Posted 9 years ago #

  • Scott McGuire Administrator

    Hi Cyrus,

    Yes, sorry, I did mean the 5.3 shortcuts are stored in com.fetch.fetchsoftworks.Shortcuts.plist .

    And yes, if you're distributing a com.fetch.fetchsoftworks.Shortcuts.plist file to each machine, that would cause Fetch to skip the conversion process on first launch, and that would also explain the problem you're seeing. Removing it from the distribution and making sure there is no existing com.fetch.fetchsoftworks.Shortcuts.plist on the machines the first time the users launch Fetch 5.3 should fix the problem.

    Let us know if you're still running into problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 9 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.