Jump to content

Jeremy Kipling

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jeremy Kipling

  • Rank
  1. What I meant by print out the binary data, is that if I just get the container field and try to output it to the website as a regular field I see a bunch of what looks like garbage characters but is the raw binary data of the image. So I take this to mean that I can access the actual data, but I just can't display it as a proper image using the typical urlencode, containerBridge technique. I believe I tried your tests already. I think when right clicking on the place holder image and pasting into a browser, you get the long url you would expect from a container field. That test happens as expected. Thanks for the tips, I will experiment with them later since the server is currently up and being beta tested. Thanks.
  2. I think we are on the right track. It is the exact same code in containerBridge on both servers, and the binary data does come through the firewall. I can print out the binary container field data, I just can't render the image itself using: $image = 'getContainer('lu_drawing')).'" />'; This returns the browser's placeholder image.
  3. Hi Jonathan, Thanks for the reply. I sent you this question on your website as well. This issue remains unresolved. For a hopefully temporary workaround we are storing the images themselves on the production server, naming them with a primary key id and referencing them in the code that way. All other fields, including text data is retrieved without a problem on both servers. These container fields store the images within the filemaker file as opposed to storing a reference only.
  4. Hi all, I have a cwp solution using the FileMaker PHP API connecting to file hosted by FileMaker Server 10. The web server is outside of a firewall and the server and wpe are behind the firewall. When I use a couple of development environments as the web server everything works fine. Moving the web pages to the production server causes the container fields to no longer render. The only differences I see are the production server is running php 5.2.10, versus 5.2.9, the apache api version number is different (but both development and production are running apache 2) and the production server is a virtual server running linux. Development servers were either mac or pc and not virtual. Any ideas on what could be the problem with the production server?
  5. The plot thickens. After removing all cascading deletes and insuring that each user is running a separate session I found one case in which two users each saw the other ones related records in a portal. This portal shows records based on a relationship that uses a global field that each user selects by clicking on a parent record. Since globals are supposed to be session specific there is no conceivable way for this error to occurr. I am convinced it's hairy voodoo. I've spoken to several developers with years of experience and no one has ever seen anything like this.
  6. The entire record is being deleted. I hesitate to say deleted because it doesn't seem right that FileMaker would delete a record without the user, but the record is completely missing from the child table. I did find a cascading delete turned on in one of the relationships between the grandparent and child, directly using a global. I can't find anywhere in the database where that would have came into play inappropriately, but I removed it since it was weird and unnecessary as far as I can tell. If that doesn't fix the problem, and it very well may not, then FileMaker Inc. does have a serious problem.
  7. Hello, I have encountered a problem when 3 or more users are using a file through Server 7 ver 4. There is a three tier relationship in which the grandparent table has a one to many relationship with the parent table which in turn has a one to many with the child table. Records are created in all three tables and later modified, and every once in a while a record in the child table will go missing after modification of either the parent or grandparent table!! This then adversely affects calc fields in the other two tables that reference the child table. This only happens when 3 or more users are working on the file at the same time. They are not, however, working on the same records. VERY weird and troublesome.
  • Create New...

Important Information

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