Web Publishing with PHP and FileMaker 9- P9 ppt

Here are the key lines, starting from the top: Make your FileMaker connection object: $fm = new FileMakerFM_FILE, FM_HOST, FM_USER, FM_PASS; Use the getRecordByIdmethod of the FileMaker

Trang 1

Drill Down Pages

So, that’s it for the view links Let’s look at the view page:

<?php

define( ‘FM_HOST’, ‘127.0.0.1’ );

define( ‘FM_FILE’, ‘Product Catalog’ );

define( ‘FM_USER’, ‘esmith’ );

define( ‘FM_PASS’, ‘m4rg0t’ );

include (‘FileMaker.php’);

$fm = new FileMaker(FM_FILE, FM_HOST, FM_USER, FM_PASS);

$record = $fm->getRecordById(‘Product’, $_GET[‘recid’]);

$id = $record->getField(‘ID’);

$name = $record->getField(‘Name’);

$model_number = $record->getField(‘Model Number’);

$price = $record->getField(‘Price’);

$created_at = $record->getField(‘Created At’);

$created_by = $record->getField(‘Created By’);

?>

<html>

<head>

</head>

<body>

<tr>

</tr>

<tr>

</tr>

<tr>

<th>Model Number</th>

</tr>

<tr>

<th>Price</th>

</tr>

<tr>

<th>Created At</th>

</tr>

CHAPTER 6 Viewing FileMaker Data

Trang 2

<th>Created By</th>

</tr>

</table>

</body>

</html>

In my opinion, this is an example of where FileMaker.phpreally shines After you have

an internal record ID, it’s really easy to work with a record This page is pretty simple

Here are the key lines, starting from the top:

Make your FileMaker connection object:

Use the getRecordById()method of the FileMaker connection object to get a reference to the record object in question, and store the reference in the $recordvariable:

$record = $fm->getRecordById(‘Product’, $_GET[‘recid’]);

NOTE

Note that, in practice, it would be considered good form to check first that

$_GET[‘recid’]actually existed and contained a value

The$recordvariable will now contain a record object for the record in question Next, use the getField()method to pull the values out of the record by field name:

$id = $record->getField(‘ID’);

$name = $record->getField(‘Name’);

$model_number = $record->getField(‘Model Number’);

$price = $record->getField(‘Price’);

$created_at = $record->getField(‘Created At’);

$created_by = $record->getField(‘Created By’);

All that’s left is to burp out the variables in the context of the HTML template:

<html>

<head>

</head>

<body>

<tr>

Viewing FileMaker Data

Trang 3

<tr>

</tr>

<tr>

</tr>

<tr>

<th>Price</th>

</tr>

<tr>

<th>Created At</th>

</tr>

<tr>

<th>Created By</th>

</tr>

</table>

</body>

</html>

Summary

We covered a lot of ground in this chapter, so let’s recap Regarding FileMaker.php, you learned:

To include FileMaker.phpin your PHP pages to get access to the features of the FileMaker API for PHP

How to create a new FileMaker connection object

How to use the newFindAllCommand()method of the FileMaker connection object

How to use the addSortRule()method of the FileMaker request object

How to use the newFindCommand()method of the FileMaker connection object

How to use the addFindCriterion()method of the FileMaker request object

How to use the getRecords()method of the FileMaker result object

How to use the getField()method of the FileMaker record object

How to use the getRecordId()method of the FileMaker connection object

CHAPTER 6 Viewing FileMaker Data

Trang 4

And, in terms of pure PHP, you learned:

How to use the andoperator in an ifstatement

How to use the defineconstruct to create constants

That trying to use a variable or array element that does not exist will trigger a PHP warning

This chapter was devoted to viewing FileMaker data In the next chapter, I will build on these concepts to show you how to build pages that will allow users to alter your

FileMaker data

Summary

Trang 5

This page intentionally left blank

Trang 6

IN THIS CHAPTER

.Introduction

.Creating Records

.Deleting Records

.Editing Records

Altering FileMaker Data

Introduction

In this chapter, I show you how to create web pages

