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
- 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.prefind (Script before Find) query parameter
- -script.presort (Script before Sort) query parameter
- -skip (Skip records) query parameter
- -sortfield (Sort field) query parameter
- -sortorder (Sort order) query parameter
- -styletype (Style type) query parameter
- -stylehref (Style href) 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
Developing FileMaker XSLT stylesheets 57
Loading additional documents
To load an additional XML document during the processing of an XSLT stylesheet, use the standard XSLT
document() function with a URI to the XML document. The document() function returns the requested XML as
a node-set that can be stored in an
<xsl:variable> element.
To load an XML document that contains data from a FileMaker database, use the document() function with
FileMaker query command and parameters. For example:
<xsl:variable name="other-data" select="document(concat($xml-base-uri,'/fmi/xml/FMPXMLLAYOUT.xml?-db=products
&-lay=sales&-view'))"/>
To load an additional password-protected XML document that requires the same user name and password that
was specified in the original request currently being processed, use the authenticated-xml-base-uri parameter.
This parameter specifies the same user name and password as part of the URI that is passed to the
document()
function.
For example:
<xsl:variable name="other-data" select="document(concat($authenticated-xml-base-uri,'/fmi/xml/FMPXMLLAYOUT.xml?
-db=products&-lay=sales&-view'))"/>
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 query parameters. For example:
<xsl:variable name="other-data" select="document('http://server.company.com/data.xml')" />
If you use the document() function with a relative URL, the Web Publishing Engine will attempt to load the
XML document from the local file system in the location relative to where the stylesheet is stored. For
example, suppose a stylesheet that is located inside the mystylesheets folder inside the xslt-template-files
folder contains the following
document() function with a relative URL:
<xsl:variable name="mydoc" select="document('mystylesheets/mydoc.xml')" />
The Web Publishing Engine will attempt to load mydoc.xml from the mystylesheets folder inside the xslt-
template-files folder in the local file system.
Note When you use the Web Publishing Engine’s base URI to load a document, the Web Publishing Engine
supports HTTP only. When you load a document from an external server, the Web Publishing Engine supports
both HTTP and HTTPS.
Using a database’s layout information in a stylesheet
You can incorporate a FileMaker database’s layout information in a stylesheet by using the
FMPXMLLAYOUT grammar to request the information and then loading it into a variable via the XSLT
document() function:
<xsl:variable name="layout" select="document(concat($xml-base-uri,'/fmi/xml/FMPXMLLAYOUT.xml?-view'))" />