Xataface Forums

Hi Shannah,

Looks very good. Probably perfect for a novice like me (I care more about data than about the programming). But I had a few problems at installation:

1. I'm using the popular Marc Liyanage installation of MYSQL 5 and PHP (www.entropy.ch) rather than the standard Apple distribution. Had no problems at all (e.g. with PHPMyAdmin) with this installation until I ran makesite. It appeared to be looking for the socket at var/mysql/mysql.sock. That may be the standard place, but MYSQL Administrator (from MYSQL) reports it as being at /tmp/mysql.sock. Worked around this by using your 'manual install' instructions

2. Had to chmod everything in /dataface to 777 to get the images etc to show in the interface

3. Initially got a bunch of errors with the routines to read the column titles. Possibly fixed these by eliminating the comma from the 50th postiion in Line 111 of QueryTool.php (after the opening quotes in the SEL query) so that it now reads:

$sql = "SELECT ".implode(',',$keys)."$titleColumn as __titleColumn__ FROM ".$this->_table->tablename;

Maybe this doesn't REALLY fix things but just gets me past an initial hiccup. Because I can't get the 'list' functions in the DB interface to work: e.g. if Dataface returns 20 records from the DB, only #20 is listed. They're long records (the DB is a single-table) containing 20 or so fields that scroll off to the right of the screen. But I can't see why this should be a problem. Can you?

Will keep digging.

Best wishes,

Peter

Um ... I should have added that the errors I got before removing the inital, empty, item in the SELECT query were just the standard MYSQL errors ('You have an error near .... ')

Hi Peter,

A couple of things.

1. The comma that you removed needed to be there. The problem was actually that you didn't have any primary keys defined in your table.

2. You should not have had to chmod 777 everything. Just the Dataface/templates_c directory. Everything else will work with directories 755 and files 644.

3. The failure to find mysql.sock in the makesite script is likely because your php command line binary uses a different PHP that is not set up for mysql (probably the default PHP install) than the PHP for your webserver. In cases like this, you did the right thing by doing the manual install.

Hope this helps.

-Steve

Great diagnosis, Shannah. Thanks.

Mr. Steve,

Is the issue here and the solution, especially regarding the mysql.sock and php version across platforms or specific to Mac?

(Currently putting together the installation part of the manual and want to include all issues someone might run into.)

This issue is not necessarily specific to Mac. It is a situation that you will run into when you are using PHP without MySQL support turned on. The default PHP on Mac (at least used to) have MySQL support disabled by default. It is quite common for Mac users to just install the Marc Lyanage (sp??) build and use that instead of the default. This install sets up the new PHP as the default for Apache, but the command line PHP remains the original PHP install (without MySQL support) unless you explicitly use the new version on the command line.

-Steve