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
138 Custom Web Publishing Guide
CDML tag name: Link to Record ID
Tag is replaced with a URL to a specific record in a database. The link that is generated includes all the search
and sort criteria that was used to generate the page this tag was on. The Layout parameter is optional.
CDML syntax: [FMP-LinkRecID: Format=FileName, Layout=LayoutName]
XSLT-CWP conversion:
1 <xsl:call-template name="get-link-rec-id"><xsl:with-param name="rec-id" select="@record-id"/
><xsl:with-param name="stylesheet" select="'/FileName.xsl'"/></xsl:call-template>
1 if followed a '-format' parameter: the 'stylesheet' parameter is passed to the 'get-link-rec-id' template
1 if followed a '-lay' parameter: the 'layout' parameter is passed to the 'get-link-rec-id' template
1 if not inside an SGML attribute: <!-- CDML Converter ERROR: [FMP-LinkRecID] not in a valid
location -->
CDML tag name: Log
Tag is replaced with the text specified as the parameter and written as user log messages in the application log
file. See
“Using the Web Publishing Engine application log” on page 73.
CDML syntax: [FMP-Log: someText]
XSLT-CWP conversion:
1 <xsl:message>someText</xsl:message>
1 if inside an SGML tag/attribute: <!-- CDML Converter ERROR: [FMP-Log] not in a valid location -->
Conversion example
Original CDML: <a href="[FMP-LinkRecID: format=FormatFile.htm, layout=detail]">More detail</a>
Converted
XSLT-CWP:
<a>
<xsl:attribute name="href">
<xsl:call-template name="get-link-rec-id">
<xsl:with-param name="rec-id" select="$record/@record-id"/>
<xsl:with-param name="stylesheet" select="'FormatFile.xsl'"/>
<xsl:with-param name="layout" select="'detail'"/>
</xsl:call-template>
</xsl:attribute>More Detail</a>
Converted
Result:
<a href="/fmi/xsl/FormatFile.xsl?-db=products&-grammar=fmresultset&-lay=detail&-recid=3&-
find=">More detail</a>
Conversion example
Original CDML: Log code is here: [FMP-Log: the search page was accessed]
Converted XSLT-CWP: Log code is here: <xsl:message>the search page was accessed</xsl:message>
Converted Result: Log code is here:
(The text the search page was accessed is written to the application log if user logging is
enabled.)