viewing container data

[Jeremy Kipling]

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?

[jonathanstark]

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?

[Jeremy Kipling]

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.

[Baloo]

the only thing that comes to mind is an error message or some other text on the production server's "container bridge" file (i.e. the local php file that queries FMP and draws the image) Look at that page in your browser and see what comes up. If there is any text you should see it along with possibly the binary container data.

Once you get beyond the WYSIWYG wizards, I know somewhere between diddley and squat about firewall management, but I guess it's always possible it's blocking the binary data in the cURL request while letting the XML and text values through.

HTH

[Jeremy Kipling]

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.

[Baloo]

I can print out the binary container field data

I'm assuming by this you mean if the binary data is an image you can print out the image as opposed to the raw binary data.

Just in case you've overlooked the obvious does the daemon have read privileges to containerBridge.php?

Other thoughts what happens when you do the following:

right click on the place holder image

select and copy the URL listed for Location (Address (URL) in IE)

Paste it into your browser's address bar.

[Jeremy Kipling]

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.

[Baloo]

OK what that means is that the binary data is getting hosed when it renders on your production containerBridge.php page. Surfing to the long URL for a container bridge should bring up the image in a browser not the binary data. The most likely culprit is an error message getting inserted into the page. Try scanning through the binary data and see if you can spot any discernible text. Also double check your containerData.php file. Even a single white-space character rendered in front of the binary data will mess things up.