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
100 FileMaker Server Custom Web Publishing with XML and XSLT
Examples:
http://localhost/fmi/xml/fmresultset.xml?–db=FMPHP_Sample&–lay=English&–relatedsets.filter=none&–findany
http://localhost/fmi/xml/fmresultset.xml?
–db=FMPHP_Sample&–lay=English&relatedsets.filter=layout
&
–relatedsets.max=all&–findany
http://localhost/fmi/xml/fmresultset.xml?
–db=FMPHP_Sample&–lay=English&–relatedsets.filter=layout
&
–relatedsets.max=10&–findany
–relatedsets.max (Limit portal records) query parameter
Specifies the maximum number of rows to return in the results for this query.
Value is: an integer, or all.
1 If the query specifies an integer, then the Web Publishing Engine returns that number of rows after the
initial row are returned.
1 If the query specifies all, then the Web Publishing Engine returns all of the related records.
1 If the query does not specify the –relatedsets.max parameter, then the number of rows is determined by
the value specified on the –relatedsets.filter parameter. See
“–relatedsets.filter (Filter portal records) query
parameter” on page 99.
Optional with: –find, –edit, –new, –dup, and –findquery.
Examples:
http://localhost/fmi/xml/fmresultset.xml?–db=FMPHP_Sample&–lay=English&relatedsets.filter=layout
&
–relatedsets.max=all&–findany
http://localhost/fmi/xml/fmresultset.xml?
–db=FMPHP_Sample&–lay=English&–relatedsets.filter=layout
&
–relatedsets.max=10&–findany
–script (Script) query parameter
Specifies the FileMaker script to run after the query command and sorting are executed. See “Understanding
how an XML request is processed” on page 39.
Value is: Script name
Optional with: all query commands except –dbnames, –layoutnames, –process, and –scriptnames
Example:
http://192.168.123.101/fmi/xml/fmresultset.xml?–db=employees&–lay=departments&–script=myscript&–findall
–script.param (Pass parameter to Script) query parameter
Passes a parameter to the FileMaker script specified by –script
Value is: A single text parameter.
1 To pass in multiple parameters, you can create a string delimiting the parameters and have your script
parse out the individual parameters. For example, pass “param1|param2|param3” as a list with the “|”
character URL-encoded as this: param1%7Cparam2%7Cparam3
1 To treat the text parameter as a value that is not text, your script can convert the text value. For example,
to convert the text value to a number, your script could include the following:
GetAsNumber(Get(ScriptParam))
1 If your query contains –script.param without –script, then –script.param is ignored.
1 If your query contains more than one –script.param, then the Web Publishing Engine uses the last value
that it parses.