• Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by ryan360Works

  1. Hi Gary, I have seen an issue similar to this and the problem was being caused by the progress bars. Add FTPeek_SetShowProgress(0) to your script before the download function call to suppress the progress bar and see if that resolves the issue.
  2. Hi Trinikal, Yes, the function to use is EmailReadMessageValue. You pass in the value that you would like to parse from the message. So if you just wanted the plain text of the email it would be EmailReadMessagValue("text"). This is dependent on if the sender included a plain text version of the email. If you want the HTML you can use EmailReadMessagValue("html") or EmailReadMessagValue("htmlRaw") if you don't want inline attachments to be converted to base64 data URLs. Please let me know if you have any questions!
  3. Hi bradQual, First, the parameter you pass into EmailReadMessageValue should be "attachments" instead of "attachments=true". EmailReadMessageValue("attachments") returns a return-separated list of paths to the attachments for a message. You will then need to loop through this list and call EmailReadAttachments(path) in a Set Field script step for each value in the list. This will put the attachment at (path) into the container field. You would either need multiple container fields or create a new record for each attachment. Storage options are entirely up to you. A side note, I highly recommend against modifying the Example Client. It was set up specifically to not download attachments at first and then download them on demand when a message is viewed. As you have discovered, it becomes quite convoluted trying to modify it to do exactly what you need. In my experience with other customers trying to do this, you will save yourself time and heartache by using the scripts as a general guide and then creating your own data structure and writing your own scripts in your solution.
  4. Hi Darren, There is not a function in the Email plugin that will output the HTML after the substitutions. Your approach is probably the best way to accomplish this. The only way I can think of to do this with solely the Email plugin would be to send the email to yourself ( or any other inbox you can access) first and then do a read on the inbox, pull the email in and parse the html out of it using EmailReadMessageValue("html").
  5. Hi Marc, CloudMail is hardcoded to only work for the US East region. We can modify CloudMail for you to run in the Ireland region. Our currently rate is $185/hr USD. If you are interested in this customization, please let me know and I will get you in contact with our project manager to discuss the project further and get you a quote.
  6. You can have multiple versions of Java installed on your machine. I suspect the preference panel is just showing the newest version of Java that is installed. Since Java 6 showed up when you ran that command in Terminal, you should be good as far as Java goes. That is a pretty old version (released in 2012). We have had quite a few updates to ScriptMaster since then including a compatibility release for FM14. I recommend download and installing version 4.42 for FM14 and 15 and seeing if that resolves the issue. You can download that here. Be sure to remove version 4.134 from the FM14 and FM15 extensions folders. Try that and let me know if you continue to have issues.
  7. Hi dmcs, I have run the Email plugin on Yosemite, El Capitan, and Sierra in FM11-FM15 and have not seen this error. Do you get this error in Windows? I would like to take a look at your plugin logs. Please send an email to support@360works.com and reference this thread. Reproduce the error and attach the plugin logs to the email. See this page for log locations. Please be sure to attach the logs and send the email before any restarts of FileMaker as restarting FileMaker overwrites the logs.
  8. This is expected behavior. The only way to see the functions in FileMaker Pro, regardless if the solution is hosted and the plugin is installed on the server, is to install the plugin in FileMaker Pro. This is the case with any FileMaker plugin. If you want to be able to run scripts with plugin functions from a hosted solution and not have to install the plugin locally, your scripts must be executed with the Perform Script on Server script step. Otherwise, the script will be executed locally and you will need to have the plugin installed for FMP. You will also need to install the plugin in FileMaker Pro for any machine that is going to be used to write the scripts, otherwise the plugin functions will not show up and you will see <function missing> in your pre-existing scripts. Assuming that the machine with FMP13 is a Mac, then you have Java 6 installed because our plugins will not operate without it installed. You can check to see if you have Java 6 installed by opening Terminal and typing: /usr/libexec/java_home -V Java 6 should be listed if you are able to enable our plugins in FMP 13. Do you have any of our other plugins installed? What version of ScriptMaster are you installing for FMP 14/15?
  9. Hi totoleheros, Make sure that you have Java 6 installed as it is a requirement to use our plugins in the Mac OS. You can download it here. Also make sure that you put the .fmplugin version of the plugin in the Extensions folder and not the .fmx or .fm64. Alternatively, you can place the plugin in a container field and use the "Install Plugin File" script step to install the plugin.
  10. Hi charlitoA, You can apply the cost of the Single User license to the Workgroup license. To do so, click on the "Pricing and Download Demo" button on the Email plugin product page. Once there, click on "Upgrade" under the Workgroup license tier. On the next page, enter in your existing license into the respective fields and click "Upgrade" next to the line that says "Upgrade from Single User to Workgroup". The plugin is the same for all license levels so you do not need to uninstall the file you already have. Please let me know if you have any questions!
  11. Hi Samr, I run this exact same configuration on my iMac on a daily basis without issue. Does the plugin show in the Admin console? Is it checked as enabled? If it doesn't show, try restarting the FileMaker script engine and rechecking. You also need to make sure that the option to "Enable FileMaker Script Engine (FMSE) to use plug-ins" is checked in the Admin console.
  12. Hi EdwinJ, Has anything changed on your mail server recently in regards to logging in? any other changes?
  13. If you are able to reproduce it, please let us know as this is something that we would definitely want to address. Send an email to support@360works.com with instructions and/or an example that reproduces it. Thank you!
  14. Hi Samr, You can have multiple versions of Java installed on a machine. You do not need to uninstall Java 8 to install Java 6.
  15. Hi Samr, Our plugins, including FTPeek, have always been compatible with FMS15 on a Mac. As long as you have Java 6 installed, the plugins will work fine in this environment. We are very close to finishing development on a new framework that doesn't have this requirement but for the time being it is still required. Are you having an issue getting it installed?
  16. Hi BrentHedden, I have not seen this reported before. Does it only happen with externally stored container fields? Are you sending to the same domain? Have you seen it happen across different domains? Does it happen with different mail clients? Different OS?
  17. HI RJS-IT, The error you are getting means that Java cannot complete the SSL handshake because the mail server you are trying to connect to either has a self-signed certificate or the certificate it has is not part of the Java trust store. Try adding the "forceTrust=true" parameter to the EmailConnectSMTP function call. This should force Java to trust the SMTP server's certificate and complete the SSL handshake.
  18. Chris, If you did not install Java 6 then it is definitely an issue, if not the entire issue. If you were having registration problems then you would be getting demo mode expired errors but it looks like the plugin has not initialized yet. Please let me know if you need anything else!
  19. Hi martincl, You can get the actual attachments into a container field. However, the example file is not currently set up to do this. In order to do this, you need to set "attachments=true" in the EmailReadMessages function call. This will tell the email plugin to download the attachments. When iterating through the emails, you will call EmailGetMessageValue("attachments"). This returns a return-separated list of paths to the attachments. You will then need to loop through that list and call Set Field(table:myfield;EmailReadAttachment(path)) to put the attachment into a container field.
  20. All of Agnes Riley's advice is solid. To elaborate on their first point, it looks like your FMS is running on a Mac and thus you must have Java 6 installed in order for the plugin to operate. Was the Java you installed Java 6? If not you can download it here. If you have Java 6, I have seen the Admin console not reflect information accurately. Restart the FMSE and the Admin Server using the fmsadmin utility. Once you have done that, log back into the Admin console and check if the plugin is enabled. Also make sure you are using the most current version of the plugin(2.17) . If you have done all of this and are still having issues, send an email to support@360works.com and reference this thread and we will get the issue sorted out.
  21. Hi Steven, In order for inline attachments to work with the Email plugin, you need to use contentIDs in your html <img src> tags and then reference them in the function EmailAttachfileInline. For example: EmailSetBody( "<html><body><img src=\"cid:headergif123\">" & " This is an HTML message with embedded images " & "<img src=\"cid:footergif456\">" & "</body></html>"; "html" ) and EmailAttachFileInline( Globals::headerContainer ; "headergif123" ) EmailAttachFileInline( Globals::footerContainer ; "footergif456" ) In this example the contentIDs (cid) are headergif123 and footergif456. These names are arbitrary. The first parameter in the EmailAttachFileInline function call can either be a field reference or a URL to the file. Let me know if you have any questions!
  22. For anyone else running into a similar issue: When installing our plugins on Windows, make sure that the plugin you are using matches the architecture (32/64bit) of FileMaker. ".fmx" is 32-bit ".fmx64" is 64-bit. You will also need to make sure that the architecture of Java matches the plugin and FileMaker Pro. Otherwise you will get the error message reported above.
  23. Hi Frankb3, Without being able to see your solution, it sounds like you could call the Go to Related Record script step and make sure that you mark the option for "match the current record". That should give you a found set of all the AUDIO records for a specific COPY record. Once you have that found set, you can create a loop that iterates through the records and calls EmailAttachFile(AUDIO::FILE) for each record. An alternative approach would be to do a Find in the AUDIO table for that specific COPY record's primary key. That should result in the same found set as the Go to Related Record script step. Hope that helps!
  24. Hi FoggyMt, For the first problem, try turning off the progress bars. You can do this by setting the parameter "progress=false" in the EmailSend function call. For the second problem, are you sending to the same account or are you sending this to multiple different recipients? If multiple, are they on the same domain? I have attached a simple test file that will test sending multiple attachments. Try sending attachments with it and see if you get the same results. EmailTest.fmp12
  25. Typically when we see this error, the license string and registered to names have been put in the opposite fields or the wrong license is being entered in. If you need to get back into demo mode for whatever reason after you have registered you will need to uninstall/reinstall SuperContainer.