Home > Designing and creating databases > Creating a database > Working with plug-ins > Installing plug-ins

Installing plug-ins

Database developers can insert plug-in files in container fields, then use scripts and calculations to install and update plug-ins.

Note  If you are concerned that unwanted plug-ins might be installed when you use solution files on a trial basis, you can disable the Allow Solutions to Install Files option in the plug-in preferences. However, be aware that the solution file may not behave as intended if you don’t allow required plug-ins to install. See Setting plug-in preferences.

To install a plug-in file:

1.	Create a container field. See About container fields.

2.	Do one of the following:

•	In Browse mode, select the container field, choose Insert menu > Insert File, select a plug-in file, then click Open.

•	Write a script and use the Insert File script step to place the plug-in the container field. See Creating and editing scripts and Insert File.

3.	Create a script and use the Install Plug-In File script step to specify the container field as the target field. See Install Plug-In File.

4.	Run the script to install the plug-in.

FileMaker Pro installs plug-ins in the following locations:

 

Operating system	Product	Plug-ins are installed in this folder
Windows 7 or Windows 8	FileMaker Pro	C:\users\user_name\AppData\Local\FileMaker\FileMaker Pro\13.0\Extensions\
	FileMaker Pro Advanced	C:\users\user_name\AppData\Local\FileMaker\FileMaker Pro Advanced\13.0\Extensions\
OS X	FileMaker Pro	Macintosh HD/Users/user_name/Library/Application Support/FileMaker/FileMaker Pro/13.0/Extensions
	FileMaker Pro Advanced	Macintosh HD/Users/user_name/Library/Application Support/FileMaker/FileMaker Pro Advanced/13.0/Extensions

Tip  You can use the Get(InstalledFMPlugins) function to identify the version of the installed plugin and compare it with the version of the plug-in stored in the container field, then update the plug-in by reinstalling, if necessary. See Updating plug-ins and Get(InstalledFMPlugins).

Notes

•	If a plug-in has been disabled in the client’s plug-in preferences, it will install but will not be accessible to FileMaker Pro until it is manually enabled by the user.

•	You cannot install multiple versions of a plug-in to support multiple versions of FileMaker Pro.

•	If your solution requires a specific plug-in version that cannot be shared with other versions of FileMaker Pro, instruct users to manually place plug-ins in the Extensions folder inside the FileMaker Pro, FileMaker Pro Advanced, or FileMaker runtime folder.

•	If a plug-in is intended for all installed versions of FileMaker Pro, you must manually install the plug-in in each user’s Application Support/FileMaker/Extensions folder.

•	The search order for loading plug-ins starts with the Extensions folder inside the FileMaker Pro application folder, followed by the folder that the Install Plug-In File script step uses. The last location checked is the Application Support/FileMaker/Extensions folder.

•	FileMaker Pro will not load a plug-in if it has already loaded a plug-in with the same plug-in ID.

•	OS X: Plug-ins stored in container fields are compressed by default.

Related topics 

Creating custom plug-ins