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
64 FileMaker Server Custom Web Publishing with XML and XSLT
If the Web Publishing Engine detects that the client allows cookies, then the fmxslt:session_encode_url()
function stores the session ID in a cookie instead of the URL.
Note Session information does not persist after the Web Publishing Engine is restarted.
Using the session extension functions
Use the following session extension functions to manipulate session variables. You can store a string,
number, boolean value, or node-set in a session object. By using node-set, you can create a data structure in
XML and then store it between requests in the session object.
Session extension function
Data type
returned
Description
fmxslt:session_exists(String session-name) boolean Checks if a session with the specified name exists.
fmxslt:create_session(String session-name) boolean Creates a session with the specified session name
and the default time-out, which is set via the Admin
Console. See FileMaker
Server Help.
Note This function requires the <?xslt-cwp-buffer?>
processing instruction. See
“Using content
buffering” on page 63.
fmxslt:invalidate_session(String session-name) boolean Forces the session to time out immediately.
fmxslt:set_session_timeout(String
session-name, Number timeout)
boolean Sets the session timeout in seconds.
The default timeout for sessions is set via the Admin
Console.
fmxslt:session_encode_url(String url) string Encodes a URL with the session ID if the client does
not support cookies; otherwise returns input URL.
fmxslt:set_session_object(String
session-name, String name, Object value)
XSLT object
(number, string,
boolean, or
node-set)
Stores an XSLT object (a number, string, boolean, or
node-set) under a session, which can be later retrieved
using the fmxslt:get_session_object () function.
This function also returns the previously stored object
under the specified session object name. If nothing
was stored under the name, it returns a null object.
Note The set_session_object() extension function
stores string values only; it interprets any object
passed to it as a string. If the object cannot be
converted to a string, then no value is stored in the
session and the extension function error code is set
to 10100 (Unknown Session Error). If you attempt
to set a session object using null or an empty string,
you also receive an error code of 10100 (Unknown
Session Error). To clear out a session variable,
remove the variable from the session using the
remove_session_object() function.
fmxslt:get_session_object(String
session-name, String name)
XSLT object Retrieves an XSLT object from the session.
fmxslt:remove_session_object(String
session-name, String name)
XSLT object Returns and then removes an XSLT object from the
session.