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
50 Custom Web Publishing Guide
Specifying an XML grammar for a FileMaker XSLT stylesheet
The recommended XML grammar to use with Custom Web Publishing with XSLT is the fmresultset grammar,
which has been designed for ease of use with XSLT. See “Using the fmresultset grammar” on page 27. You
can also use the older FMPXMLRESULT or FMPXMLLAYOUT grammars. To access value lists and field
display information in layouts, you must use the FMPXMLLAYOUT grammar. See
“Using other FileMaker
XML grammars” on page 29. You cannot use the FMPDSORESULT grammar with Custom Web Publishing
with XSLT.
To specify the grammar for a FileMaker XSLT stylesheet, use the –grammar query parameter in a URL or as
a statically defined query parameter in the
<?xslt-cwp-query?> processing instruction.
For example:
http://192.168.123.101/fmi/xsl/my_template/my_stylesheet.xsl?-grammar=fmresultset&-db=mydatabase
&-lay=mylayout&-findall
Or
<?xslt-cwp-query params="-grammar=fmresultset&-db=mydatabase&-lay=mylayout&-findall"?>
Important If you don’t specify an XML grammar for a FileMaker XSLT stylesheet, the error “QUERY -
ER0001” is displayed. See
appendix B, “Error codes for Custom Web Publishing.”
About namespaces and prefixes for FileMaker XSLT stylesheets
Unique XSLT namespaces help distinguish XSLT tags by the application they were designed for. In the
<xsl:stylesheet> 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.
You must also declare the following required namespace in each FileMaker XSLT stylesheet:
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
Here is an example of namespace declarations:
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fmrs="http://www.filemaker.com/xml/fmresultset"
xmlns:fml="http://www.filemaker.com/fmpxmllayout"
xmlns:fmq="http://www.filemaker.com/xml/query"
xmlns:fmxslt="xalan://com.fmi.xslt.ExtensionFunctions"
exclude-result-prefixes="xsl fmrs fmq fml fmxslt">
If you use this Declare this namespace
Use this
prefix
fmresultset XML grammar xmlns:fmrs="http://www.filemaker.com/xml/fmresultset" fmrs
FMPXMLRESULT grammar xmlns:fmp="http://www.filemaker.com/fmpxmlresult" fmp
FMPXMLLAYOUT grammar xmlns:fml="http://www.filemaker.com/fmpxmllayout" fml
For the query XML grammar xmlns:fmq="http://www.filemaker.com/xml/query" fmq
For the FileMaker XSLT extension
functions
xmlns:fmxslt="xalan://com.fmi.xslt.ExtensionFunctions" fmxslt