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
Appendix C
Converting CDML solutions to FileMaker XSLT
This appendix explains the results of using the FileMaker CDML Converter to convert CDML format files to
FileMaker XSLT stylesheets. For information on using the FileMaker CDML Converter, see
“Using the
FileMaker CDML Converter” on page 42.
Note In this appendix and in the generated comments in converted XSLT stylesheets, the term “XSLT-CWP”
refers to FileMaker Custom Web Publishing with XSLT.
About the process of converting CDML solutions to FileMaker XSLT solutions
The CDML Converter converts, renames, or copies the CDML solution files in the source folder as follows:
1 CDML format files that contain CDML tags or query parameters are converted to XSLT stylesheets and
then saved in the destination folder.
1 The filename extensions of HTML files, regardless of whether they contain CDML tags or not, are renamed
to .xsl, and then the files are copied to the destination folder. For example, myfile.html is renamed to
myfile.xsl.
1 All upper case filenames are changed to lower case because all converted file references use lower case and
XSLT is case sensitive.
1 Non-HTML files that do not contain CDML tags or query parameters are copied without changes to the
destination folder.
1 Any folders within the source folder hierarchy are automatically created in the destination folder.
To convert each CDML format file to an XSLT stylesheet, the CDML Converter:
1 removes the <!DOCTYPE> tag if it is included.
1 maps all CDML boolean expressions to XPath expressions.
1 in all occurrences of the –format CDML tag, converts all filename extensions to .xsl in filename references.
1 maps all CDML replacement tags and intratag parameters to XSLT-CWP statements.
1 inserts the <?xslt-cwp-query params="–grammar=fmresultset"?> processing instruction in all converted
stylesheets to specify the fmresultset grammar. See
“Using statically defined query commands and query
parameters” on page 51.
1 inserts a value for the encoding attribute in the <?xml ... ?> processing instruction and the <xsl:output> element
that matches the text encoding option you selected in the CDML Converter during the conversion.
1 inserts a value of “xml” for the method attribute of the <xsl:output> element if the input file begins with a
<?xml ... ?> processing instruction. If the input file is an HTML file, “html” is inserted as the value of the
method attribute; otherwise, “text” is inserted.