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
28 Custom Web Publishing Guide
The <relatedset-definition> element represents a portal. Each related field in a portal is represented by the
<field-definition> element contained within the <relatedset-definition> element. If there are multiple related fields
in a portal, the field definitions for the related fields are grouped within a single
<relatedset-definition> element.
The <resultset> element contains all of the <record> elements returned as the result of a query and an attribute
for the total number of records found. Each
<record> element contains the field data for one record in the result
set—including the mod-id and the record-id attributes for the record, and the
<data> element containing the
data for one field in the record.
Each record in a portal is represented by a <record> element within the <relatedset> element. The count
attribute of the
<relatedset> element specifies the number of records in the portal, and the table attribute
specifies the table associated with the portal.
Example of XML data in the fmresultset grammar
The following is an example of XML data generated with the fmresultset grammar.
<?xml version="1.0" standalone="no"?>
<!DOCTYPE fmresultset PUBLIC "-//FMI//DTD fmresultset//EN" "/fmi/xml/fmresultset.dtd">
<fmresultset xmlns="http://www.filemaker.com/xml/fmresultset" version="1.0">
<error code="0"></error>
<product build="01/10/2004" name="FileMaker Web Publishing Engine" version="7.0v1" />
<datasource database="art" date-format="M/d/yyyy" layout="web" table="art" time-format="h:mm:ss a"
total-count="3" />
<metadata>
<field-definition auto-enter="no" global="no" max-repeat="1" name="Title" not-empty="no" result="text"
type="normal" />
<field-definition auto-enter="no" global="no" max-repeat="1" name="Artist" not-empty="no" result="text"
type="normal" />
<field-definition auto-enter="no" global="no" max-repeat="1" name="Image" not-empty="no" result="container"
type="normal" />
<field-definition auto-enter="no" global="no" max-repeat="2" name="Description" not-empty="no" result="text"
type="normal" />
<relatedset-definition table="artlocations">
<field-definition auto-enter="no" global="no" max-repeat="1" name="artlocations::Location"
not-empty="no" result="text" type="normal" />
<field-definition auto-enter="no" global="no" max-repeat="1" name="artlocations::Date" not-empty="no"
result="text" type="normal" />
</relatedset-definition>
<field-definition auto-enter="no" global="no" max-repeat="1" name="artistbio::birthdate" not-empty="no"
result="date" type="normal" />
</metadata>
<resultset count="1" fetch-size="1">
<record mod-id="5" record-id="1">
<field name="Title">
<data>Village Market</data>
</field>
<field name="Artist">
<data>Camille Pissarro</data>
</field>