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
Developing FileMaker XSLT stylesheets 59
By default, the Web Publishing Engine will use a cookie to store the session ID. To accommodate clients that
do not allow cookies, you can use the
fmxslt:session_encode_url() function to add the Session ID to the URL.
To guarantee compatibility in all situations, it is recommended that you encode all URLs written out to the
page with the
fmxslt:session_encode_url() function. This function adds to your URL a semicolon-separated
parameter called
jsessionid, which is the identifier for the particular client’s parent session.
For example, instead of placing the following link on a page:
<a href="my_stylesheet.xsl?-db=products&-lay=sales&-grammar=fmresultset&-findall">hyperlinked text</a>
You should encode all links on a page as follows:
<a href="{fmxslt:session_encode_url('my_stylesheet.xsl?-db=products&-lay=sales&-grammar=fmresultset&-findall')}">
hyperlinked text</a>
If the client does not allow cookies, the page includes:
<a href="my_stylesheet.xsl;jsessionid=<session id>?-db=products&-lay=sales&-grammar=fmresultset&-findall">
hyperlinked text</a>
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
Administration Console. See the FileMaker
Server Advanced Web Publishing Installation
Guide.
Note This function requires the <?xslt-cwp-
buffer?> processing instruction. See “Using
content buffering” on page 58.
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 minutes.
The default timeout for sessions is set via the
Administration 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.