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
102 Custom Web Publishing Guide
1 If a CDML request does not specify a –max query parameter for a –find or –findall query command, the
CDML Converter adds –max=25 to the converted XSLT request. The CDML Converter uses the value 25
to create the same behavior as the original CDML request in which 25 records are returned if the –max
query parameter is not specified. Note that this behavior has changed in XML or XSLT requests; if the –max
query parameter is not specified in an XML or XSLT request, all records are returned. See
“–max
(Maximum records) query parameter” on page 85.
1 If a conversion error occurs, the CDML Converter inserts an error comment into the converted stylesheet
immediately after the element where the error occurred. You are required to manually fix errors in the
stylesheet. An error comment has the following format:
<!-- CDML Converter ERROR: <description of error> -->
1 If a conversion warning occurs, the CDML Converter inserts a warning comment into the converted
stylesheet immediately after the element where the cause of the warning occurred. You are not required to
fix warnings in the stylesheet, but you should investigate them to prevent other errors. A warning comment
has the following format:
<!-- CDML Converter WARNING: <description of warning> -->
1 The CDML Converter removes CDML action and variable tags that are obsolete from URLs, and inserts an
error comment in the stylesheet where they are removed. See “Conversion of obsolete CDML action tags,”
and “Conversion of obsolete CDML variable tags.”
1 The CDML Converter does not convert the obsolete –mail variable tags (such as –mailto and –mailfrom).
See “Conversion of obsolete CDML variable tags” on page 104. To replace the email functionality provided
by the –mail variable tags, use an fmxslt:send_email () extension function. See “Sending email messages from
the Web Publishing Engine” on page 61.
1 If a <form> element with an action parameter ending in fmpro does not contain a –format <input> element,
the CDML Converter inserts the following error comment:
<!-- CDML Converter ERROR: parameter '-format' not found -->.
Conversion of the –error and –errornum CDML variable tags
The CDML Converter converts the CDML –error and –errornum tags into token values. For example, in this
original URL:
fmpro?-db=employees&-format=format.htm&-error=error.htm&-errnum=401&-view
the –error tag is converted to –token.error, and the –errnum tag is converted to –token.errnum. The converted
XSLT-CWP URL is:
format.xsl?-db=employees&-token.error=error.xsl&-token.errnum=401&-view