![]() This will return an example of the sort of path used by the function. To get an example of the sorts of paths that the plugin uses, use the BE_SelectFile function in the Data Viewer, and choose a file with a known path. Windows : C:\Users\John Smith\Documents\test.xlsx Plugin Paths Examples Mac : /Users/John Smith/Documents/test.xlsx" So if you're mixing and matching FileMaker paths and plugin paths, you will need to convert them between the types in order to use them in other places. These file: prefixes that you get from things like the Get ( FilePath ) function and others, are unique to FileMaker and don't work anywhere else other than FileMaker itself, including not in the BE plugin. On the Mac, they usually start with /Volumes or /Users and on windows will be something like C:\Folder\Path.įileMaker paths often start with file: or filemac: and these WILL NOT work in the plugin. The paths used by the plugin are Operating System paths. Please note :įileMaker paths and plugin paths are not the same thing. For example: \My_Path\Database Server\Extensions\.Lots of the BE plugin functions use paths in the parameters or in values they return. If FileMaker Server is installed in a non-default location, the beginning portion of the default paths shown above, \Program Files\FileMaker\FileMaker Server, is replaced with the path that was specified during installation. The file permissions must allow the fmsadmin or claris group to read and execute the plug-in files. Plug-in files placed in this folder or sub-folders must be owned by the fmsadmin (FileMaker Server only) or claris (Claris Server only) group. If the Plugins folder does not exist, you must create it. See Changing plug-in file permissions (FileMaker Server only, macOS). ![]() To enable the FileMaker Data API to use plug-ins, you must place them in the proper folder on the primary machine in your FileMaker Server deployment.įileMaker Server only, Windows: :\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\wip\Plugins\įileMaker Server only, macOS: /Library/FileMaker Server/Web Publishing/publishing-engine/wip/Plugins/įileMaker Server only, Linux: /opt/FileMaker/FileMaker Server/Web Publishing/publishing-engine/wip/Plugins/Ĭlaris Server only, Linux: /opt/Claris/Server/WebPublishing/publishing-engine/wip/Plugins/įileMaker Server only, macOS: For FileMaker Server, you must set the correct file permissions for plug-ins. For all web publishing solutions (XML, PHP, and FileMaker WebDirect), place the plug-ins in this folder:įileMaker Server only, Windows: :\Program Files\FileMaker\FileMaker Server\Web Publishing\publishing-engine\cwpc\Plugins\įileMaker Server only, macOS: /Library/FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins/įileMaker Server only, Linux: /opt/FileMaker/FileMaker Server/Web Publishing/publishing-engine/cwpc/Plugins/Ĭlaris Server only, Linux: /opt/Claris/Server/WebPublishing/publishing-engine/cwpc/Plugins/ To enable the Web Publishing Engine to use a plug-in, place a copy of the plug-in on every machine in the deployment running a Web Publishing Engine (including the machine running the Database Server). ![]() To enable the FileMaker Script Engine to use plug-ins, you must place them in the proper folder on the primary machine in your FileMaker Server deployment.įileMaker Server only, Windows: :\Program Files\FileMaker\FileMaker Server\Database Server\Extensions\įileMaker Server only, macOS: /Library/FileMaker Server/Database Server/Extensions/įileMaker Server only, Linux: /opt/FileMaker/FileMaker Server/Database Server/Extensions/Ĭlaris Server only, Linux: /opt/Claris/Server/Extensions/ ![]()
0 Comments
Leave a Reply. |