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
36 Custom Web Publishing Guide
query parameters, which prevent the use of unauthorized query commands and query parameters, such as
database names. See
chapter 4, “Introduction to Custom Web Publishing with XSLT” and chapter 5,
“Developing FileMaker XSLT stylesheets.”
If your solution requires client-side stylesheet processing, you can have the Web Publishing Engine generate
an XML stylesheet processing instruction with each grammar by including the –styletype and –stylehref
parameters in the FileMaker query string request. You can use cascading stylesheets (CSS) or XSLT
stylesheets for displaying your XML document.
1 The –styletype parameter is used for setting the value of the type attribute (type=text/css or type=text/xsl).
1 The –stylehref parameter is used for setting the value of the HREF attribute that specifies the location of the
stylesheet using an absolute path. For example: href=/mystylesheet.css or href=/stylesheets/
mystylesheet.xsl. The name of the stylesheet can be any name but it must contain an extension of either .css
or .xsl.
Here is an example of a FileMaker query string that generates client-side stylesheet processing:
http://localhost/fmi/xml/fmresultset.xml?-db=products-lay=sales&-findall&-styletype=text/xsl
&-stylehref=/mystylesheet.xsl
Note This “/” in “-stylehref=/document.xsl” in this example is used because the stylesheet is located in the
root folder of the web server software. Use a URL for the stylesheet that uses an absolute path to specify its
location on the web server. The stylesheet can also be located on another web server.
Based on this request, the Web Publishing Engine will include the following processing instruction in the
XML document:
<?xml-stylesheet type="text/xsl" href="/mystylesheet.xsl"?>
Copy or place the stylesheet for client-side processing on the web server in the location specified by the
absolute path in the URL for the HREF attribute.
Important Do not place stylesheets for client-side processing inside the xslt-template-files folder, which is used
for server-side processing of XSLT stylesheets. See
“Using FileMaker XSLT stylesheets in a web site or
program” on page 45.
Note Some web browsers do not support client-side processing. For information, see the documentation for
your web browser.
Troubleshooting XML document access
If you have trouble accessing XML documents with the Web Publishing Engine, verify that:
1 The extended privileges in the database are set for XML Custom Web Publishing and assigned to a user
account. See
“Enabling Custom Web Publishing in a database” on page 17.
1 The database is hosted and opened by FileMaker Server. See FileMaker Server Administration Help.
1 The database account name and password you are using, if any, are correct.
1 The web server and the Web Publishing Engine are running.
1 XML Publishing is enabled in the Web Publishing Engine. See the FileMaker Server Advanced Web
Publishing Installation Guide
.