Drew Wesley

I loaded the iText jar, registered the function, but in text viewer, I'm getting this string: com.itextpdf.text.pdf.PdfReader@17361e2 What am I doing wrong? Thanks!

A new FMP7Script protocol that launches a url-defined script is available for FM Go. "Opening files using the fmp7 script protocol with FileMaker Go" http://help.filemaker.com/app/answers/detail/a_id/7786/~/opening-files-using-the-fmp7-script-protocol-with-filemaker-go Syntax: FMP7Script://192.168.10.0/Client.fp7?script=ListClients&param=TopClients&$NumberToList=10 I've been running some tests on a Windows machine to register this protocol for use on a desktop environment. [color:gray]--- Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOTFMP7Script] @="URL:FMP7Script Protocol" "URL Protocol"="" [HKEY_CLASSES_ROOTFMP7Scriptshellopencommand] @="C:Program FilesFileMakerFileMaker Pro 11 AdvancedFileMaker Pro Advanced.exe %1" --- Results so far: I can partially register the protocol so my shortcut shows the FMP icon and calls the application, but get an error when using the %1 suffix in the registry: 'The file "t://192.168.10.0/Client.fp7" could not be opened. (Not Found)' Changing the %1 suffix to a %2 (or any other single-digit number) doesn't produce the error and calls the application : , but also doesn't prompts for authentication. : I don't understand why FileMaker, Inc. released the upgraded protocol for their FM Go "mobile app" before the FMP desktop versions. A silver lining is that there doesn't seem to be any server requirements.

I found this bit of information in the help file included in FileMaker Server 9: http://localhost:16000/admin-help/en/wwhelp/wwhimpl/js/html/wwhelp.htm If you enable SSL on the web server, then you must use the Deployment assistant to configure FileMaker Server to use the HTTPS protocol to communicate with the web server. The Deployment assistant tries to detect your web server using the HTTP protocol, so if your web server uses HTTPS, the Deployment assistant fails to detect the web server and prompts you for more information. In the Deployment assistant’s Web Server Test Failed step, select HTTPS and continue. See Changing a FileMaker Server deployment. So if you already have Web Publishing setup, 1. Open the Admin Console. 2. Select the 'Edit Server Deployment' link. 3. Keep web server turned on with SSL and have the Deployment Assistant 'try' to detect the web server. It will keep searching. 4. Stop the web server to trigger the 'cannot find web server' window. 5. Select the HTTPS radio, enter the server's IP address, and enter the https port (443). 6. Start the web server. 7. If you get errors, restart FileMaker Server.

I'm trying to find a suitable url plug-in that can grab html off websites and run in a server-side script. Troi URL works on the client only, and ScriptMaster proposes a vulnerability in a shared-server system with its vast array of file functions. Are there any other plug-ins that can do the job?