![]() Getting the Plugin into a container field This could be a single record Plugins table you create just for this purpose, or could be global fields that you set in the file when it's not hosted.Īll of the scripted methods require that the BaseElements plugin is first inside a FileMaker container field. So one for Win32, Win64, Mac and Linux, or only one if you are only ever on a single platform. If you're starting from scratch to build this yourself, it's not complex, but there are a few steps.Ĭreate a FileMaker file ( or use a table in an existing file, or create a new table) with container fields to store all of the versions of the plugin you need to install. You can use a script that runs via the On First Window Open trigger, to check for the latest version and install it if required. The scripted install is the best way to keep plugins up to date on any system that is being used constantly and where you want to check that the plugin is active before you let a user do tasks that require the plugin. Recommended : Scripted Installation for Client or Server There's also different locations on server for different functionality, so a plugin that does a calculation that displays in WebDirect will need to be installed for that, and will be a different location than one for Perform Script on Server scripts.Īlso when you use plugin functions inside stored calculation fields, these can often be evaluated on the server, so the plugin needs to be installed there too. ![]() ![]() And some behaviours, especially around file paths, will be different on each platform. Each FileMakerPro client will need to have a copy of the plugin installed locally for them to be able to use plugin functions inside scripts and calculations that run on the client.Įach FileMaker Pro client with a different OS needs a different plugin - so there are different files for Mac vs Windows for example. You can install plugin on FileMaker server - this doesn't not do anything for FileMaker clients being able to use plugin functions though. The first thing to understand is the difference between a server and client install. fmplugin file, now what do you do? Server vs Client installs Source: BaseElements Plugin Updated to 3.You've downloaded the plugin file, and got a. It doesn’t cover all our costs, but it does help, and you get a proper support channel and a bunch of other cool plugin related code.īesides SMTP, the new version contains an EvaluateJavascript function, Gzip and UnGzip, Values_ContainsDuplicates, and much more. It’s because of their support that you get all this for free, so if you use the plugin and know someone who sponsors, make sure to buy them a round.Īnd if you can, please consider sponsoring. Thanks again to all the people and companies that sponsor the plugin. The documentation will be updated in the next few days, I’ll post another note here when it’s done. And BE_ImportFile for importing files into containers – you can do this in the client, but now you can also do it on the server via the plugin. There’s the ability to evaluate JavaScript inside the plugin, which opens a whole world of possibilities. There’s a ConvertContainer for turning a file to a picture and vice versa, so no more exporting and re-importing. This version removes support for Windows XP, so be aware of that if you’re running older OS versions.īut in return you get SMTP along with JPEG compression for reducing container picture sizes. This is a huge release, lots of cool new features. Big news last month from Goya: Their free BaseElements Plugin has been updated to 3.1, and now supports SMTP and a host of other new features:Īnd one more release note, we’ve updated the free BaseElements Plugin to 3.1.0.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |