Define whether this version should install for a given group of people. This may force a downgrade to an older version if needed and you discovered a problem with a newer version of a plugin. Once you have such a table for your script, you can fill it with plugins. 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. 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.
We have usually a check for GetAsText( Get (ApplicationArchitecture)) being "x86_64" to verify the FileMaker has 64-bit architecture. If you use Get ( SystemPlatform ) function in FileMaker, you can check platform. 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. Now you have the record for the plugin you need to install, you check the version of the current plugin. For MBS FileMaker Plugin you can do a query GetAsText(MBS(" Version")) to check whether plugin is installed. This is either "?", if the plugin is not installed or the current installed version.
#Baseelements plugin file modified code
BASEELEMENTS PLUGIN SERVER CODEĪlternatively to GetAsText you could check with Get(LastError) and get the error code for not having the plugin installed. For our plugin you can use GetAsNumber(MBS(" VersionAutoUpdate")) to query the version number to compare. This gives an 8 digit number always with version, e.g. Now you compare this version against your database entry. If you have the question mark, you can install plugin. If you have a version number, it may be older than the one you like to install and then you install an update. Please be aware that the user may have a newer plugin already installed, e.g. a beta version with a critical bug-fix for them. So don't downgrade them unless really required. Now you have a plugin in a container and you like to install it.
You call the Install Plug-In File script step in a script and pass the right container. Here is a list from Claris with the plugin errors:Įrror 1550: Cannot load the plug-in, or the plug-in is not a valid plug-in It is important to check Get (LastError) and Get (LastExternalErrorDetail) after the call and see whether the installation worked. Invalid plug-in signature, OSStatus error: Certificate name.
0 kommentar(er)
