Custom Web Publishing with XML and XSLT
Table Of Contents
- Preface
- Chapter 1 Introducing Custom Web Publishing
- Chapter 2 About Custom Web Publishing with XML and XSLT
- Chapter 3 Preparing databases for Custom Web Publishing
- Chapter 4 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 fmsresultset 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 5 Introduction to Custom Web Publishing with XSLT
- Chapter 6 Developing FileMaker XSLT stylesheets
- Using XSLT stylesheets with the Web Publishing Engine
- About the FileMaker XSLT Extension Function Reference
- About the FileMaker XSLT Starter Solution
- 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 the layout information for a database 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 7 Staging, testing, and monitoring a site
- Appendix A Valid names used in query strings
- About the query commands and parameters
- Query command reference
- -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
- -findquery (Compound find) query command
- -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
- Query parameter reference
- -db (Database name) query parameter
- -delete.related (Portal records delete) 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
- -query (Compound find request) query parameter
- -recid (Record ID) query parameter
- -relatedsets.filter (Filter portal records) query parameter
- -relatedsets.max (Limit portal records) 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
- Index
54 FileMaker Server Custom Web Publishing with XML and XSLT
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, if logo.jpg was in the Web folder
inside the FileMaker Pro folder, the container field’s <data> element is:
<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 21.
1 If a container field is empty, then the container field’s <data> element is empty.
Using query strings in FileMaker XSLT stylesheets
When using a query string in a URL or in the <?xslt-cwp-query?> processing instruction in a FileMaker XSLT
stylesheet, you can include any of the query commands and parameters that are defined for requesting XML
data from a FileMaker database. See
“Using FileMaker query strings to request XML data” on page 37.
You can also use the following query command and parameters that are defined for use only with FileMaker
XSLT stylesheets.
Specifying an XML grammar for a FileMaker XSLT stylesheet
The recommended XML grammar to use with Custom Web Publishing with XSLT is the fmresultset
grammar, which has been designed for ease of use with XSLT. See
“Using the fmsresultset grammar” on
page 31. You can also use the older FMPXMLRESULT or FMPXMLLAYOUT grammars. To access value lists and
field display information in layouts, you must use the FMPXMLLAYOUT grammar. See “Using other
FileMaker XML grammars” on page 34. You cannot use the FMPDSORESULT grammar with Custom Web
Publishing with XSLT.
To specify the grammar for a FileMaker XSLT stylesheet, use the –grammar query parameter in a URL or
as a statically defined query parameter in the <?xslt-cwp-query?> processing instruction.
For example, in an URL:
http://192.168.123.101/fmi/xsl/my_template/my_stylesheet.xsl?–grammar=fmresultset&–db=mydatabase
&–lay=mylayout&–findall
Use this XSLT
query command or
parameter name To Comment
–grammar Specify the XML grammar for XSLT-CWP requests or
for XSLT stylesheets. See the next section,
“Specifying
an XML grammar for a FileMaker XSLT stylesheet.”
This query parameter is
required in all XSLT requests.
–encoding Specify the text encoding for a request. See “Setting text
encoding for requests” on page 56.
This query parameter is
optional in all XSLT requests.
–process Process a stylesheet without requesting data. See
“Processing XSLT requests that do not query FileMaker
Server” on page 58.
This query command requires
the –grammar query
parameter.
–token Pass values between pages without using sessions or
cookies. See
“Using tokens to pass information between
stylesheets” on page 58.
This query parameter is
optional in all XSLT requests.