capable of altering data that is stored in your FileMaker

database When I say alter, I mean:

Creating records

Deleting records

Editing records

Naturally, you are not going to want the general public

doing these sorts of things to your product catalog

However, it might make a lot of sense to allow members of

your workgroup to perform these actions

A fairly common setup is to have these sorts of pages

published only on your company intranet, as opposed to

the public Internet By definition, your company intranet

would not be accessible to the general public, so only

company employees would be able to access it in the

first place

I will presume this “intranet” scenario for the duration of

the chapter

Creating Records

If you want to allow employees to create new records via a

web browser, the first thing you need to do is give them a

web page with a New Product button to click See Figure

7.1 for an example of how it will look in a browser

Trang 7

FIGURE 7.1 The New Product button provides navigation to the New Product page.

Here is a modified example of the product list code from Chapter 6, “Viewing FileMaker Data.” The only difference is that this example has a bit of HTML appended near the bottom:

<?php

define( ‘FM_HOST’, ‘127.0.0.1’ );

define( ‘FM_FILE’, ‘Product Catalog’ );

define( ‘FM_USER’, ‘esmith’ );

define( ‘FM_PASS’, ‘m4rg0t’ );

require_once (‘FileMaker.php’);

if(isset($_GET[‘search’]) and $_GET[‘search’] != ‘’) {

$search = $_GET[‘search’];

$request = $fm->newFindCommand(‘Product’);

$request->addFindCriterion(‘Name’, $search);

} else {

$search = ‘’;

$request = $fm->newFindAllCommand(‘Product’);

}

if(isset($_GET[‘sortby’]) and $_GET[‘sortby’] != ‘’) {

$request->addSortRule($_GET[‘sortby’], 1);

}

$result = $request->execute();

$records = $result->getRecords();

$rows = ‘’;

foreach ($records as $record) {

$rows = ‘<tr>’;

$rows = ‘<td><a href=”06_05.php?recid=’.$record->getRecordId()

➥’”>view</a></td>’;

$rows = ‘<td>’.$record->getField(‘ID’).’</td>’;

$rows = ‘<td>’.$record->getField(‘Name’).’</td>’;

$rows = ‘<td>’.$record->getField(‘Model Number’).’</td>’;

CHAPTER 7 Altering FileMaker Data

Trang 8

$rows = ‘<td>’.$record->getField(‘Price’).’</td>’;

$rows = ‘<td>’.$record->getField(‘Created At’).’</td>’;

$rows = ‘<td>’.$record->getField(‘Created By’).’</td>’;

$rows = ‘</tr>’;

}

?>

<html>

<head>

</head>

<body>

<p>

Product Name Search:

</p>

</form>

<tr>

➥&sortby=ID”>ID</a></th>

➥&sortby=Name”>Name</a></th>

➥&sortby=Model+Number”>Model Number</a></th>

➥&sortby=Price”>Price</a></th>

➥&sortby=Created+At”>Created At</a></th>

➥&sortby=Created+By”>Created By</a></th>

</tr>

<?php echo $rows; ?>

</table>

</form>

</body>

</html>

Creating Records

Trang 9

These three lines near the bottom are the only change:

</form>

All I have done here is tack on a tiny form that points to a different page, in this case named07_02.phpas you can see in the actionattribute of the formtag It’s really just navigation to the page that allows the user to create a new record See Figure 7.2 for an example of what the new record page looks like in a browser

FIGURE 7.2 The New Product page allows users to add products to the database

Here is the code in the 07_02.phppage:

<?php

define(‘FM_HOST’, ‘127.0.0.1’);

define(‘FM_FILE’, ‘Product Catalog’);

define(‘FM_USER’, ‘esmith’);

define(‘FM_PASS’, ‘m4rg0t’);

$message = ‘’;

