![]() In the examples to follow, I will be using the BaseElements plugin version of the Base64 encode function. However, if you cannot use FileMaker 13-16 yet, there is still hope for you by using the fabulous free BaseElements plugin from Goya. If you are on the cutting edge, you already own a copy of FileMaker 13-16 which has Base64 encode and decode functions built right in. Why should you care about base64 encoding? Well, it allows you to convert an image into plain text which you can then embed directly into your html code and display the result in a Web Viewer! Not too much to ask right? I also wanted to store these images in a repeating container field along with the text and then reference them directly in the web viewer without having to export them or store them on a shared drive or web server somewhere. I wanted to have images embedded in the help so that they could be displayed within the context of the help. ![]() I wanted to create a help system for my clients using FileMaker’s web viewer. For example: \My_Path\Database Server\Extensions\.I have released a new version of the sample file which demonstrates how to use this technique to embed video files as well. 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. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |