Guide to Updating Plug-ins

Chapter 1
|
Setting up Auto Update in your database 11
To change the permissions for plug-in files on a Mac OS server:
1. Launch the Terminal application ([hard disk]/Applications/Utilities/Terminal).
2. Navigate to the parent folder of the file or folder whose permissions you intend to change and enter the
following at the command line:
chmod g+rx <filename or folder>
or
chmod g+wrx <filename or folder>
The g+rx is necessary because scripts and plug-ins must have the group read and executable bits
enabled. Use the g+wrx form to permit write permission as well. Some plug-ins or scripts that use
preferences or folders of additional files may require write permission to those files or folders.
Setting up Auto Update in your database
There are several ways to set up Auto Update in your database. This guide describes one way, which uses
simple script steps and global fields, and is based on the sample file named AutoUpdatePlugin.fp7 installed
with FileMaker Server.
Overview
To set up plug-in version checking in your database, you need to write a few simple script steps that run
when a client opens your database. The first directs FileMaker Pro to a start-up layout, which contains global
fields that store version information about your database’s plug-in requirements. This script calls a script
named Run Plug-in Scripts, which calls sub-scripts that check for the required plug-in on both the client and
server computers, collects version numbers of plug-ins that exist in these locations, compares them, and
downloads an updated plug-in from the server, if needed.
To set up plug-in version checking in your database
1. Open your database using FileMaker Pro and enable the Auto Update plug-in in the Preferences dialog
box.
Note Remind the server administrator to turn on Auto Update in the FileMaker Server Admin Console,
Database Server > FileMaker Pro Clients tab, to allow FileMaker
Pro clients to download updates
automatically.
2. Create a layout to contain:
1 fields defined with the global storage option to collect plug-in version information or result codes
1 a button to manually run the script that creates a plug-in version information file for storage on the
server
For an example layout that contains all the fields and the button you need, see the STARTUP layout in
the AutoUpdatePlugin.fp7 sample file.
3. Write a script that uses the FMSAUC_Version function, which returns the name and version of the Auto
Update plug-in available in FileMaker Pro. If the name and version string is not returned, FileMaker Pro
assumes the Auto Update plug-in is missing or isn’t enabled on the client computer.