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
Accessing XML data with the Web Publishing Engine 25
1 If a container field stores a file reference instead of an actual object, then the container field’s <data>
element contains a relative path that refers to the object. For example:
<data>/images/logo.jpg</data>
Note The referenced container object must be stored in the FileMaker Pro Web folder when the record is
created or edited, and then copied or moved to a folder with the same relative location in the root folder of
the web server software. See
“About publishing the contents of container fields on the web” on page 19.
1 If a container field is empty, then the container field’s <data> element is empty.
Note The syntax for container objects using XML is different from the syntax for container objects using
XSLT. See
“About the URL syntax for FileMaker container objects in XSLT solutions” on page 48.
About URL text encoding
The URLs for accessing XML data and container objects must be encoded in UTF-8 (Unicode Transformation
8 Bit) format. See
“About UTF-8 encoded data” on page 33.
For example, to set the value of the info field to fiancée, you could use the following URL:
http://server.company.com/fmi/xml/fmresultset.xml?-db=members&-lay=relationships&-recid=2&info= fianc%C3%A9e
&-edit
In this example URL, %C3%A9 is the URL encoded UTF-8 representation of the é character.
For more information on URL text encoding, see the URL specification, which is available at www.w3.org.
Accessing XML data via the Web Publishing Engine
To access XML data via the Web Publishing Engine, you use a URL that specifies the name of the FileMaker
grammar to use, one FileMaker query command, and one or more FileMaker query parameters. The Web
Publishing Engine generates XML data from your database that is formatted by one of the following types of
XML grammars:
1 fmresultset: This is the recommended grammar for the Web Publishing Engine. It is flexible and optimized
for XSLT stylesheet authoring with easier field access by name and easier manipulation of relatedset
(portal) data. This grammar is also more directly linked to FileMaker terminology and features such as
global storage options and identification of summary and calculation fields. You can use this grammar for
accessing XML data and for XSLT stylesheets. To facilitate web publishing, this grammar is designed to
be more verbose than the FMPXMLRESULT grammar. See
“Using the fmresultset grammar” on page 27.
1 FMPXMLRESULT and FMPXMLLAYOUT: You can also use the FMPXMLRESULT and
FMPXMLLAYOUT grammars with the Web Publishing Engine for accessing XML data and for XSLT
stylesheets. To use one stylesheet for both XML export and Custom Web Publishing, you must use the
FMPXMLRESULT grammar. To access value lists and field display information in layouts, you must use
the FMPXMLLAYOUT grammar. See
“Using other FileMaker XML grammars” on page 29.
1 FMPDSORESULT: The FMPDSORESULT grammar, which is supported in FileMaker Pro for exporting
XML, is deprecated for accessing XML data via the Web Publishing Engine. The FMPDSORESULT
grammar is not supported for XSLT stylesheets. For information on the FMPDSORESULT grammar, see
FileMaker
Pro Help.