Custom Web Publishing with XML and XSLT
Table Of Contents
- Preface
- Chapter 1 Introducing Custom Web Publishing
- Chapter 2 About Custom Web Publishing with XML and XSLT
- Chapter 3 Preparing databases for Custom Web Publishing
- Chapter 4 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 fmsresultset 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 5 Introduction to Custom Web Publishing with XSLT
- Chapter 6 Developing FileMaker XSLT stylesheets
- Using XSLT stylesheets with the Web Publishing Engine
- About the FileMaker XSLT Extension Function Reference
- About the FileMaker XSLT Starter Solution
- 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 the layout information for a database 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 7 Staging, testing, and monitoring a site
- Appendix A Valid names used in query strings
- About the query commands and parameters
- Query command reference
- -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
- -findquery (Compound find) query command
- -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
- Query parameter reference
- -db (Database name) query parameter
- -delete.related (Portal records delete) 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
- -query (Compound find request) query parameter
- -recid (Record ID) query parameter
- -relatedsets.filter (Filter portal records) query parameter
- -relatedsets.max (Limit portal records) 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
- Index
Chapter 6
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 To use an XSLT stylesheet with the Web Publishing Engine, you must specify the name of the XSLT
stylesheet in a URL. If you don’t specify a stylesheet, or if the Web Publishing Engine is unable to find
or parse the stylesheet, the Web Publishing Engine displays an error page. See
“About the URL syntax
for FileMaker XSLT stylesheets” on page 52.
1 The stylesheet filename and the folder name where the stylesheet is stored must be UTF-8 URL-encoded.
If your stylesheet must be compatible with older web browsers, limit the names to ASCII characters.
1 You must specify the FileMaker XML grammar to use, either as a query parameter in the URL, or as a
statically defined query parameter in the <?xslt-cwp-query?> processing instruction. If you don’t specify
an XML grammar, the Web Publishing Engine displays an error. See
“Specifying an XML grammar for
a FileMaker XSLT stylesheet” on page 54.
1 You can specify the query parameters that identify the FileMaker XML data you want to request either
in the URL, or as a statically defined query parameter in the <?xslt-cwp-query?> processing instruction.
See
“About the URL syntax for FileMaker XSLT stylesheets” on page 52 and “Using statically defined
query commands and query parameters” on page 55.
1 You can optionally specify the text encoding of an XSLT request by using the –encoding query
parameter. If you don’t specify an encoding, the Web Publishing Engine uses its default text encoding
setting for requests. See
“Setting text encoding for requests” on page 56.
1 You can optionally specify an output method via the method attribute of the <xsl:output> element. If you
don’t specify an output method, the Web Publishing Engine uses HTML as the output. You can also
optionally specify the output page encoding by using the encoding attribute of the <xsl:output> element.
If you don’t specify an encoding, the Web Publishing Engine uses the default text encoding setting for
output pages. See
“Specifying an output method and encoding” on page 57.
1 You can optionally specify the text encoding for email messages sent from the Web Publishing Engine
via a function parameter for the fmxslt:send_email() extension function. See
“Sending email messages
from the Web Publishing Engine” on page 65.
To construct a request, the Web Publishing Engine begins by using any query command and query parameters
that are statically defined in the optional <?xslt-cwp-query?> processing instruction. The statically defined query
command and parameters become the base request. The <?xslt-cwp-query?> processing instruction is not
required in a stylesheet, but its base request takes precedence over any matching query command or parameters
that are specified in the URL query string. The Web Publishing Engine then adds to the base request any query
command or additional parameters in the URL query string that are not defined in the <?xslt-cwp-query?>
processing instruction. The Web Publishing Engine uses this request to obtain the FileMaker XML data and
return it to your web browser or program in the output method you specified, or as HTML.