FileMaker Server 8 Advanced ® Custom Web Publishing Guide
© 2004-2005 FileMaker, Inc. All Rights Reserved. FileMaker, Inc. 5201 Patrick Henry Drive Santa Clara, California 95054 FileMaker is a trademark of FileMaker, Inc., registered in the U.S. and other countries, and ScriptMaker and the file folder logo are trademarks of FileMaker, Inc. All persons and companies listed in the examples are purely fictitious and any resemblance to existing persons and companies is purely coincidental. FileMaker documentation is copyrighted.
Contents Chapter 1 Introducing Custom Web Publishing About this guide Creating dynamic web sites with the Web Publishing Engine About Custom Web Publishing with XML About Custom Web Publishing with XSLT About the tools for developing XSLT stylesheets Web publishing requirements What is required to publish a database using Custom Web Publishing What web users need to access a Custom Web Publishing solution Connecting to the Internet or an intranet Key features in Custom Web Publishing with XML and XSLT FileM
FileMaker Server Advanced Custom Web Publishing Guide Accessing XML data via the Web Publishing Engine About namespaces for FileMaker XML About FileMaker database error codes Retrieving the document type definitions for the FileMaker grammars Using the fmresultset grammar Description of elements in the fmresultset grammar Example of XML data in the fmresultset grammar Using other FileMaker XML grammars Description of elements in the FMPXMLRESULT grammar Example of XML data in the FMPXMLRESULT grammar De
| Chapter 5 Developing FileMaker XSLT stylesheets Using XSLT stylesheets with the Web Publishing Engine About the FileMaker XSLT Extension Function Reference About the URL syntax for FileMaker XSLT stylesheets About the URL syntax for FileMaker container objects in XSLT solutions Using query strings in FileMaker XSLT stylesheets Specifying an XML grammar for a FileMaker XSLT stylesheet About namespaces and prefixes for FileMaker XSLT stylesheets Using statically defined query commands and query parameters
FileMaker Server Advanced Custom Web Publishing Guide Chapter 6 Testing and monitoring a site Testing a Custom Web Publishing site Examples of stylesheets for testing XML output Monitoring your site Using the web server access and error logs Using the Web Publishing Engine application log Using the Web Server Module error log Using Web Publishing Core internal access logs Appendix A Valid names used in query strings About the query commands and parameters Obsolete request names and parameters Guideline
| Using the query parameters –db (Database name) query parameter –encoding (Encoding XSLT request) query parameter –field (Container field name) query parameter fieldname (Non-container field name) query parameter fieldname.op (Comparison operator) query parameter –grammar (Grammar for XSLT stylesheets) query parameter –lay (Layout) query parameter –lay.
FileMaker Server Advanced Custom Web Publishing Guide Appendix C Converting CDML solutions to FileMaker XSLT About the process of converting CDML solutions to FileMaker XSLT solutions Conversion of CDML action tags, variable tags, and URLs Conversion of the –error and –errornum CDML variable tags Conversion of obsolete CDML action tags Conversion of supported CDML action tags Conversion of obsolete CDML variable tags Conversion of supported CDML variable tags Conversion of CDML boolean parameters to XPa
Chapter 1 Introducing Custom Web Publishing With FileMaker® Server Advanced, you can publish FileMaker databases on the Internet or an intranet in these ways: 1 1 1 Custom Web Publishing using Extensible Markup Language (XML) Custom Web Publishing using Extensible Stylesheet Language Transformations (XSLT) stylesheets Instant Web Publishing. See the FileMaker Instant Web Publishing Guide.
FileMaker Server Advanced Custom Web Publishing Guide About this guide This guide assumes you are experienced with XML and XSLT, developing web sites, and using FileMaker Pro to create databases.
Chapter 1 1 1 1 1 1 | Introducing Custom Web Publishing 11 Security: As the administrator for the Web Publishing Engine, you can individually enable or disable Instant Web Publishing, XML web publishing, or XSLT web publishing for all databases hosted by the server. As the FileMaker database owner, you can control web user access to Instant Web Publishing, XML web publishing, or XSLT web publishing for each database.
FileMaker Server Advanced Custom Web Publishing Guide About the tools for developing XSLT stylesheets FileMaker Server Advanced includes two tools for developing XSLT stylesheets: 1 1 The FileMaker Site Assistant is an application you can use to create basic XSLT stylesheets as a starting point for Custom Web Publishing with XSLT. The Site Assistant is a good way to learn how FileMaker XSLT stylesheets are constructed.
Chapter 1 | Introducing Custom Web Publishing 13 Connecting to the Internet or an intranet When you publish databases on the Internet or an intranet, the host computer must be running FileMaker Server, and the databases you want to share must be hosted and available. In addition: 1 1 It is strongly recommended that you publish your database on a computer with a full-time Internet or intranet connection.
1 1 FileMaker Server Advanced Custom Web Publishing Guide Some new query commands and parameters have been added, and some have become obsolete. To access data in a database, you must specify a layout. For security reasons, accessing data without specifying a layout is no longer supported. See appendix A, “Valid names used in query strings.” Each web user can have a unique global field value that persists as long as a session is active. For general information on global fields, see FileMaker Pro Help.
Chapter 1 1 1 | Introducing Custom Web Publishing 15 Some scripts that work with one step from a FileMaker Pro client may require an additional Commit Record/Request step to save the data to the host. Because web users don’t have a direct connection to the host, they aren’t notified when data changes. For example, features like conditional value lists aren’t as responsive for web users because the data must be saved to the host before the effects are seen in the value list field.
FileMaker Server Advanced Custom Web Publishing Guide Script step Behavior in Custom Web Publishing solutions Go to Field You cannot use Go to Field to make a particular field active in the web browser, but you can use this script step in conjunction with other script steps to perform tasks. For example, you can go to a field, copy the contents, go to another field and paste the value. To see the effect in the browser, be sure to save the record with the Commit Record script step.
Chapter 1 | Introducing Custom Web Publishing 17 Where to go from here Here are some suggestions for what to do and where to find information in the documentation to get started developing Custom Web Publishing solutions: 1 1 1 1 If you haven’t already done so, use FileMaker Server Administration and the Web Publishing Engine Administration Console to enable Custom Web Publishing. See FileMaker Server Administration Help and the FileMaker Server Advanced Web Publishing Installation Guide.
FileMaker Server Advanced Custom Web Publishing Guide
Chapter 2 Preparing databases for Custom Web Publishing Before you can use Custom Web Publishing with a database, there are some steps you must take to prepare the database and protect it from unauthorized access. Enabling Custom Web Publishing in a database You must enable Custom Web Publishing in each database you want to publish. You can individually enable either Custom Web Publishing with XML or Custom Web Publishing with XSLT, or you can enable both technologies in each database.
FileMaker Server Advanced Custom Web Publishing Guide Here is a summary of what happens when a web user uses a Custom Web Publishing solution to access a database: 1 1 1 If you have not assigned a password for an account, web users only specify the account name. If the Guest account is disabled, then users will be prompted for account name and password when they access the database. The account must have a Custom Web Publishing extended privilege enabled.
Chapter 2 | Preparing databases for Custom Web Publishing 21 Web server support for Internet media types (MIME) Your web server determines the support for the current MIME (Multipurpose Internet Mail Extensions) types registered for the Internet. The Web Publishing Engine does not change a web server’s support for MIME. For more information, see the documentation for your web server.
FileMaker Server Advanced Custom Web Publishing Guide
Chapter 3 Accessing XML data with the Web Publishing Engine You can obtain and update FileMaker data in Extensible Markup Language (XML) format by using the Web Publishing Engine. In the same way that HTML has become the standard display language for communication on the World Wide Web, XML has become the standard language for structured data interchange. Many individuals, organizations, and businesses use XML to transfer product information, transactions, inventory data, and other business data.
1 1 1 1 1 FileMaker Server Advanced Custom Web Publishing Guide You can dynamically access XML data from FileMaker databases by using URL requests with the Web Publishing Engine. The FileMaker Pro XML export feature generates a pre-specified XML data file. Working with XML data via the Web Publishing Engine is an interactive operation. FileMaker Pro XML import and export is a batch operation. The Web Publishing Engine can access XML data from a FileMaker portal, but FileMaker Pro cannot.
Chapter 3 | Accessing XML data with the Web Publishing Engine 25 General process for accessing XML data from the Web Publishing Engine Here is an overview of the process for using the Web Publishing Engine to access XML data in a FileMaker database: 1. In the Web Publishing Engine Administration Console, make sure XML Publishing is enabled. See FileMaker Server Advanced Web Publishing Installation Guide. 2.
FileMaker Server Advanced Custom Web Publishing Guide What’s new in the URL syntax for XML data In FileMaker Server versions 7 and 8, the Web Publishing Engine uses a URL syntax for accessing XML data. 1 FileMaker Pro 6 and earlier versions used the following syntax in requests for XML data: FMPro? This syntax has changed. See the next section, “About the URL syntax for XML data.
Chapter 3 | Accessing XML data with the Web Publishing Engine 27 About the URL syntax for FileMaker container objects in XML solutions In a generated XML document for an XML solution, the syntax used to refer to a container object is different for container fields that store the actual object in the database, as opposed to container fields that store a reference to the object.
FileMaker Server Advanced Custom Web Publishing Guide About URL text encoding The URLs for accessing XML data and container objects must be encoded in UTF-8 (Unicode Transformation 8 Bit) format. See “About UTF-8 encoded data” on page 36. For example, to set the value of the info field to fiancée, you could use the following URL: http://server.company.com/fmi/xml/fmresultset.
Chapter 3 | Accessing XML data with the Web Publishing Engine 29 About namespaces for FileMaker XML Unique XML namespaces help distinguish XML tags by the application they were designed for. For example, if your XML document contains two elements, one for FileMaker XML data and another for Oracle XML data, the namespaces will identify the element for each. The Web Publishing Engine generates a default namespace for each grammar.
FileMaker Server Advanced Custom Web Publishing Guide For example: http://192.168.123.101/fmi/xml/fmresultset.xml?–db=employees&–lay=family&–findall Note When specifying the fmresultset grammar, be sure to use lowercase. The Web Publishing Engine will generate an XML document using the fmresultset grammar.
Chapter 3 | Accessing XML data with the Web Publishing Engine 31 The element represents a portal. Each related field in a portal is represented by the element contained within the element. If there are multiple related fields in a portal, the field definitions for the related fields are grouped within a single element.
FileMaker Server Advanced Custom Web Publishing Guide Paul Cezanne Vault 07/07/1997 Home 08/01/2001
Chapter 3 | Accessing XML data with the Web Publishing Engine 33 To use the FMPXMLLAYOUT grammar, specify the following grammar name with the –view query command in the URL requesting the XML document from the Web Publishing Engine: FMPXMLLAYOUT.xml For example: http://192.168.123.101/fmi/xml/FMPXMLLAYOUT.xml?–db=employees&–lay=family&–view Note When specifying the FMPXMLRESULT and FMPXMLLAYOUT grammars, be sure to enter the grammar name in uppercase.
FileMaker Server Advanced Custom Web Publishing Guide
Chapter 3 | Accessing XML data with the Web Publishing Engine 35 For date, time, and timestamp fields, data for value lists are formatted using the “fm” format for that field type. The “fm” formats are MM/dd/yyyy for date, HH:mm:ss for time, and MM/dd/yyyy HH:mm:ss for timestamp. See “Using the date, time, and day extension functions” on page 72.
FileMaker Server Advanced Custom Web Publishing Guide About UTF-8 encoded data All XML data generated by the Web Publishing Engine is encoded in UTF-8 (Unicode Transformation 8 Bit) format. This format compresses data from the standard Unicode format of 16 bits to 8 bits for ASCII characters. XML parsers are required to support Unicode and UTF-8 encoding.
Chapter 3 | Accessing XML data with the Web Publishing Engine 37 This section contains a summary of the FileMaker query commands and parameters. For more information about using them in a query string, see appendix A, “Valid names used in query strings.” Note The Web Publishing Engine also supports an additional query command (–process) and three query parameters that are defined for use only with FileMaker XSLT stylesheets. See “Using query strings in FileMaker XSLT stylesheets” on page 54.
FileMaker Server Advanced Custom Web Publishing Guide Use these query parameter names With these query commands –script.param (pass a parameter value to the Optional with –script script specified by –script) –script.prefind (perform script before –find, –findany, and –findall) Optional with –find, –findany, –findall –script.prefind.param (pass a parameter value Optional with –script.prefind to the script specified by –script.prefind) –script.
Chapter 3 | Accessing XML data with the Web Publishing Engine 39 6. Sort the resulting data, if a sort was specified. 7. Process the –lay.response query parameter to switch to a different layout, if this is specified. 8. Process the –script query parameter, if specified. 9. Generate the XML document. If one of the above steps generates an error code, the request processing stops; any steps that follow are not executed. However, any prior steps in the request are still executed.
FileMaker Server Advanced Custom Web Publishing Guide Based on this request, the Web Publishing Engine will include the following processing instruction in the XML document: Copy or place the stylesheet for client-side processing on the web server in the location specified by the absolute path in the URL for the HREF attribute.
Chapter 4 Introduction to Custom Web Publishing with XSLT You can use FileMaker XSLT stylesheets to transform, filter, or format XML data for use in a web browser or in other programs and applications. This chapter introduces FileMaker XSLT stylesheets and two tools to help you get started creating XSLT stylesheets—the Site Assistant and the CDML Converter. For more detailed information about how FileMaker XSLT stylesheets are constructed, see chapter 5, “Developing FileMaker XSLT stylesheets.
FileMaker Server Advanced Custom Web Publishing Guide Getting started using Custom Web Publishing with XSLT If you know standard XML and XSLT, then you can immediately start using the Web Publishing Engine after learning a few unique details about FileMaker XML and XSLT, such as how to use the FileMakerspecific XSLT extension functions and query commands and parameters. The Site Assistant and the CDML Converter are tools to help you get started creating stylesheets and learn how they are constructed.
Chapter 4 | Introduction to Custom Web Publishing with XSLT 43 General steps for using Custom Web Publishing with XSLT Here is a summary of the steps for using Custom Web Publishing with XSLT: 1. In the Web Publishing Engine Administration Console, make sure XSLT Publishing is enabled. See the FileMaker Server Advanced Web Publishing Installation Guide. 2.
FileMaker Server Advanced Custom Web Publishing Guide Using the FileMaker Site Assistant to generate FileMaker XSLT stylesheets The FileMaker Site Assistant is an application you can use to create basic XSLT stylesheets as a starting point for use with Custom Web Publishing with XSLT. The Site Assistant is a good way to learn how FileMaker XSLT stylesheets are constructed. You can then use your own XSLT stylesheet authoring or text editing tools to modify the stylesheets as necessary.
Chapter 4 | Introduction to Custom Web Publishing with XSLT 45 Starting the Site Assistant To start the Site Assistant, do one of the following: 1 Double-click the FileMaker Site Assistant application icon. 1 Windows: Click the Start button, and choose FileMaker Site Assistant from the Programs menu. FileMaker Site Assistant Using the Site Assistant For detailed information and step-by-step procedures for using the Site Assistant, see the Site Assistant Help.
FileMaker Server Advanced Custom Web Publishing Guide About the Site Assistant’s generated stylesheets The XSLT stylesheets generated by the Site Assistant include several FileMaker-specific processing instructions, elements, and parameters. Here are a few examples of what is included: 1 The processing instruction specifies the XML grammar to use and statically defines the name of the database you chose in the Site Assistant.
Chapter 4 | Introduction to Custom Web Publishing with XSLT 47 Installing the CDML Converter For information about installing the CDML Converter, see the FileMaker Server Advanced Web Publishing Installation Guide.
FileMaker Server Advanced Custom Web Publishing Guide 5. For Destination Folder, click Select to specify the folder where you want to store the converted XSLT stylesheets and other files from the CDML web site. The CDML Converter creates a folder hierarchy and a set of files in the destination folder that correspond to the source files. The CDML Converter copies files from the source folder that do not require CDML conversion, such as the GIF files in an images subfolder, without changing them.
Chapter 4 | Introduction to Custom Web Publishing with XSLT 49 For more information about the CDML to XSLT mapping rules and other situations where you will have to manually fix XSLT statements because the CDML tag conversion could not be done, see appendix C, “Converting CDML solutions to FileMaker XSLT.” Notes 1 1 If there are any query parameters that reference CDML format files from database fields, you will need to manually update the references in the database.
FileMaker Server Advanced Custom Web Publishing Guide 3. If a database container field stores a file reference instead of an actual file, then the referenced container object must be stored in the FileMaker Pro Web folder when the record is created or edited, and then copied or moved to a folder with the same relative location in the root folder of the web server software. See “About publishing the contents of container fields on the web” on page 21.
Chapter 5 Developing FileMaker XSLT stylesheets This chapter contains information about how FileMaker XSLT stylesheets are constructed and how to use the FileMaker XSLT extension functions. Using XSLT stylesheets with the Web Publishing Engine When developing and using XSLT stylesheets to request FileMaker XML data via the Web Publishing Engine, be aware of the following points: 1 1 1 1 To use an XSLT stylesheet with the Web Publishing Engine, you must specify the name of the XSLT stylesheet in a URL.
FileMaker Server Advanced Custom Web Publishing Guide To construct a request, the Web Publishing Engine begins by using any query command and query parameters that are statically defined in the optional processing instruction. The statically defined query command and parameters become the base request.
Chapter 5 | Developing FileMaker XSLT stylesheets 53 About the URL syntax for FileMaker container objects in XSLT solutions In a generated XML document for an XSLT solution, the syntax used to refer to a container object is different for container fields that store the actual object in the database, as opposed to container fields that store a reference to the object.
FileMaker Server Advanced Custom Web Publishing Guide Using query strings in FileMaker XSLT stylesheets When using a query string in a URL or in the processing instruction in a FileMaker XSLT stylesheet, you can include any of the query commands and parameters that are defined for requesting XML data from a FileMaker database. See “Using FileMaker query strings to request XML data” on page 36.
Chapter 5 | Developing FileMaker XSLT stylesheets 55 About namespaces and prefixes for FileMaker XSLT stylesheets Unique XSLT namespaces help distinguish XSLT tags by the application they were designed for. In the element at the start of all FileMaker XSLT stylesheets, declare the namespaces for the FileMaker XSLT extension functions and the particular grammars you are using in the stylesheet.
FileMaker Server Advanced Custom Web Publishing Guide where: name is a string that is the name of a query command, query parameter, or database field. value is an arbitrary length string value. For query parameters and field names, use the particular value you want to define, such as “–db=products”. For query commands, don’t specify an equals (“=”) sign or a value after the command name, such as –findall. See appendix A, “Valid names used in query strings.
Chapter 5 | Developing FileMaker XSLT stylesheets 57 After the Web Publishing Engine determines the encoding, that encoding is used and no further steps are taken to determine the encoding. For example, if the charset attribute is set in the Content-Type request header, the Web Publishing Engine does not use the value of the –encoding query parameter.
FileMaker Server Advanced Custom Web Publishing Guide About the encoding of XSLT stylesheets In addition to the encoding for requests and output pages, the encoding of your XSLT stylesheets must be specified in the encoding attribute of the XML declaration at the top of the stylesheet. You can use any of the text encodings listed in the table on page 57. For example, this declaration specifies UTF-8 as the encoding of the stylesheet:
Chapter 5 | Developing FileMaker XSLT stylesheets 59 Using the FileMaker XSLT extension functions and parameters The FileMaker XSLT extension functions are defined to be in the fmxslt namespace. Make sure you include a declaration of the fmxslt namespace in the element at the start of your XSLT stylesheet. See “About namespaces and prefixes for FileMaker XSLT stylesheets” on page 55.
FileMaker Server Advanced Custom Web Publishing Guide An XML document fragment is loaded into the request-query parameter in the following grammar: ] Note The query information is defined to be in the namespace fmq="http://www.filemaker.com/xml/query".
Chapter 5 | Developing FileMaker XSLT stylesheets 61 Using the Web Publishing Engine base URI parameter The Web Publishing Engine defines the base Uniform Resource Identifier (URI) parameter to be the host and port where the Web Publishing Engine is installed. The base URI allows requests for XML data from FileMaker databases to be resolved in relation to the Web Publishing Engine host.
FileMaker Server Advanced Custom Web Publishing Guide To load a password-protected XML document that requires a different user name and password than what was specified in the parent request, then use the following syntax to specify the user name and password as part of the URI that is passed to the document() function: http://username:password@hostname/path?querystring To load an XML document that is not based on a FileMaker database, use the document() function without FileMaker query commands or que
Chapter 5 | Developing FileMaker XSLT stylesheets 63 Using content buffering When content buffering is disabled, the Web Publishing Engine streams the result of an XSLT transformation directly back to the client. Content buffering is always disabled unless you explicitly enable it. If you enable content buffering, the Web Publishing Engine stores the transformed content until the entire transformation is finished. Content buffering is required for XSLT stylesheets that manipulate headers.
FileMaker Server Advanced Custom Web Publishing Guide If the client does not allow cookies, the page includes: hyperlinked text If the Web Publishing Engine detects that the client allows cookies, then the fmxslt:session_encode_url() function stores the session ID in a cookie instead of the URL. Note Session information does not persist after the Web Publishing Engine is restarted.
Chapter 5 | Developing FileMaker XSLT stylesheets 65 Here is an example of creating a session and then storing a favorite color in the session: true PAGE 66FileMaker Server Advanced Custom Web Publishing Guide Notes 1 In each of the three forms of the fmxslt:send_email () function, the smtpFields parameter is a URL-encoded string of any length that contains the address and subject information using the following format, which is based on RFC 2368, the mailto URL scheme: username@host?name1=value1&name2=value2... where username@host specifies a recipient.
Chapter 5 1 | Developing FileMaker XSLT stylesheets 67 The fmxslt:send_email(String smtpFields, String xsltFile, Node xml, boolean includeImages) function sends an email message consisting of XML data that is processed by the email stylesheet you specify in this function. 1 For the xsltFile parameter, specify the name of the email stylesheet by entering a URL that is relative to the main processing stylesheet file for the request.
FileMaker Server Advanced Custom Web Publishing Guide The following example demonstrates how to set the value of the header. Suppose you are using a stylesheet to output a vCard. There is a potential problem that when a browser tries to load the stylesheet page, the browser could interpret the .xsl file as a stylesheet rather than a vCard. If you use the header called ContentDisposition, you can specify that there is an attachment with an extension of .vcf.
Chapter 5 | Developing FileMaker XSLT stylesheets 69 Using the string manipulation extension functions You can use the string manipulation functions to change the encoding of strings of any length. String manipulation extension function Data type returned fmxslt:break_encode(String value) string Returns an HTML break-encoded string. Characters such as “&” (ampersand) are replaced with “&”. New line characters such as line feeds and carriage returns are replaced with
.
FileMaker Server Advanced Custom Web Publishing Guide String manipulation extension function Data type returned fmxslt:url_decode(String value) string Returns a URL-decoded string from a URL string that was previously encoded. fmxslt:url_decode(String value, String encoding) string Returns a URL-decoded string using the character encoding you specify for the encoding parameter, which can be: US-ASCII, ISO-8859-1, ISO-885915, ISO-2022-JP, Shift_JIS or UTF-8.
Chapter 5 | Developing FileMaker XSLT stylesheets 71 For example, suppose a field in a FileMaker database layout has the following checkbox options: [ ] Red [ ] Blue [ ] Green [ ] Small [ ] Medium [ ] Large If a user selected Red only, then the field would contain the string “Red”.
FileMaker Server Advanced Custom Web Publishing Guide Using the date, time, and day extension functions You can use extension functions to get the current date, time, or day, and to compare any two dates, times, or days. The functions in the following table use the “fm” formats regardless of locale. The “fm” formats are MM/ dd/yyyy for date, HH:mm:ss for time, and MM/dd/yyyy HH:mm:ss for timestamp.
Chapter 5 Date, time, day extension function Data type returned | Developing FileMaker XSLT stylesheets 73 Description fmxslt:compare_time(String time1, String time2) number This function compares two time values. It returns a negative number if time1 is before time2. It returns a positive number if time1 is after time2. It returns a 0 if time1 is identical to time2. Both times must be specified in the “fm” time format.
FileMaker Server Advanced Custom Web Publishing Guide Letter Date or Time Component Presentation Examples F Day of week in month Number 2 E Day in week Text Tuesday; Tue a Am/pm marker Text PM H Hour in day (0-23) Number 0 k Hour in day (1-24) Number 24 K Hour in am/pm (0-11) Number 0 h Hour in am/pm (1-12) Number 12 m Minute in hour Number 30 s Second in minute Number 55 S Millisecond Number 978 z Time zone General time zone Pacific Standard Time; PST; GM
Chapter 5 1 1 | Developing FileMaker XSLT stylesheets 75 Month: If the number of pattern letters is three or more, the month is interpreted as text; otherwise, it is interpreted as a number. General time zone: Time zones are interpreted as text if they have names. For time zones representing a GMT offset value, the following syntax is used: 1 1 1 1 1 GMTOffsetTimeZone. GMT Sign Hours:Minutes Sign. + or Hours. Digit or Digit Digit Minutes. Digit Digit Digit.
FileMaker Server Advanced Custom Web Publishing Guide Checking the error status of extension functions You can use the following extension function within an XSLT stylesheet to check the current error status of the most recently called FileMaker XSLT extension function and handle errors that occur during the processing of your pages: fmxslt:check_error_status() When the fmxslt:check_error_status() function is called, the Web Publishing Engine returns the current error code value for the most recently
Chapter 5 | Developing FileMaker XSLT stylesheets 77 2. Define the extension component and extension functions, with the code that actually implements your extension function. function getValueColor(value) { if (value > 0) return ("#009900"); else return ("#CC0000"); } This example returns a color value based on an input value.
FileMaker Server Advanced Custom Web Publishing Guide The example below shows a JavaScript XSLT extension function that retrieves a current stock price from Yahoo and makes it available via an XPath function: PAGE 79Chapter 5 | Developing FileMaker XSLT stylesheets 79 Apple Stock Price:
When the Web Publishing Engine processes this stylesheet, it requests the stock information from Yahoo. The get_quote() function parses the stock quote data and returns the data to the stylesheet.
FileMaker Server Advanced Custom Web Publishing Guide
Chapter 6 Testing and monitoring a site Test your Custom Web Publishing site before deploying it. You can use log files to monitor the site during testing or after deployment. Testing a Custom Web Publishing site Before notifying users that your Custom Web Publishing site is available, it is important to verify that it looks and functions as you expect. 1 1 1 1 Test features like finding, adding, deleting, and sorting records with different accounts and privilege sets.
1 FileMaker Server Advanced Custom Web Publishing Guide When debugging a stylesheet, you can use the following example of an HTML
