Jump to content


  • Posts

  • Joined

  • Last visited

About Genx

  • Birthday 03/17/1989

Profile Information

  • Gender
  • Location
    Brisbane, Australia

Contact Methods

  • Website URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Genx's Achievements

Grand Master

Grand Master (14/14)

  • First Post
  • Collaborator
  • Posting Machine Rare
  • Week One Done
  • One Month Later

Recent Badges



  1. Syntax looks fine. I'd suggest you debug what's actually getting posted... at the top of your form processing page (presumably this page), chuck in a print_r($_POST); and take a look at the output From the code you've pasted above, in the second example you have [value="Poor"'] - there's an extra quote there - might be breaking your post content.
  2. Makes sense - there's a cleaner way to do it but we can discuss that later. In the mean time to the actual issue: what does getCode return from the error object - will be eaiser to debug if it's an actual code rather than a paraphrased message.
  3. Need more information... i.e. why you're trying to use snapshot files at all.
  4. ... Super hard to read the above - would be helpful if you used the code tags provided in the editor. 1) Why is your related recs loop outside your record loop? In the above you're getting the related records only for the very last record... is that what you want? 2) What's the actual error code being returned... i.e. $relatedRecs->getCode() ?
  5. Hard to tell without any code. Most likely a security issue - does the account you're using have Full Access?
  6. Deploy the FileMaker Server and the Web Publishing role to a single machine, the linux box has nothing to do with FileMaker itself and doesn't need to be configured.
  7. Presuming your Header layout has a portal on it attached a Table Occurrance called "HeaderRelatedRecs": . . .foreach($records as $record){ $relatedRecs = $record->getRelatedSet("HeaderRelatedRecs"); if( !FileMaker::isError($relatedRecs) ){ foreach($relatedRecs as $relatedRec){ $myFormattedSubRecDataArray = array(); $myFormattedSubRecDataArray['record_id'] = $relatedRec->getRecordId(); $myFormattedSubRecDataArray['my_field'] = $relatedRec->getField("my_field"); $myFormattedDataArray[$record_count]['HeaderRelatedRecs'][] = $myFormattedSubRecDataArray; } } } . . .
  8. In order to communicate with FileMaker via its XML engine (which the PHP API does) you MUST install the "Custom Web Publishing Engine" (CWPE) - this component is a connecting service that processes inbound XML over a target web port / path, passes a command or series of commands to FileMaker server which then returns its response to the component which then in turn returns the XML. This is a complete and distinct component of FileMaker needs to be installed regardless of whether your PHP application sits on that server or somewhere entirely different. Components: 1) FileMaker Server 2) FileMaker CWPE 3) Your PHP engine Each component can sit on a separate server though 1+2 are normally located on the same machine.
  9. Are you sure you've actually configured CWP on the FM Server?
  10. The advantage of layouts as opposed to tables: you can return subsets of data in table by creating layouts with just specific fields on them. this will allow you to return larger sets of records with less overhead (resulting both from smaller data size and prevention of unnecessary unstored calculations) layouts are relationally aware - any portals that you have on your layout are accessible via a method on the record object (getRelatedSet()) without needing to perform separate queries to artificially reconstruct the relationships as you'd have to with ODBC. This has very large convenience and speed benefits. the API has a fairly critical bottleneck - the length of time it takes to execute a single API query is normally acceptable (depending on where the web server is in relation to the FileMaker server). If you are adding or modifying a complex object with significant amounts of related data, a single API call which adds and modifies all the records via the portals will execute exponentially (depending on how many related entities you have) faster than individual API calls for each and every record and related record. Layouts as context based data access methods are a constant concept in FileMaker and have been for a while - the API exposes this and essentially allows web developers to work well with FileMaker developers without needing to understand the nature of the calculations or relationships ... just that they exist (at this stage, these two groups [filemaker developers and web developers] are largely the same - if FileMaker ever gets their act together and improves the quality and speed of their web engine and the speed and reliability of their storage / server engine, this may change ... that being said i don't see too much hope for that any time soon despite the them of this years developer gathering supposedly being about "the cloud")
  11. If the page is coming up completely blank it's probably not a filemaker issue.. Try chucking an echo above your require statement and then running. Then try chucking an echo below your require statement and the running.
  12. Please nobody try to delete records like that... it's kind of like seeing an apple in a crate and unpacking the whole crate just to get to the apple you want.
  13. Hard to tell without actually seeing the code in FileMakerService.php - exiting with a global variable obviously won't work though.
  • Create New...

Important Information

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