June 28, 200619 yr Just a quick observation: In servar_data: $webCompanionPort = 80; In fx_test: $testfx = new FX($serverIP,$WebCompanionPort); PHP is case dependant. Hence $WebCompanionPort should be exactly the same in both scripts. For OS X you can use the System Console to view the http error log. This may give you an indication of what is happening. Good Luck. Garry
June 28, 200619 yr Gary, hit the nail on the head (hey Gary forgot to look you up when I was in Sydney a few weeks ago). But to answer the database path question: You do not need the full path to the database. The only thing that FX.php will look for is if the database is open on the FMServer. Most of my errors have been because of case sensitive code. When something goes blank, this should always be the first place to check.
June 29, 200619 yr Author Thank you for your reply. We are also wondering if there is a username/password problem that is preventing PHP from finding the database. The username and password mentioned in the fxtest.php file is a Full Access username and password for the Manager.fp7 database, right? Not a username and password for the Filemaker Server itself. And the fmsadmin account that needs to be set up is a user account which must be added to the hosted database (eg Manager.fp7) in Accounts and Privileges. An account called fmsadmin doesnt need to be created to access the Filemaker Server itself? Finally does any special PHP code need to be added to server_data.php or other php files to get access to the filemaker server other than that mentioned in the files I quoted above? Regards, Steven
June 30, 200619 yr The only Usernames and Passwords you will require are those in the FM Users list for a particular database. No special PHP code is needed for the server_data.php script. Unfortunately, I don't know anything a "fmsadmin" account! All the best. Garry
July 10, 200619 yr Is there a user with the name "admin" in your databases? Can't remember the security for FM7/8, but in FM5/6 we use Web security databases that check to see if someone accessing the database has the correct credentials. In the web security databases we set up a user called "fx" that had the web security level privileges in our Filemaker databases. One quick thought might be to set up a user account 'fx' with a password (eg 'webaccess') in databases and then change the corresponding php code: $webUN = 'fx'; $webPW = 'webaccess'; let me know how you make out.
July 11, 200619 yr Author this problem has been fixed - the problem lay with the IP address of FM8SA quoted in the server_data.php file. It wasn't clear whether we were suppsoed to use the IP address of the FM8 Server where the DBs are hosted or that of FM8SA which can be hosted on the same server or on the web server. We eventually placed FM8SA on the web server so everything has the same IP address and it works fine.
Create an account or sign in to comment