Jump to content

jonathanstark

Members
  • Content Count

    51
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jonathanstark

  • Rank
    member
  • Birthday 12/21/1968

Recent Profile Visitors

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

  1. It's not clear from you question whether or not you are storing the raw HMTL in FileMaker or if you are trying it compose it in the PHP based on FileMaker data. If you are storing HTML in FileMaker, you need to use getFieldUnencoded() instead of getField().
  2. Sounds like your problem is solved, but if anyone else would like to read up on checkboxes + php + filemaker, you might want to check out my article on the topic in Advisor: http://my.advisor.com/doc/19601
  3. Paging through result records is actually complex enough that the specifics of your situation can dictate the best approach.
  4. If I understand you correctly, you have a text field with rich text formatting and you want the formatting to bleed through to the web. Let's say your text field is called "Description" - in FileMaker, make a new calc field called "Description CSS" with the following formula: GetAsCSS ( Description ) Then, add Description CSS to the FileMaker layout that you are pointing your PHP query at. Then, in the PHP page where you are doing the query, you'll need to change this: $record->getField('Description'); to this: $record->getFieldUnencoded('Description CSS'); HTH, j
  5. If it were me, I'd have a text field that accepted the MM/YYYY data entry, and a calc field that converted it to MM/01/YYYY for any date calculation needs.
  6. Have you tried using Let to assign the result of the curl statement to a local var within the script?
  7. I've accomplished this in the past by creating a "before nav" script that I call at the top of all my nav scripts. In the before nav script, I deal with all the dirty work logic, and call a halt if necessary. It's an ugly solution, but AFAIK there isn't a better option in FileMaker.
  8. Hmmm... nothing that you mentioned raises any red flags that would be specific to container fields. Can you retrieve text data in both development and production environments?
  9. Glad to hear that that helped. If you want more info about best practices on the web, and general security considerations, I have a bunch of good links left over from my web security session at devcon that you can peruse here: Devcon 2009 Cheers!
  10. If memory serves, you use a period in a field name via CWP to indicate that you want to edit a particular repetition of a field. Hence the error.
  11. Have you tried setting up custom record level access permissions in Accounts & Privileges?
  12. As you pointed out, you *really* shouldn't have your "authentication" set up this way, but I'm not here to wag my finger ;-) First, you could add a check to the top of your PHP page that required a contactID like so: if(empty($_GET['contactID'])) { die('Sorry! Contact ID is required.'); } Next, you could add an exact field match operator to your query, just like you'd do in FileMaker Pro. So, if you are currently doing this: $request->addFindCriterion('contactID', $_GET['contactID']); then change it to this: $request->addFindCriterion('contactID', '=="' . $_GET['contactID'] . '"'); HTH, j
  13. Well, I don't know squat about IIS but on Apache, PHP errors are logged to the Apache error log by default (but you prolly already knew that). On my machine: /private/var/log/apache2/error_log You prolly also already saw this in the docs, but just in case: Using the web server access and error logs 1 IIS (Windows) The Microsoft IIS web server generates an access log file and displays errors in the Windows Event Viewer instead of writing them to a log file. The access log file, which is in the W3C Extended Log File Format by default, is a record of all incoming HTTP requests to the web server. You can also use the W3C Common Logfile Format for the access log. For more information, see the documentation for the Microsoft IIS web server. Using the Web Publishing Engine application log By default, the Web Publishing Engine generates an application log file that contains a record of Web Publishing Engine error, script, and user log information. The log file is named pe_application_log.txt, and is located on the Web Publishing Engine component of the FileMaker Server deployment: 1 IIS (Windows): :Program FilesFileMakerFileMaker ServerLogspe_application_log.txt
×
×
  • Create New...

Important Information

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