jrhoogl.blogg.se

1. BASEELEMENTS PLUGIN SERVER HOW TO
2. BASEELEMENTS PLUGIN SERVER INSTALL
3. BASEELEMENTS PLUGIN SERVER PRO
4. BASEELEMENTS PLUGIN SERVER CODE

BASEELEMENTS PLUGIN SERVER INSTALL

You call the Install Plug-In File script step in a script and pass the right container. Now you have a plugin in a container and you like to install it.

So don't downgrade them unless really required. a beta version with a critical bug-fix for them. Please be aware that the user may have a newer plugin already installed, e.g. If you have a version number, it may be older than the one you like to install and then you install an update. If you have the question mark, you can install plugin. Now you compare this version against your database entry.

This gives an 8 digit number always with version, e.g. For our plugin you can use GetAsNumber(MBS(" VersionAutoUpdate")) to query the version number to compare.

BASEELEMENTS PLUGIN SERVER CODE

Alternatively to GetAsText you could check with Get(LastError) and get the error code for not having the plugin installed. This is either "?", if the plugin is not installed or the current installed version. For MBS FileMaker Plugin you can do a query GetAsText(MBS(" Version")) to check whether plugin is installed. Now you have the record for the plugin you need to install, you check the version of the current plugin. Just be aware that value 4 for Web Direct doesn't tell you whether you are on Windows, MacOS or Linux server, so check that separately, e.g. If you use Get ( SystemPlatform ) function in FileMaker, you can check platform. We have usually a check for GetAsText( Get (ApplicationArchitecture)) being "x86_64" to verify the FileMaker has 64-bit architecture. for current mode development/tester/usersĪnd then pick the newest file and check this for installation.Then in the scripts below you can make a search to find: Once the plugin needs to be pushed to everyone, you can change the target group from development to all users. You may have dozens of records there and have last final plugin version there to install for all users, but a newer beta version to install for development or testing only. Once you have such a table for your script, you can fill it with plugins. This may force a downgrade to an older version if needed and you discovered a problem with a newer version of a plugin. Define whether this version should install for a given group of people. The target groups like development, testers, users.Minimum and maximum FileMaker version, so you can have an older plugin for an older FileMaker version and a newer version for a newer FileMaker version.An active switch, so you can enable/disable this plugin.The platform for the given file: MacOS, Windows, Linux and 32/64bit if needed.The plugin name, as this can be used for multiple plugins.You may want to have the following fields: For example you can have a table which contains the plugin and metadata.

BASEELEMENTS PLUGIN SERVER HOW TO

When you plan to add automatic plugin install, you may need to think about the processes and how to define the table and the scripts. Especially if you manage a vertical solution with hundreds of customers running each servers and clients, you like to automate this. But same techniques apply for server installations for people with a lot of FileMaker servers.

BASEELEMENTS PLUGIN SERVER PRO

This is great when you have hundreds of FileMaker Pro installations and you need to use the plugin locally in your scripts. You can automate the installation of MBS FileMaker Plugin via the Install Plugin script step. Automatically install MBS FileMaker Plugin