March 2, 201411 yr We are having trouble getting our FMPro13 databases to talk to the website via FX.php. When we installed FMPRo 13 Server we ticked the 3rd party PHP option as we aren't going to be using the Filemaker PHP API. For FMPro11 we have the following settings in the databases security privileges area (which works fine): Access via Instant Web Publishing Engine - ticked Access via ODBC/JDBC - ticked Access via Filemaker Network (fmapp) - ticked Access via Filemaker Mobile (fmmobile) - not ticked (not being used) Access via XML web Publishing - ticked Access via XSLT Web Publishing - ticked Access via PHP Web Publishing - FMS only (fmphp) - not ticked In the Filemaker Pro 13 version of the same databases we have the following options: fmiwp Access via ODBC/JDBC (fmxdbc) Access via Filemaker Network (fmapp) Access via XML Web Publishing Engine - FMSA (fmxml) Access via PHP Web Publishing - FMS only (fmphp) Access via Filemaker WebDirect (fmwebdirect) + 2 settings for Filemaker Go which we aren't using Which of the above settings do we need to have ticked for FX.php to work? All advice gratefully received.
March 3, 201411 yr Author Thanks webko. In the FMPRo 13 Admin console under Web Publishing there are various settings. We have them set as follows at the moment: General Settings Enable logging for Web Publishing - not ticked PHP Publishing Enable PHP Publishing - unticked XML Publishing Enable XML Publishing - ticked Filemaker WebDirect Enable WebDirect - unticked But the databases are not talking to the web pages: The basic database call info is currently as follows: $News_Search=new FX($serverIP, $webCompanionPort, 'FMPro9'); $News_Search->SetDBData('News.fmp12', 'News', $groupsize); $News_Search->SetDBPassword('fmsadmin', 'fmsadmin'); We are also going to remove the database file extension and use $dataSourceType instead of 'FMPro9'. $News_Search=new FX($serverIP, $webCompanionPort, $dataSourceType); $News_Search->SetDBData('News', 'News', $groupsize); $News_Search->SetDBPassword('fmsadmin', 'fmsadmin');
Create an account or sign in to comment