if (isset($_POST[‘action’])) {

if ($_POST[‘action’]==’Cancel’) {

$message = ‘<p>Action cancelled Record was not created.</p>’;

} elseif ($_POST[‘action’]==’Save’) {

$request = $fm->newAddCommand(‘Product’);

$request->setField(‘Name’, $_POST[‘name’]);

$request->setField(‘Model Number’, $_POST[‘model_number’]);

$request->setField(‘Price’, $_POST[‘price’]);

$request->execute();

$message = ‘<p>Record was created.</p>’;

}

Trang 10

?>

<html>

<head>

</head>

<body>

<?php echo $message; ?>

<tr>

</tr>

<tr>

</tr>

<tr>

<th>Price</th>

</tr>

</table>

<p>

</p>

</form>

</body>

</html>

Let’s take it from the top The first new line you come across is this:

$message = ‘’;

What I am doing here is initializing the $messagevariable to an empty string because I don’t know at this point in the script if I’m going to have a message for the user or not Ultimately, I’ll be echoing out the $messagevariable in the HTML template portion of the page Setting the variable to an empty string protects me from the possibility of echoing out a nonexistent variable later on, which would cause a PHP warning

Next, I check to see whether the user has submitted a POSTrequest to this page this time around:

if (isset($_POST[‘action’])) {

Creating Records

Trang 11

As you have seen in previous examples, this page can behave differently depending on how it was requested If this page was requested by the user clicking the New Product button on page 07_01.php, the $_POST[‘action’]array element will not be set, for two reasons:

That form used the GETmethod, so the POSTarray won’t exist

There were no elements in that form named action

However, if the user requested this page from this page, there will be a POSTarray That’s because the form on this page—which we will look at in a second—uses the POSTmethod, and there will be a POSTelement named actionbecause the form has an input named action

Actually, the form on this page has two inputs named action Here they are:

Because the user can only click one button at a time, the $_POST[‘action’]array element

is going to either evaluate to Save, or Cancel In the code, I opted to check for Cancel first:

if ($_POST[‘action’] == ‘Cancel’) {

$message = ‘<p>Action cancelled Record was not created.</p>’;

Previously, I initialized the $messagevariable to an empty string just in case it didn’t get set elsewhere in the script If the user clicks the Cancel button, the $messagevariable does get set, as you can see here So, as the page continues to load and makes its way down to the HTML template section, this Cancel message is echoed out to the browser

Of course, the user doesn’t have to click Cancel The user could have clicked Save, which would have triggered the code block beginning with this line:

} elseif ($_POST[‘action’]==’Save’) {

This Save section is really the meat of this example, so I will take it line by line First, I includeFileMaker.php I could have done that at the top, but I only need it if the user is actually saving the new record, so I stuck it in the Save block:

Then, as usual, I create my connection to FileMaker:

Trang 12

Here’s something new This is where I call the newAddCommand()method of the FileMaker connection object The newAddCommand()method requires that you give it a layout

name—Product, in this case

$request = $fm->newAddCommand(‘Product’);

Then, all you have to do is use the setField()method of the $requestto tell it which field values to assign to each field To do so, you just pull them out of the submitted POST superglobal array:

$request->setField(‘Name’, $_POST[‘name’]);

$request->setField(‘Model Number’, $_POST[‘model_number’]);

$request->setField(‘Price’, $_POST[‘price’]);

NOTE

Sending data to the database directly from the $_POSTsuperglobal array is generally

considered a security risk Please refer to Appendix B, “Security Concerns,” for more

information on this topic

After you have that done, just execute the $request:

$request->execute();

Doing so creates the record in FileMaker and sets the field values as you instructed The only thing left to do is notify the user:

$message = ‘<p>Record was created.</p>’;

This finally brings us to the HTML template portion of the page It is all just plain HTML, with the exception of this line, where I am echoing out the $messagevariable:

<?php echo $message; ?>

This is why I initialized the $messagevariable to an empty string If this was the first

page load and there was no message for the user, PHP would throw an error when it got

to this line

Deleting Records

Back in Chapter 6, I added a column of view links to the product list page In very similar fashion, I am now going to add delete links to the product list page The finished product

will look similar to Figure 7.3

Deleting Records

Định dạng
Số trang	15
Dung lượng	195,92 KB