Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Featured Replies

  • Newbies

I am attempting to use XSLT with Custom Web Publishing and continue to get the following error when attempting to connect via the web. I am using FileMaker Server 7 Advanced.

"FileMaker Custom Web Publishing with XSLT - The requested stylesheet file could not be found (FILE-ER0001)" (followed by the name of the file).

I have checked all of the following:

1. The stylesheet (.xsl file) has been placed in the xslt-template-files folder (inside the Web Publishing Folder; inside FileMaker Server 7 folder; on the host where Web Publishing Engine is installed)

2. The corresponding database has extended privileges added (fmxslt) and assigned to the user account

3. The web server is running & the Web Publishing Engine is working; with XSLT enabled; and the corresponding .fp7 database file is shown as being published via XSLT

4. The url matches the example given in the Custom Web Publishing Guide and I have checked to make sure folder/file names are correct ex. http:///fmi/xsl//

What am I missing? Could this be a firewall issue?

Additional info: I have IWP running fine from this server and I have also successfully served and accessed xml data using a url request.

Thanks for any help you can give,

LHB

Check if the .xsl files have the right permissions: they must belong to group fmsadmin and this group must be able to read them.

  • Author
  • Newbies

I re-checked the settings and permissions are set correctly to fmsadmin with read & write privileges granted on all my xsl files. Any other ideas?

Thanks, LDHB

Restart the WPE (or switch it to development mode, then again back to production mode).

  • 5 weeks later...
  • Author
  • Newbies

Thanks for your suggestions, Martin. I finally discovered that ports were being blocked by a firewall. Once those were opened up, the problem was solved.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.