A standard install of FMS installs PHP... the correct version of PHP with no need to configure anything.
Php is working. We have confirmed that. However, we have web pages that populate data that is entered into fm databases on the web server. For instance, a calendar.php page displays our web page with data from the calendar.fm# db. Right now we just get a 504 error. I have checked the console for apache errors and there is nothing specific to point me in the right direction. It also does not give us out standard web page error that is customized for our site.
For the life of me I just don't know where to look to find the problem.
I'm sorry I can't give more specific information. It simply was not documented well by the precious web administrator.
Sent from my iPhone
Is it a 504 Gateway timeout (HTTP error)?
504 Value in field is not unique as required in validation entry options (FileMaker error)?
504 Remote administration: Enabled (FileMaker Server informational notice)?
Sorry. My mistake.
"Http error 500 (internal server error). An unexpected condition was encountered while the server was attempting to fulfill the request."
Sent from my iPhone
The thing is that several versions of PHP can happily co-exist.
If you ran :
<?php phpinfo() ?>
I think you might find that the PHP you are using is the one in the standard PHP path.... not the FileMaker Path.
I have to look this up every time... but I found this thread useful:
whoops... that is only part A. I'll have a look for the other reference when I get back from the airport.
Message was edited by: Lyndsay Howarth
You may be right Lindsay.
I looked at that link. No help. All the files look as though they are in the right place, I guess.
index.php is in Webserver/Documents
info.php is in Webserver/Documents
filemaker.php is in Webserver/Documents
"filemaker" directory for the PHP API is in Webserver/Documents
php.ini is in /etc
php5 module is active in the Server admin panel
From the FileMaker Server Console, can you pull up the test page and test the sample PHP that came with the install? what do you get?
This is always my first step to diagnosing what's going on.
Built in FM PHP TEst is successful
Ok, Now I have corrected one part of the issue(not the important part).
I was getting the 500 error.
I went into the root webserver/serverfolder and there was our php file there. I named it "Calendar.php.temp" and now I get the proper error redirect page that was not showing up before.
You can see it here:
I do believe that the proper php file exists in a directory called "Connections"
I want to reiterate something. I said this in my first post:
"I have tried editing the httpd.conf file to add the FMI_Configuration .../libphp5.so file and it broke our server.
However, the regular php5 module was still active in the same file."
I want to emphasize here that the standard php line is in that conf file, but the FM line is not. They could not coexist, so I took that FM version back out.
Perhaps I should go back into that file and activate the FM line instead of the standard php5 line?
I don't mess with the conf and ini files when FMS installs, unless it's in the instructions. Take a look at your php.ini file, too
I'll look at the permissions. In the meantime, I noticed this:
Is the FM PHP API compatible with APACHE 2 at all?
We are running Apache version 2 on )S 10.6 and that web page clearly says that it is only compatible with Apache version 1:
NOTE: In the supported Mac OS X versions, Apache is already installed. Only the version of Apache 1.3.x that is installed as part of Mac OS X and Mac OS X Server is supported.
Am I nuts?
Where is the php.ini file that I need to look at and what am I looking for?
You can search for "php.ini", but note that you may need to search for "invisible" files. If you have more than ONE php.ini, well, discover where they are and that may be a clue to problems, too.
If you run the "phpinfo();" in a file on your web server, the path to this "ini" may be there next to "Loaded Configuration File" label.