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
- Using server-side processing of scripting languages
- 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.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
- 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
Chapter 4
|
Introduction to Custom Web Publishing with XSLT 49
For more information about the CDML to XSLT mapping rules and other situations where you will have to
manually fix XSLT statements because the CDML tag conversion could not be done, see
appendix C,
“Converting CDML solutions to FileMaker XSLT.”
Notes
1 If there are any query parameters that reference CDML format files from database fields, you will need
to manually update the references in the database. If any such references are found in any of the
converted XSLT stylesheets, a note is inserted in the XSLT stylesheet reminding you to make the
changes in the database.
1 If the converted XSLT stylesheets include a FileMaker date or time extension function, such as
fmxslt:get_date(), then the function uses the “fm” formats for strings. The “fm” formats are MM/dd/yyyy
for date,
HH:mm:ss for time, and MM/dd/yyyy HH:mm:ss for timestamp. See “Using the date, time, and day
extension functions” on page 72. After conversion, you must manually change and localize date and time
formatting strings that are passed to these functions, such as changing Month/Day/Year to Day/Month/
Year.
Using the CDML Converter’s generated stylesheets
After fixing the errors in the converted XSLT stylesheets, you can use them with the Web Publishing Engine.
See the following section,
“Using FileMaker XSLT stylesheets in a web site or program.”
Testing the CDML Converter’s generated stylesheets
You should thoroughly test the converted XSLT stylesheets before using them in a production environment.
See
chapter 6, “Testing and monitoring a site.”
Using FileMaker XSLT stylesheets in a web site or program
Whether you have used the Site Assistant or the CDML Converter to generate XSLT stylesheets, or you have
created your own stylesheets from scratch, the steps for using them in a web site or program with the Web
Publishing Engine are the same.
To use FileMaker XSLT stylesheets in a web site or program:
1. Copy or place the XSLT stylesheets in the xslt-template-files folder, which is located inside the Web
Publishing
folder inside the FileMaker Server folder on the host where the Web Publishing Engine is
installed.
You can also place the stylesheets in an optional folder or folder hierarchy inside the xslt-template-files
folder.
2. If your XSLT stylesheets reference static files, such as static images or HTML files, place the static files
in their original folder hierarchy within the root folder on the web server. Make sure the relative path is
preserved.
For example, suppose an XSLT stylesheet references an image file called logo.jpg by using the HTML
tag
<img src="logo.jpg">. The logo.jpg file must be located in the following location on the web server:
<root folder>/fmi/xsl/logo.jpg