Jump to content

ggt667

Members
  • Content count

    372
  • Joined

  • Last visited

  • Days Won

    4

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
    Male
  • Location
    Tellus
  • Interests
    Trikke T12 Roadster, bouldering, DIY woodwork

Contact Methods

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

FileMaker Experience

  • FM Application
    16 Advanced

Platform Environment

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

Recent Profile Visitors

5,900 profile views
  1. 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.
  2. 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
  3. 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.
  4. ggt667

    Five Emerging Trends To Impact FileMaker Platform Security

    A good read, however I'm not sure what makes this FileMaker specific.
  5. server { server_name sub.domain.tld; location / { proxy_pass http://10.0.0.10:8080; 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: 10.0.0.10:8080/fmi/webd/sub would no longer be optional.
  6. 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
  7. Are there ways to make route or rewrite a domain name to 1 given IWP database?
  8. 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.
  9. 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>
  10. REST/JSON and SOAP/XML are just 2 parallell technologies; I don't see one being newer or older than the other by any significance. REST/JSON booming due to its easily parsing in front end is not a reason for dropping SOAP/XML for data transport. And we all saw at DevCon what actively developing for means when it comes to REST/JSON; they are doing a minimum REST-like implementation; not an RFC implementation thereof. And as pr that definition FileMaker itself is deprecated. Seeing that both FMI/XMLRESULT and FMI/DATA will benefit from gzip compression in an nginx-like reverse proxy also removes the "size" argument.
  11. ggt667

    XLST for import to Filemaker

    Those data you are asking for is really stored in the XML as a related table. Are you sure you would like to flatten them? A separate table, with a separate XSLT, and a separate import would probably to do you good; here are my thoughts; this is not a piece of code that actually runs, it's just typed off the top of my head to give you the gist of how I would have done this. <xsl:template match="/titleListingTextSets/listingTexts/listingText"> <xsl:value-of select="../../titleId"/><!-- Or similar key--> <xsl:value-of select="name"/> <xsl:value-of select="value"/> or similar would probably be a better option in your solution; unless you really want to flatten the data. As pr example below( note this will be like importing "invoice rows" in relation to your existing data ): $ cat ~/titleListingTextSets_listingTexts_ListingText.xslt <?xml version="1.0" encoding="UTF-8"?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> <xsl:template match="/"> <FMPXMLRESULT xmlns="http://www.filemaker.com/fmpxmlresult"> <METADATA> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="titleId" TYPE="NUMBER"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="name" TYPE="TEXT"/> <FIELD EMPTYOK="YES" MAXREPEAT="1" NAME="value" TYPE="TEXT"/> </METADATA> <RESULTSET FOUND="{count(unscheduledTitles/title/titleListingTextSets/listingTexts/listingText)}"> <xsl:for-each select="unscheduledTitles/title/titleListingTextSets/listingTexts"> <ROW MODID="1" RECORDID="1"> <COL> <DATA> <xsl:value-of select="../../titleId"/> </DATA> </COL> <COL> <DATA> <xsl:value-of select="listingText/name"/> </DATA> </COL> <COL> <DATA> <xsl:value-of select="listingText/value"/> </DATA> </COL> </ROW> </xsl:for-each> </RESULTSET> </FMPXMLRESULT> </xsl:template> </xsl:stylesheet> xsltproc ~/titleListingTextSets_listingTexts_ListingText.xslt ~/Sample_Data.xml | tidy -i -xml -wrap 0
  12. Hey Lee, At least now others can search and find a reasonable answer. G
  13. No, but user experience may improve. Somehow https responds quicker in many cases. free options can be found in the dehydrated project and the best is to sign your own as described by beezwax in their blog; https://blog.beezwax.net/2017/12/03/creating-your-own-ssl-certificates-for-filemaker/ Of course NSA-worshippers will not agree with this as they may have to do some work to decipher your traffic Also note that if you did not sign your own certificate; the SSL is pr definition not secure. For people serious about their SSL root certificates should never leave your SD-card or other removable storage stored in a physical safe; except for the times you turn off your WiFi and disconnect your ethernet, then insert the SD card for signing new related certs; remember to put the SD card back in the safe before you connect to the www again.
  14. No client, it's all HTML5, supports MSRDP and VNC; deployed correctly may or may not be competing with citrix when it comes to bandwidth use.
  15. Dear forum: What is deprecated about FX.php? I read in the topic that FX.php is deprecated. as far as I am concerned FX.php is up to date for FileMaker 16 and php 7.
×

Important Information

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