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
88 FileMaker Server Custom Web Publishing with XML and XSLT
Guidelines for using query commands and parameters
When using query commands and parameters in a query string, keep the following guidelines in mind:
1 A query string must contain only one query command; no more and no less. For example, a query string
can contain –new to add a new record, but it can’t contain –new and –edit in the same query string.
1 Most query commands require various matching query parameters in the query string. For example, all
query commands except –dbnames and –process require the –db parameter that specifies the database to
query. See the table of required parameters in
“Using FileMaker query strings to request XML data” on
page 37.
1 For query parameters and field names, specify the particular value you want to use, such as
–db=employees. For query commands, don’t specify an “=” sign or a value after the command name, such
as –findall.
1 Query command and parameter names must be specified in lowercase, such as –delete or –lay.
1 Database names, layout names, and field names used in query strings are case insensitive, such as
–lay=mylayout to specify MyLayout.
Note Field and database names that are used in XSLT statements outside of query strings are case
sensitive and must exactly match the actual names used in the database. For example, in this statement:
<xsl:value-of select="fmrs:field[@name='LastName']"/>
the field reference “LastName” must exactly match the name of the LastName field in the database.
1 Field names can contain periods, with the following exceptions:
1 The period cannot be followed by a number. For example, myfield.9 is an invalid field name.
1 The period cannot be followed by the text string op (the two letters “op”). For example, myfield.op is
an invalid field name.
1 The period cannot be followed by the text string global (the word “global”). For example, myfield.global
is an invalid field name.
Field names containing any of these exceptions cannot be accessed via XML or XSLT using an HTTP
query. These contructs are reserved for record IDs, as described in the section,
“About the syntax for a
fully qualified field name,” below.
1 For the –find command, the value of a field is case insensitive. For example, you can use Field1=Blue or
Field1=blue. For the –new and –edit commands, the case you use in the value of a field is preserved and
stored in the database exactly as you specify in the query string. For example, LastName=Doe.
About the FileMaker Query Strings Reference
This release includes a FileMaker database called Query Strings Reference.fp7 that contains brief descriptions
and examples of each of the FileMaker query commands and query parameters. This can be found in the
following directory on any machine in your FileMaker Server deployment (master or worker):
Mac:
/Library/FileMaker Server/Examples/XSLT
Windows:
<drive>:\Program Files\FileMaker\FileMaker Server\Examples\XSLT
Where: <drive> is the primary drive from which the system is started.