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
46 FileMaker Server Advanced Custom Web Publishing Guide
About the Site Assistant’s generated stylesheets
The XSLT stylesheets generated by the Site Assistant include several FileMaker-specific processing
instructions, elements, and parameters. Here are a few examples of what is included:
1 The <?xslt-cwp-query params="query string-fragment"?> processing instruction specifies the XML grammar
to use and statically defines the name of the database you chose in the Site Assistant. See
“Using
statically defined query commands and query parameters” on page 55.
1 The <xsl:param name="request-query"/> element is used to access query information in a request or HTML
form data. For example, this element can be used in the Site Assistant stylesheets to access the current
request query information to determine the current location in a found set of records and to create links
to the previous and next record. See
“Accessing the query information in a request” on page 59.
1 The <xsl:param name="authenticated-xml-base-uri"/> element, which isn’t always included, is used to
access the authenticated base URI in a request when more XML data is needed within the request. See
“Using the authenticated base URI parameter” on page 61.
The Site Assistant also generates the utilities.xsl stylesheet for defining errors and common XSLT templates
that are called by several Site Assistant stylesheets.
For information about other sections of the Site Assistant stylesheets, see chapter 5, “Developing FileMaker
XSLT stylesheets.”
Using the FileMaker CDML Converter
In FileMaker Server 7 Advanced, XSLT replaced CDML (a FileMaker proprietary markup language) as the
Custom Web Publishing language for FileMaker databases. FileMaker no longer supports CDML. To
migrate web sites from CDML format files to FileMaker XSLT stylesheets, use the FileMaker CDML
Converter.
About the FileMaker CDML Converter
The FileMaker CDML Converter is an application that converts working CDML format files to XSLT
stylesheets that are compatible with Custom Web Publishing with XSLT. It is a useful tool for beginning the
process of CDML web site migration and learning how FileMaker XSLT stylesheets are constructed.
Before using the CDML Converter, it is recommended that you copy the CDML format files from the
production environment to a temporary working directory. After using the CDML Converter, you will need
to examine the generated stylesheets and conversion log. In some cases, the converted XSLT stylesheets are
ready for use with FileMaker Server without any further modification. In other cases, the CDML Converter
may be unable to convert all of the CDML tags to XSLT stylesheets and you will need to do some manual
editing of the converted XSLT stylesheets. You can use your own XSLT stylesheet authoring or text editing
tools to modify the stylesheets as necessary. Some changes to the database may also be required if CDML
format files are referenced in database records. This is because the names of the converted XSLT stylesheets
will use the
.xsl filename extension.
You can only use the CDML Converter to convert working CDML format files into new stylesheets. You
cannot use it to edit converted XSLT stylesheets. To use the CDML Converter and migrate the CDML web
site to XSLT effectively, you should be an experienced CDML developer and you should be familiar with
Custom Web Publishing with XSLT.
Note The generated XSLT stylesheets transform FileMaker data into HTML pages based on the fmresultset
XML grammar.