Deprecation of XSLT API for Custom Web Publishing

Beginning with the next full version of FileMaker Server and FileMaker Server Advanced, the XSLT API for Custom Web Publishing and the XSLT Site Assistant will no longer be available.

As FileMaker software evolves the list of APIs and technologies it supports may change and less efficient interfaces may be deprecated in favor of new ones. If you are using XSLT in Custom Web Publishing or the XSLT Site Assistant, FileMaker recommends that you migrate your solution to use other more efficient APIs, technologies, or alternative features of the product to meet the same need in your solutions.

Note: FileMaker will continue to support XML and applying an XSLT style sheet during export. Here are some recommended resources to help you choose an alternative to XSLT:

About PHP Web Publishing: http://www.filemaker.com/support/technologies/php.html

FileMaker Server 11 Custom Web Publishing with PHP http://www.filemaker.com/support/product/docs/fms/fms11_cwp_php_en.pdf

2 thoughts on “Deprecation of XSLT API for Custom Web Publishing”

  1. I am building an Adobe AIR application using Flash Builder 4 and your FlexFM. Our FileMaker database is on our own server with FileMaker Server 10 Advanced. I have gone through “Flex FM How To”, hosted Hopper.fp7 so we could run the FlexFMSnippets, but still have a problem. Our AIR app runs fine and we can see all our FileMaker data, but I can’t get a FileMaker script to run. Am using appendix A from “FileMaker Server 10 Custom Web Publishing” to construct a query string. We have tried several versions of this:

    Could you please point us to information that may help solve our problem.

  2. I haven’t played aurond with this too much, but I did try it out quickly. It looks like the user name and password are stored in Session variables (if you aren’t familiar with PHP, Sessions let you carry data from one page to another in PHP). In the sites created by the Site Assistant, most of this seems to be handled in the FMView.php file; in fact, one of first lines in the file sets the name of the session ( session_name( abcd ) ); if you set the session name to be the same for every site, that looks like it takes care of the problem.

Leave a Comment

Your email address will not be published. Required fields are marked *

We're celebrating 20 years! Read about our journey here.

Party horn and confetti
Scroll to Top