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
- Using server-side processing of scripting languages
- 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.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
- 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
Appendix C
|
Converting CDML solutions to FileMaker XSLT 149
CDML tag name: Link First
The HTML between [FMP-LinkFirst] and [/FMP-LinkFirst] is replaced with a link to the first range of records
based on the -Max value used to create the current page.
CDML syntax: [FMP-LinkFirst]...[/FMP-LinkFirst]
XSLT-CWP conversion:
1 <a href="{$link-first}">...</a>
1 insert at top-level of document: <xsl:variable name="link-first"><xsl:call-template name="get-link-first"/></
xsl:variable>
1 if inside an SGML tag/attribute: <!-- CDML Converter ERROR: [FMP-LinkFirst] not in a valid location -->
CDML tag name: Link Last
The HTML between [FMP-LinkLast] and [/FMP-LinkLast] is replaced with a link to the last range of records
based on the -Max value used to create the current page.
CDML syntax: [FMP-LinkLast]...[/FMP-LinkLast]
XSLT-CWP conversion:
1 <a href="{$link-last}">...</a>
1 insert at top-level of document: <xsl:variable name="link-last"><xsl:call-template name="get-link-last"/>
</xsl:variable>
1 if inside an SGML tag/attribute: <!-- CDML Converter ERROR: [FMP-LinkLast] not in a valid location -->
CDML tag name: Link Next
The HTML between [FMP-LinkNext] and [/FMP-LinkNext] is replaced with a link to the next range of records
based on the -Max and -Skip values used to create the current page.
CDML syntax: [FMP-LinkNext]...[/FMP-LinkNext]
XSLT-CWP conversion:
1 <a href="{$link-next}">...</a>
1 insert at top-level of document: <xsl:variable name="link-next"><xsl:call-template name="get-link-next"/>
</xsl:variable>
1 if inside an SGML tag/attribute: <!-- CDML Converter ERROR: [FMP-LinkNext] not in a valid location -->
Conversion example
Original CDML: [FMP-LinkFirst]First set of records[/FMP-LinkFirst]
Converted XSLT-CWP: <a href="{$link-first}">First set of records</a>
Converted Result: <a href="/fmi/xsl/stylesheet.xsl?-max=10&-find=">First set of records</a>
Conversion example
Original CDML: [FMP-LinkLast]Last set of records[/FMP-LinkLast]
Converted XSLT-CWP: <a href="{$link-last}">Last set of records</a>
Converted Result: <a href="/fmi/xsl/stylesheet.xsl?-skip=10&-max=10&-find=">Last set of records</a>