Custom Web Publishing Guide
Table Of Contents
- Chapter 1 Introducing Custom Web Publishing
- Chapter 2 Preparing databases for Custom Web Publishing
- Chapter 3 Accessing XML data with the Web Publishing Engine
- Using Custom Web Publishing with XML
- General process for accessing XML data from the Web Publishing Engine
- About the URL syntax for XML data and container objects
- Accessing XML data via the Web Publishing Engine
- Using the fmresultset grammar
- Using other FileMaker XML grammars
- About UTF-8 encoded data
- Using FileMaker query strings to request XML data
- Switching layouts for an XML response
- Understanding how an XML request is processed
- Using server-side and client-side processing of stylesheets
- Troubleshooting XML document access
- Chapter 4 Introduction to Custom Web Publishing with XSLT
- 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
- Setting text encoding for requests
- Specifying an output method and encoding
- About the encoding of XSLT stylesheets
- Processing XSLT requests that do not query FileMaker Server
- Using tokens to pass information between stylesheets
- Using the FileMaker XSLT extension functions and parameters
- About the FileMaker-specific XSLT parameters set by the Web Publishing Engine
- Accessing the query information in a request
- Obtaining client information
- Using the Web Publishing Engine base URI parameter
- Using the authenticated base URI parameter
- Loading additional documents
- Using a database’s layout information in a stylesheet
- Using content buffering
- Using Web Publishing Engine sessions to store information between requests
- Using the session extension functions
- Sending email messages from the Web Publishing Engine
- Using the header functions
- Using the cookie extension functions
- Using the string manipulation extension functions
- Comparing strings using Perl 5 regular expressions
- Checking for values in a field formatted as a checkbox
- Using the date, time, and day extension functions
- Checking the error status of extension functions
- Using logging
- Using server-side processing of scripting languages
- Chapter 6 Testing and monitoring a site
- Appendix A Valid names used in query strings
- About the query commands and parameters
- Using the query commands
- -dbnames (Database names) query command
- -delete (Delete record) query command
- -dup (Duplicate record) query command
- -edit (Edit record) query command
- -find, -findall, or -findany (Find records) query commands
- -layoutnames (Layout names) query command
- -new (New record) query command
- -process (Process XSLT stylesheets)
- -scriptnames (Script names) query command
- -view (View layout information) query command
- 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.response (Switch layout for response) query parameter
- -lop (Logical operator) query parameter
- -max (Maximum records) query parameter
- -modid (Modification ID) query parameter
- -recid (Record ID) query parameter
- -script (Script) query parameter
- -script.param (Pass parameter to Script) query parameter
- -script.prefind (Script before Find) query parameter
- -script.prefind.param (Pass parameter to Script before Find) query parameter
- -script.presort (Script before Sort) query parameter
- -script.presort.param (Pass parameter to Script before Sort) query parameter
- -skip (Skip records) query parameter
- -sortfield (Sort field) query parameter
- -sortorder (Sort order) query parameter
- -stylehref (Style href) query parameter
- -styletype (Style type) query parameter
- -token.[string] (Pass values between XSLT stylesheets) query parameter
- Appendix B Error codes for Custom Web Publishing
- 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 XPath boolean parameters
- Conversion of CDML boolean operators to XPath
- Conversion of CDML intratag parameters to XSLT-CWP
- Manually fixing CDML conversion errors
- Conversion of CDML replacement tags to XSLT-CWP
- Index
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 <xsl:stylesheet> element at the start of your XSLT stylesheet. See
“About namespaces and prefixes for FileMaker XSLT stylesheets” on page 55.
The FileMaker XSLT extension functions have been designed so that you can use them within an XSLT
stylesheet by specifying them as a function call within an XPath statement. XPath statements are used as
the values of the select attribute and the test attribute in numerous XSLT elements.
For example, suppose you want to check the User-Agent header to determine the browser being used. To do
this, you might want to use a variable that contains the value of the User-Agent header:
<xsl:variable name="user-agent" select="fmxslt:get_header('User-Agent')"/>
For the extension functions that return a value, the value will be returned in the XSLT type specified. Many
functions return strings, but a few functions return a
node-set that can be traversed.
Note This section describes the FileMaker XSLT extension functions and parameters, and includes some
examples. For additional examples of each function, see the FileMaker XSLT Extension Function
Reference. See
“About the FileMaker XSLT Extension Function Reference” on page 52.
About the FileMaker-specific XSLT parameters set by the Web Publishing Engine
When processing a request, the Web Publishing Engine dynamically sets the values of the following
FileMaker-specific XSLT parameters. You can use the values of these parameters in your stylesheet by using
the
<xsl:param> element.
Accessing the query information in a request
You can use a FileMaker XSLT parameter to access query information in a request in a URL or HTML form
data. For example, you can access the current request query information to determine the current location
in a found set of records, and create links to the previous and next record.
The following FileMaker XSLT parameter provides access to all of the query commands and query
parameters that are used to request FileMaker XML data via the Web Publishing Engine:
<xsl:param name="request-query"/>
With the exception of field names, the Web Publishing Engine returns all query command and query
parameter names in lowercase. The capitalization of field names is preserved.
FileMaker-specific XSLT parameter For more information, see
<xsl:param name="request-query"/> “Accessing the query information in a request” in the next section.
<xsl:param name="client-ip"/>
<xsl:param name="client-user-name"/>
<xsl:param name="client-password"/>
“Obtaining client information” on page 60.
<xsl:param name="xml-base-uri"/> “Using the Web Publishing Engine base URI parameter” on
page 61.
<xsl:param name="authenticated-xml-base-uri"> “Using the authenticated base URI parameter” on page 61.