What is the fmp: URL protocol?
This is a special url, prefixed with fmp, that is answered by FileMaker Pro (or Go) instead of by your browser. These URLs can contain scripts and script parameters and it is by opening URLs like this that DayBack Calendar can talk to FileMaker Pro.
The url protocol itself (the prefix) is registered with your operating system when FileMaker is installed. If you install more than one copy or uninstall lots of copies you can mess up this linkage of the URL with the most recent version of FileMaker and *no application* will answer the URL.
FIleMaker 16: Changes Required
FileMaker introduced a new extended privilege in FileMaker 16 that permits the FMP URL protocol to function. The first time you open DayBack, ProMaps, or any webviewer-heavy solution in 16 without this privilege enabled, you'll see this error:
The fix is simply to enable the new privilege. Here's how.
- 1. Select File / Manage / Security from the FileMaker menus.2. Click on the "Extended Privileges Tab", then double-click the "fmurlscript" keyword.3. Check "on" for any privilege sets you wish to be able to use DayBack.4. That's it! Click "refresh" in DayBack and you should be all set.
Why did FileMaker make this change? They believed that malicious users who knew your script names could trigger them from URLs even if you didn't provide buttons for those scripts. But users would still need to be logged into FMP with sufficient permission to run the script: the FMP URL doesn't bypass FileMaker security in any way.
Version 9.69 of DayBack includes a test to see if FileMaker is listening for these URLs: if you see an error stating that the fmp:// URL isn't working, the best way to fix it is to uninstall and the reinstall FileMaker Pro. More below.
Testing & Fixing the FMP URL Protocol
You can verify that your fmp url calls are working correctly by opening DayBack, then clicking on following link: fmp://$/DayBack.fmp12?script=Unused¶m=run
If you receive a popup in FileMaker with the message "This button is not yet assigned to anything", your fmp url calls are working correctly.
If the above test fails to run, or gives you a different error message, your fmp url calls are not functioning properly. Fortunately this is pretty easy to fix...
and you'll find an array called LSHandlers and a sub-array called LSHandlerURLScheme... In some cases you'll see that was pointing to fmp and not fmpa13. This doesn't appear to be in the same place for every version of MacOSX.
- 1. Open Regedit and Backup your registry. (Instructions Here)
- 2. Find the following key:
- 3. Modify the "(Default)" value with the path to the version of FileMaker you'd like to use by default with the following added at the end: %1. for example:
C:\Program Files\FileMaker\FileMaker Pro 15 Advanced\FileMaker Pro Advanced.exe %1