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 115
Conversion of CDML action tags, variable tags, and URLs
To convert CDML action tags, variable tags, and URLs, the CDML Converter does the following:
1 The CDML Converter does not change unidentified tag names that are preceded by a dash (–).
Unidentified tag names in a URL are moved to the end of the query string. The CDML Converter
assumes that tag names that are not preceded by a dash are
<fieldname> variable tags and leaves them in
the appropriate position in the URL.
1 The CDML Converter searches for the text string “fmpro?” to identify URLs. In non-SGML documents
and SGML comments, the CDML Converter identifies URLs in any location. Inside SGML elements,
the CDML Converter only identifies URLs that are located inside element attribute values.
1 The CDML Converter identifies the –format variable tag outside of URLs only if it is inside input
elements in HTML documents. The CDML Converter ignores all other form elements, such as text select
and text area elements.
1 The CDML Converter replaces all <input> elements that contain the CDML –format tag with XSLT-CWP
statements. For example, the following
<input> element and –format tag:
<input type="hidden" name="–format" value="results.htm">
are replaced with:
<xsl:attribute name="action">results.xsl</xsl:attribute>
1 The CDML Converter converts URLs in requests and <form> <input> elements to the new syntax for
XSLT. See
“About the URL syntax for FileMaker XSLT stylesheets” on page 52.
1 The CDML Converter converts URLs that request FileMaker XML data, where –format uses a value of
–fmp_xml or –dso_xml to the new URL syntax for XML data. See “About the URL syntax for XML data
and container objects” on page 25.
1 The CDML Converter converts URLs that request FileMaker image data (using –img) to the URL syntax
for requesting container objects in XSLT solutions. See
“About the URL syntax for FileMaker container
objects in XSLT solutions” on page 53. If a query request contains the img-key format, the CDML
Converter converts it in the same way it converts the [FMP-Image] variable tag. For example, this CDML
request:
<img src="fmpro?–db=employees&key=[FMP-Field: fieldname, url]&–img=">
is converted the same as this:
<img src="[FMP-Image: fieldname]">
For information on the conversion of [FMP-Image], see “CDML tag name: Image” on page 145.
1 The CDML Converter converts tag names to XSLT-CWP query command and parameter names in
lowercase, with the exception of <fieldname> CDML variable tags in find requests. Values for query
commands and parameters are not changed.
1 The CDML Converter reorders the converted XSLT-CWP query commands and parameters in a URL
into the following order: –db, –grammar, –lay, any other the query parameters, and the query command
last, such as
–findall. The CDML Converter does not change the order of <form> <input> elements that
contain query commands and parameters.