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 61
Sending email messages from the Web Publishing Engine
You can use the Web Publishing Engine to generate email messages, which is useful for custom web solutions.
To have the Web Publishing Engine send an email message, use one of the following three
fmxslt:send_email ()
extension functions in an XSLT stylesheet. You can use these functions to send one or more separate
messages. Because the
fmxslt:send_email () functions are contained in the Web Publishing Engine’s server-side
XSLT stylesheet, a client cannot use the Web Publishing Engine to send unauthorized email messages.
Notes
1 In each of the three forms of the fmxslt:send_email () function, the smtpFields parameter is a URL-encoded
string of any length that contains the address and subject information using the following format, which is
based on RFC 2368, the mailto URL scheme:
username@host?name1=value1&name2=value2...
where username@host specifies a recipient. The name/value pairs can be specified in any order and are
defined as follows:
1 from=username@host (must appear only once). The from field must be specified.
1 to=username@host. Use this name/value pair for additional recipients.
1 reply-to=username@host (can appear only once)
1 cc=username@host
1 bcc=username@host
1 subject=string (can appear only once)
If the from, reply-to, or subject fields are specified more than once, then the email message is not sent, a
value of false() is returned by the function, and the appropriate error status code is set.
1 The Web Publishing Engine will check the syntax of all email addresses provided. They must be of the
form:
user@host.tld or "quoted identifier"<user@host.tld>
where tld is any top-level-domain such as com or net. If any of the fields contains an invalid email address,
then the email message is not sent and the appropriate error status code is set.
Email extension function
Data type
returned Description
fmxslt:send_email(String smtpFields,
String body)
boolean Sends a plain text email message of any length from the Web
Publishing Engine using the Web Publishing Engine’s
default text encoding for email messages
fmxslt:send_email(String smtpFields,
String
body, String encoding)
boolean Sends a plain text email message of any length using one of
the following text encodings: US-ASCII, ISO-8859-1, ISO-
8859-15, ISO-2022-JP, Shift_JIS, UTF-8. For information
on these encodings, see “Setting text encoding for requests”
on page 52.
fmxslt:send_email(String smtpFields,
String xsltFile, Node xml, boolean
includeImages)
boolean Sends an HTML-based email message using the encoding
that is specified by encoding attribute of the <xsl:output>
element in the stylesheet. If the encoding attribute is not
included in the <xsl:output> element, the Web Publishing
Engine’s default text encoding for email messages is used.