Practically this means that plug-ins can’t show dialog boxes, progress bars, flash dialogs etc. For example Troi File Plug-in contains a function TrFile_SelectFileDialog, which shows a dialog to let a user select a file.
#Baseelements plugin functions code
#BASEELEMENTS PLUGIN SERVER CODE#Īs this is not allowed, this function won’t work on Server, and will return the error code kErrNotAvailableOnServer. When you run a plug-in server-side, it will run in the context of the FileMaker Server application. FileMaker Server runs in a non-logged-in state and does not have permissions. You should be aware of this when you use a plug-in such as Troi File Plug-in: as long as you are targeting files or folders inside the Server Documents folder you should be OK, but outside of that you are likely to get permission errors.
64-bit plug-ins are needed for FileMaker Server 13 and laterįileMaker Server 13 and later and WebDirect are 64-bit processes, for which plug-ins need to be compiled for 64-bit. On Windows 64-bit plug-ins have a different extension: fm圆4. In the download of a 64-bit compatible plug-in you will find this extra copy of the plug-in. Plug-ins for macOS can be universal and the extension is always the same: fmplugin. A universal plug-in is a single plug-in that will run on a 32-bit process as well as on 64-bit process. You can not easily see if a macOS plug-in is 64-bit compatible. We have created a simple dropper app called “Troi Architecture Check” to determine for which architectures a plug-in is compiled.
You can download the app here.Ī plug-in running on FileMaker Server 13 or later and WebDirect does not run in the background.
0 kommentar(er)
