Your best friend for file transfer.

Fetch application logoFetch

upload/download completed (32 posts)

  • Started 6 years ago by LP1
  • Latest reply 3 years ago from Scott McGuire
  • LP1 Member

    Is there any way of generating an email when either the upload or download of a file is completed ??

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi,

    There isn't a built-in feature for that in Fetch, however it's pretty easy to create an Automator droplet that you could drag files to, have them uploaded, and then an email would be sent using Mail.app.

    Setting up something similar for downloads is a little trickier, but doable.

    Please let us know if you would like help in setting one of these up.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • LP1 Member

    Hi Scott,

    I would really appreciate some help with both !

    Regards
    Nick

    Originally posted by ScottMcGuire:

    Hi,

    There isn't a built-in feature for that in Fetch, however it's pretty easy to create an Automator droplet that you could drag files to, have them uploaded, and then an email would be sent using Mail.app.

    Setting up something similar for downloads is a little trickier, but doable.

    Please let us know if you would like help in setting one of these up.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi Nick,

    Okay, let's start with using Automator to create a droplet that will upload files and send a mail message when the upload is finished.

    Note that these instructions assume that you have set up Apple's Mail.app program to work with your email server; if you have not done that, you should do that first. Unfortunately, I do not believe that most other email programs work with Automator, but if you use a different program, we can investigate. So you may have to set up Apple Mail even if you don't want to use it as your primary email program.

    First, if you aren't familiar with Automator, you should read our Introduction to using Automator with Fetch topic in Fetch Help (or click the link here). It introduces the concepts and terms of Automator, and includes two short examples of Fetch Automator workflows.

    Then, to create the upload droplet, follow these steps in Automator:

    * Open Automator (located in your Applications folder). A new workflow window should open automatically. If it does not, choose File > New.
    * Click the Fetch icon in the Applications list.
    * Drag an "Upload Files" action from the Action list to the workflow area.
    * In the "Upload Files" action, enter the connection information for the server and remote folder (if any) you want to upload the files to, or choose a recent connection or shortcut from the pop-up menus.
    * Click on the Mail icon in the Applications list.
    * Drag an "New Mail Message" action from the Action list to the workflow area, placing it after the first action.
    * Enter the desired information in the To, Subject, and Message fields of the "New Mail Message" action. This list of files that were uploaded will be added to the bottom of the Message when the email is sent.
    * Drag a Send Outgoing Messages action to the workflow area, placing it after the "New Mail Message" action. Your mail won't be sent if you don't include this action.
    * Finally, save the workflow as an application. Go to the File menu, and choose Save As. In the Save dialog, choose Application from the File Format pop-up menu, and then enter a name and choose a location to save your droplet.

    To use it, drag files to the droplet's icon. It will automatically open Fetch, upload the files, and then send the mail message.

    If the connection to the server requires a password, you will be prompted for it when you use the workflow. If you do not want to be prompted for the password, you should save the password for the connection in your keychain.

    Let us know how that goes, or if you have any questions, and then we can move on to creating a workflow for doing the same when downloading files.

    Thanks,

    Scott McGuire
    Fetch Softworks

    [This message has been edited by ScottMcGuire (edited 09-26-2007).]

    Posted 6 years ago #

  • LP1 Member

    Early problem ... I can't find the Fetch application in the automator list ?

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi Nick,

    Okay, here are some things to try.

    Make sure you have the latest version of Fetch, version 5.2.1. If you have version 5.0 or later, this is a free upgrade. (Automator support was introduced with version 5.1.)

    If you had an older version of Fetch, open the updated version of Fetch. Then open Automator, and see if Fetch is listed.

    If that wasn't the problem, or didn't fix it, next you should check and make sure that you only have one copy of Fetch on your Mac, and that copy is version 5.2.1. Multiple copies of the same application can confuse Automator. (If you want to save older versions of Fetch, use the Finder's "Create Archive" command to create archives of them, and throw out the unarchived versions.)

    Once you're sure you have only one copy of Fetch, open Fetch.

    Then quit Automator if it's running, hold down the Option key while opening Automoator, and keep holding down the Option key until the blank Automator workflow window appears.

    One of these tricks should make Fetch show up in Automator's application list. Let us know if they do not.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • LP1 Member

    Hi Scott,

    That did the job, I was still using 4.0.3 !
    I have followed your Automator instructions, works fine.
    Could we try the download option ?

    Posted 6 years ago #

  • Scott McGuire Administrator

    Hi Nick,

    I'm glad to hear the uploading droplet is working well for you. (And thanks for upgrading your copy of Fetch!)

    Here are instructions for setting up the Automator workflow to download files and send an email. The workflow will download files and folders you select in the Fetch transfer window, and send an email when all the files are finished downloading (it won't send an email for each individual file). As before, this assumes that you will use Apple Mail for sending the email message.

    This workflow will not list the names of the files and folders that were downloaded in the email. We apologize for that, but there isn't a way to do that with the Fetch actions at the moment.

    Create the "download and send email" workflow by following these steps in Automator:

    * Open Automator (located in your Applications folder). A new workflow window should open automatically. If it does not, choose File > New.
    * Click the Fetch icon in the Applications list.
    * Drag a "Get Selected Fetch Items" action from the Action list to the workflow area.
    * Drag a "Download Fetch Items" action from the Action list to the workflow area, placing it below the first action.
    * In the "Download Fetch Items" action, choose the location on your Macintosh you'd like the files to be downloaded to from the pop-up menu. If the location you want isn't listed, choose "Other" to select the folder of your choice.
    * Click on the Mail icon in the Applications list.
    * Drag a "New Mail Message" action from the Action list to the workflow area, placing it after the "Download Fetch Items" action.
    * This is very important: in the gray title bar of the "New Mail Message" action, click where it says "Files/Folders". A short pop-up menu will appear; choose "Ignore Results from Previous Action." If you do not do this, your downloaded files will be sent as attachments with the email message - and you probably don't want that.
    * Enter the desired information in the To, Subject, and Message fields of the "New Mail Message" action.
    * Drag a "Send Outgoing Messages" action to the workflow area, placing it after the "New Mail Message" action. Your mail won't be sent if you don't include this action.
    * Finally, save the workflow as an application. Go to the File menu, and choose Save As. In the Save dialog, choose Application from the File Format pop-up menu, and then enter a name and choose a location to save your workflow.

    To use the droplet:

    Unlike the upload droplet, you cannot just drag and drop files from Fetch on to the droplet in order to download them. Instead, you must select the files and folders in the Fetch file list window, and then open the workflow.

    One way to do this would be just to put the workflow in your Dock, and then you can click on it after selecting files in Fetch.

    Alternately, if you don't want to clutter up your Dock with it, you can put the workflow in the system-wide "Scripts" menu, where it will appear as a menu item. Then you can select the files, go to the Scripts menu, and choose a "Download and send email" menu item. Let us know if you would like information on setting up the Scripts menu and getting the workflow listed in it instead.

    And please let me know if you have further questions, or if the workflow described above doesn't do quite waht you wanted.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 6 years ago #

  • agennuso Member

    I have tried the Upload File version of this using 5.5.2 but for some reason I get "Apple Script Error: The result of a numeric operation was too large. (-2702)" when I try to save it. And if I do get it running I cannot seem to get the file that I have selected to actually upload to my server.

    Any help would be appreciated. Thanks.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi agennuso,

    Which version of Mac OS X are you using?

    I have tested creating the upload version of the workflow as described above with Fetch 5.5.2, and it worked for me (I did not get errors when saving and it uploaded the file); so we need to figure out what might be different between my system and yours.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • agennuso Member

    Hi Scott,
    Thanks for the reply.
    I am using snow leopard so I am not sure if that is making a difference or not to the way the workflow needs to be created.

    Thanks.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi agennuso,

    Thanks for the information. I have duplicated the problem you encountered on Snow Leopard with the Upload Files + New Mail Message actions in Automator. They work fine separately, but together they cause the error you saw. Unfortunately, I haven't yet figured out what is causing the error, or a workaround for it. I am consulting with a colleague, and once I know something more, I will let you know.

    EDIT: We have now identified the problem and there is a workaround. Please see this post for the details.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Kohl S Gill Member

    Scott, when you figure out the "The result of a numeric operation was too large. (-2702)" error, I'd love to hear about it, for an unrelated Automator issue.

    Thanks,

    Kohl

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Kohl,

    We'll definitely post an update here once we have an idea.

    (And agennuso, sorry we don't have an update for you yet.)

    Kohl, it might help us track down this problem if you could tell us more about where you're experiencing this error, even if it it's not with Fetch. Having a second example of the problem to compare with would be useful. Could you describe the workflow and which actions from which programs you're using when you run into this error?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Kohl S Gill Member

    Great. I'm just fiddling with a simple little automator folder action that, upon dropping a file into the folder, prompts the user for a new location for said file, a new name, and spotlight tags. I started getting the "The result of a numeric operation was too large. (-2702)" error after I'd added the Rename Finder Items. I'm trying now to reproduce the error, and now get it not only when I run, but also when I switch back to the Automator application.

    Here's my code in brief. I've inserted a Get Specified Finder Items to test it in Automator:

    (ignore input) Get Specified Finder Items
    Set Value of Variable --Saving the file to variable:file itself
    (ignore input) Get Contents of Clipboard --want the program to start the location prompt at the last location used as I'll be running this program over and over
    Add Prefix to Text Paragraphs --adding "{alias " to the path string to get it into an alias format for later
    Add Suffix to Text Paragraphs --adding "}"
    Set Value of Variable --variable:path
    (ignore input) Ask for Finder Items --set the new path, with a default of what was pulled from the clipboard
    Set Value of Variable --variable:path
    Copy to Clipboard
    (ignore input) Ask for Text --variable:filename
    Set Value of Variable
    (ignore input) Ask for Text --variable:tags
    Set Value of Variable
    (ignore input) Get value of Variable --variable:file itself
    Set Spotlight Comments for Finder Items --appending, using variable:tags
    Move Finder Items --to variable:path
    Rename Finder Items --change basename to "$(...)" where ... is the hex code found for variable:filename in the package contents for this folderaction

    When run, everything seems to work except that I don't get any spotlight comments.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Kohl,

    Thanks for the information, we'll keep it in mind.

    When I was gathering data about the -2702 error, I found that in order to clear out the error before running a new test, I needed to quit Automator between tests. Otherwise I'd get the -2702 error in places I hadn't gotten it previously.

    Good luck and let us know if you figure anything out.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Jake Member

    Did you ever figure out the issue with agennuso's problem? I'm having the same thing happen in Snow Leopard. Looks to be something to do with the "Upload Files" action. I get the AppleScript Error The result of a numeric operation was too large. (-2702)

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Jake,

    As best we can the Upload Files + New Mail Message problem is the result of a bug in Mac OS X 10.6, unfortunately, and we haven't figured out a workaround for it. As I noted above, the Upload Files action appears to work fine in most cases, just not when combined with that other action.

    EDIT: We have now identified the problem and there is a workaround. Please see this post for the details.

    Are you encountering the error with a combination of Upload Files action with some other action? If so, we'd like to hear about it, just in case it gives us new light on the problem.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Jake Member

    Nope. After posting that, however, I've seen that the process still works; it just gives me the error when I open the application to edit it.

    Thanks for getting back to me!

    Edited 4 years ago #

  • Matt Member

    We are also getting the -2702 error. This is very disappointing as we ftp a lot of files and using automator made this very simple. It's one of the reasons we got Fetch. Now that we have upgraded to Snow Leopard, it no longer works correctly. Please let us know if there is a fix for this!

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    I understand that you're frustrated and we continue to look into this problem.

    EDIT: We have now identified the problem and there is a workaround. Please see this post for the details.

    Could you tell us a little more about your setup? Have you saved the workflow as an application, or are you running the workflow in Automator?

    Does your workflow include only Fetch Automator actions, or does it include actions from other applications? Specifically, does it include actions from Mail?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Matt Member

    We are using upload to ftp, and create entourage email. Those two together cause the problem. We have an applescript and get clipboard contents in between, but even without those two the problem still exists. Everything worked great with 10.5. Just upgraded to snow leopard and now we have the problem. I open automator, create application and as soon as I add upload to ftp and email it gives the error.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    Thanks for the additional information.

    I realize you get an error when saving the application.

    Have you tried using the application even though you got an error when saving it? If so, do you get the -2702 error when you try to use the application after saving it?

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Matt Member

    I get the error upon opening saved applications and when I try to create applications using "upload to ftp" and "create new entourage mail message". The error pops up before I even try to save.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    Try the following, which has worked for me:

    * Create a new workflow.
    * Add a Fetch upload action only.
    * Configure the upload action as desired.
    * Then add the rest of your actions. Do not make changes to the upload action again.
    * Save the workflow as an application, ignoring the error.
    * Try using the Automator application and see if it works.

    Let me know if that works or not, and if not, at which point you got an additional error.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Matt Member

    Yes, that workaround does seem to work. However, if I need to edit the application droplet, when I open it back up, all of the ftp information is cleared out. But for now, it will do. Thanks, and hopefully someone can find a better solution for this in the future.

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    Glad to hear that worked. I agree it's not a perfect workaround.

    Unfortunately, as I've said before, the indications are that this is a Mac OS X bug (there are reports of the same error with Automator workflows that don't involve Fetch), but if we find a better solution, we will definitely update this topic.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Edited 4 years ago #

  • Scott McGuire Administrator

    Hi all,

    We have an update regarding the "The result of a numeric operation was too large. (-2702)" problem on Mac OS X 10.6 Snow Leopard, including a new workaround to avoid it.

    We've sat down with Apple engineers and together we have identified the problem; it is, as we suspected, a Mac OS X issue. A bug report has been filed, but we do not know when or if it will be fixed in Mac OS X 10.6.

    In the meantime, we have learned that you can work around the problem by setting Automator to run in 32-bit mode - the problem only happens in 64-bit mode. To do this:

    * Quit Automator if it's running.
    * Open your Applications folder.
    * Click once to select the Automator application.
    * Go to the File menu, and choose Get Info.
    * In the General section, check the "Open in 32 Bit Mode" checkbox.
    * Close the info window.
    * Open Automator and create your action.

    Now you will be able to use both the Fetch Upload Items action and Get New Mail Message action in the same workflow without getting an error.

    Note that you only need to do the above steps if you are running Mac OS X 10.6 and are experiencing the "The result of a numeric operation was too large. (-2702)" error when trying to use the Fetch Automator actions. Otherwise, you do not need to perform the above steps.

    In theory setting Automator to work only in 32-bit mode could decrease the performance of Automator slightly, but in actual use, in nearly all cases there should be no noticeable change in performance.

    We're going to investigate to see if we can add a workaround to the Fetch Automator actions for this Mac OS X problem, and if we are successful, we'll update this thread again. But in the meantime, setting Automator to run in 32-bit mode should prevent the error from happening.

    If you give this a try, please let us know how it goes, or if you run into any new problems or have other questions.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #

  • Matt Member

    This works perfectly. Now I won't have to edit my scripts on a computer running 10.5 anymore. I really appreciate your diligence in resolving this issue. Great customer support!

    Posted 4 years ago #

  • Scott McGuire Administrator

    Hi Matt,

    You're very welcome, and thanks for letting us know that it resolved the problem for you!

    Best,

    Scott McGuire
    Fetch Softworks

    Posted 4 years ago #