AnsweredAssumed Answered

PHP Execute aborts after newFindAllCommand but not after newCompoundFindCommand

Question asked by davidrcrowe on Mar 26, 2014
Latest reply on Jul 17, 2014 by davidrcrowe

Summary

PHP Execute aborts after newFindAllCommand but not after newCompoundFindCommand

Product

FileMaker Server

Version

12

Operating system version

Windows Server 2008 R2 Standard Service Pack 1

Description of the issue

My PHP application issues "newCompoundFindCommand" or "newFindAllCommand" depending on whether the user, via the web form, enters any search constraints. The following sequence is repeatable:
1) Search for everything. PHP "echo" prior to the $findCommand->execute() is printed, but the first statement following, is not printed.
2) Search with a constraint (software now issues newCompoundFindCommand). Works fine.
3) Search again for everything. Now it works fine and continues to work fine until the user logs out of the application or refreshes the browser, at which point the error occurs again.

It is certainly possible that this is an error in my code, but there appears to be an exception within the FM PHP API, and given the limited information given to FM in the case of newFindAllCommand, it is hard to see how any inputs could be causing such a drastic failure.

Steps to reproduce the problem

See above.

Expected result

newFindAllCommand should always return all records on the specified layout.

Actual result

FM PHP API "execute" command appears to silently abort.

Exact text of any error message(s) that appear

No error message.

Workaround

None so far. Adding a field that is always a constant value would be a workaround, but the application does not have control over the layout, so it would force the database designer to add this field to every layout for which this application will be used.

Outcomes