Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


ggt667 last won the day on June 6 2017

ggt667 had the most liked content!

Community Reputation

8 Neutral

About ggt667

  • Rank
    Street Stupid, Nerd Stupid, Geek Wiz

Profile Information

  • Title
    Philosopher, Partner, and Keyboard Masseur
  • Industry
    Logistics, horticulture production
  • Gender
  • Location
  • Interests
    Trikke T12 Roadster, bouldering, DIY woodwork

Contact Methods

  • Website URL
  • Skype
  • MSN
    iMessage: ggt667@me.com and FaceTime

FileMaker Experience

  • Skill Level
  • FM Application
    11 Advanced

Platform Environment

  • OS Platform
  • OS Version
    OS X, Arch linux, Joyent SmartOS, iOS

Recent Profile Visitors

6,414 profile views
  1. ggt667

    Should I upgrade to Filemaker 17

    Is it yet possible to install self signed certificates in FileMaker 17? To my knowledge I have only seen this documented for FileMaker 16 in this article: https://blog.beezwax.net/2017/12/03/creating-your-own-ssl-certificates-for-filemaker/ That said I'm not able to make a valid self signed certificate following that article; I have been better off using openssl in terminal. Publicly signed SSL certificates are good to document who has a web site. Self signed SSL certificates are way better for security.
  2. ggt667

    SAXParseException only in HTTP

    Where do you split the export into separate files? And why do you use for-each? The error you are asking about is sometimes due to async sources and FileMaker being sync. It's hard to help you without any hands-on.
  3. Rerun this year?
  4. ggt667

    CWP internal server error 500

    Try the server's Documents folder
  5. If it's not already in MacOS High Sierra: brew install netcat nc -l 8080 ( Any port above 1024 should work without sudo )
  6. To track down this issue I would change the URL to 80 and launch netcat; as such: nc -l 8080 and change my queries accordingly; using the URL: localhost:8080, then I would compare what the queries look like on the server side.
  7. ggt667

    FM17 Server installs way outdated PHP

    Use CWP and do the PHP yourself. FileMaker's PHP is heading down the same rabbithole as their XSLT; they just don't give a flying tomato in reverse about keeping up to date.
  8. ggt667

    FX.PHP and FM10>FM16..oddities. Help?

    If you'd like I can log in and take a look. If you make the query to: /fmi/xml/FMPXMLRESULT.xml there should be no changes to the XML grammar between the different versions of FileMaker Server. /fmi/xml/fmresultset.xml on the other hand can change from version to version in FileMaker IIRC
  9. ggt667

    FMS Backup Strategy Best Practices

    In the server control panel you will see Schedules; that's where you configure scheduled backups. As for white paper I have not yet seen a good one. Personally I prefer ZFS for storage as this allows for system snapshots, rollback, compression, and separate backups rooted in the snapshots. ZFS has a mac implementation named o3x.
  10. ggt667

    Five Emerging Trends To Impact FileMaker Platform Security

    A good read, however I'm not sure what makes this FileMaker specific.
  11. server { server_name sub.domain.tld; location / { proxy_pass; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } Above works great for FileMaker 16 Server through nginx as reverse proxy. What I would like to be able to is to stimagtize what has to be mentioned after sub.domain.tld so that this part "/fmi/webd/sub" from here: would no longer be optional.
  12. Right now I'm doing a rewrite in Apache, however I assume there are ways to proxy a file using nginx. Your example is quite nice, it can make a custom looking login page. Perhaps that is more purposeful for some cases. My bad I forget that the current iteration of IWP is named webd: https://fmhelp.filemaker.com/docs/16/en/fmwd/index.html#accessing_linking
  13. Are there ways to make route or rewrite a domain name to 1 given IWP database?
  14. I see XML for integrations and data interchange with more complex structures( due to the built in validation ); and JSON for simpler data interchange such as user interfaces and signaling. Both are good for each their purpose. In the case of FileMaker PATCH will take recid and modid into consideration; while PUT will overwrite recid blindly. And if FileMaker Inc should ever read this a REST API should at least implement the following verbs/methods: 1 GET The GET method is used to retrieve information from the given server using a given URI. Requests using GET should only retrieve data and should have no other effect on the data. 2 HEAD Same as GET, but transfers the status line and header section only. 3 POST A POST request is used to send data to the server, for example, customer information, file upload, etc. using HTML forms. 4 PUT Replaces all current representations of the target resource with the uploaded content in full. 5 PATCH Amends the current representations of the target resource with the uploaded content. Note this is typically used for editing a subset of a record when changing as an example the name of a contact record; leaving the remainder of the fields untouched. 6 DELETE Removes all current representations of the target resource given by a URI. 7 CONNECT Establishes a tunnel to the server identified by a given URI. 8 OPTIONS Describes the communication options for the target resource. 9 TRACE Performs a message loop-back test along the path to the target resource.
  15. ggt667

    XLST for import to Filemaker

    As there are no attributes attached to that subtable, it's quite hard to extract those data as is; you will most likely have to composite data from the XSLT I gave you to generate the keys you need. Or if you are lucky you can use the XSLT I gave you and reimport the data to the same table if there is an appropriate primary key there somewhere. Or you can put values from name and value in one field. <COL> <DATA> <xsl:value-of select="listingText/name"/><xsl:text> </xsl:text><xsl:value-of select="listingText/value"/> </DATA> </COL>

Important Information

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