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 23
To access XML data in a portal, set the view for the database layout to View as Form or View as List. If a user
or script changes the view of the database layout to
View as Table, only the first related record (first row of
the portal) is accessible as XML data.
3. Send an HTTP or HTTPS request in the form of a URL that specifies the FileMaker XML grammar, one
query command, and one or more FileMaker query parameters to the Web Publishing Engine through an
HTML form, an HREF link, or a script in your program or web page. You can also type the URL in a web
browser.
For information on specifying the URL, see the next section, “About the URL syntax for XML data and
container objects.” For information on query commands and parameters, see “Using FileMaker query
strings to request XML data” on page 33, and appendix A, “Valid names used in query strings.”
4. The Web Publishing Engine uses the grammar you specified in the URL to generate XML data containing
the results of your request, such as a set of records from the database, and returns it to your program or web
browser.
5. The web browser, if it has an XML parser, displays the data, or the program uses the data in the way you
specified.
If you specified a client-side stylesheet, the web browser parser also applies the stylesheet instructions. See
“Using server-side and client-side processing of stylesheets” on page 35.
About the URL syntax for XML data and container objects
This section describes the URL syntax for using the Web Publishing Engine to access XML data and container
objects from FileMaker databases. The URL syntax for using XSLT stylesheets is different from XML. See
“About the URL syntax for FileMaker XSLT stylesheets” on page 48 and “About the URL syntax for
FileMaker container objects in XSLT solutions” on page 48.
What’s new in the URL syntax for XML data
The Web Publishing Engine uses a new URL syntax for accessing XML data.
1 FileMaker Pro 6 and earlier versions used the following syntax in requests for XML data:
FMPro?<CGI_request>
This syntax has changed. See the next section, “About the URL syntax for XML data.”
1 The –lay query parameter for specifying a database layout is now required with all query commands except
–dbnames, –layoutnames, and –scriptnames. See
appendix A, “Valid names used in query strings.”
1 The –format parameter is obsolete. The XML grammar for XML requests is now specified in the URL
syntax before the query string. See the next section, “About the URL syntax for XML data.”
Note Unlike XML requests, the grammar for XSLT stylesheets is specified with the –grammar query
parameter. See
“Specifying an XML grammar for a FileMaker XSLT stylesheet” on page 50.
About the URL syntax for XML data
The URL syntax for using the Web Publishing Engine to access XML data from FileMaker databases is:
<scheme>://<host>[:<port>]/fmi/xml/<xml_grammar>.xml[?<query string>]
where:
1 <scheme> can be the HTTP or HTTPS protocol.
1 <host> is the IP address or domain name of the host where the web server is installed.