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 3
|
Accessing XML data with the Web Publishing Engine 37
This section contains a summary of the FileMaker query commands and parameters. For more information
about using them in a query string, see
appendix A, “Valid names used in query strings.”
Note The Web Publishing Engine also supports an additional query command (–process) and three query
parameters that are defined for use only with FileMaker XSLT stylesheets. See
“Using query strings in
FileMaker XSLT stylesheets” on page 54.
Use this query command name To execute this command
–dbnames Retrieve names of all hosted and web-shared databases
–delete Delete record
–dup Duplicate record
–edit Edit record
–find Find record(s)
–findall Find all records
–findany Find a random record
–layoutnames Retrieve names of all available layouts for a hosted and web-shared
database
–new New record
–scriptnames Retrieve names of all available scripts for a hosted and web-shared
database
–view Retrieves layout information from a database if the FMPXMLLAYOUT
grammar is specified. Retrieves <metadata> section of XML document
and an empty recordset if the fmresultset or FMPXMLRESULT grammar is
specified.
Use these query parameter names With these query commands
–db (database name) Required with all query commands except –dbnames and –process
(XSLT requests only)
–field Required to specify a field in a URL for container requests. See “About
the URL syntax for FileMaker container objects in XML solutions” on
page 27.
fieldname At least one field name is required with –edit. Optional with –find. See
“fieldname (Non-container field name) query parameter” on page 93.
fieldname.op (operator) Optional with –find
–lay (layout name) Required with all query commands, except –dbnames, –layoutnames,
–scriptnames, and –process (XSLT requests only)
–lay.response (switch layout for XML
response)
Optional with all query commands, except –dbnames, –layoutnames,
–scriptnames, and –process (XSLT requests only)
–lop (logical operator) Optional with –find
–max (maximum records) Optional with –find, –findall
–modid (modification ID) Optional with –edit
–recid (record ID) Required with –edit, –delete, –dup. Optional with –find
–script (perform script) Optional with –find, –findall, –findany, –new, –edit, –delete, –dup, –view