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
56 Custom Web Publishing Guide
Obtaining client information
You can use the following FileMaker XSLT parameters to obtain information from the Web Publishing
Engine about a web client’s IP address, user name, and password:
<xsl:param name="client-ip"/>
<xsl:param name="client-user-name"/>
<xsl:param name="client-password">
Include these parameter statements in your XSLT stylesheet before the top <xsl:template> element.
You can use these parameters if you need to provide the web user’s credentials when programmatically
loading additional password-protected XML documents while processing the original request. See
“Loading
additional documents” on page 57. next. The web user must provide the user name and password initially via
the HTTP Basic Authentication dialog box. See “When web users use Custom Web Publishing to access a
protected database” on page 17.
For more information and examples of using these three FileMaker XSLT parameters, see the FileMaker
XSLT Extension Function Reference.
Using the Web Publishing Engine base URI parameter
The Web Publishing Engine defines the base Uniform Resource Identifier (URI) parameter to be the host and
port where the Web Publishing Engine is installed. The base URI allows requests for XML data from
FileMaker databases to be resolved in relation to the Web Publishing Engine host.
To access the Web Publishing Engine base URI, include this statement in your XSLT stylesheet before the top
<xsl:template> element:
<xsl:param name="xml-base-uri"/>
You can then use the base URI for the current stylesheet via the $xml-base-uri variable whenever you need to
make an additional request for FileMaker XML data. For example, you can use the base URI in the following
request for additional XML data:
<xsl:variable name="layout_information" select="document(concat($xml-base-uri,'/fmi/xml/FMPXMLLAYOUT.xml?
-db=products&-lay=sales&-view'))" />
Using the authenticated base URI parameter
The following parameter combines the functionality of the client-user-name and client-password parameters
with the xml-base-uri parameter:
<xsl:param name="authenticated-xml-base-uri"/>
Use this parameter to load an additional password-protected XML document that requires the same user name
and password that was specified in the original request currently being processed. For an example, see the next
section,
“Loading additional documents.”
Include this parameter statement in your XSLT stylesheet before the top <xsl:template> element.
If the values for the client-user-name and client-password parameters are not blank, then the value of the
authenticated-xml-base-uri parameter is:
http://username:password@hostname:port
If the values for the client-user-name and client-password parameters are blank, then the value of the
authenticated-xml-base-uri parameter is the same as the value of the xml-base-uri parameter.