Web Publishing with PHP and FileMaker 9- P12 pps

We have to remember toclose our table, form, and PHP tags, and then output the HTML template exactly like the last page example... Altering Related RecordsLet’s modify the web page to al

Trang 1

The rest of the page is pretty humdrum compared to all that We have to remember to

close our table, form, and PHP tags, and then output the HTML template exactly like the last page example

$portal_html = ‘</table>’;

$portal_html = ‘</form>’;

?>

<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>

<tr>

<th>Created By</th>

</tr>

</table>

<?php echo $portal_html; ?>

</body>

</html>

Creating Related Records

Trang 2

Altering Related Records

Let’s modify the web page to allow users to edit or delete related records in the portal by adding two hyperlinks to the third column See Figure 8.15 for an example of the page displayed in a browser

FIGURE 8.15 Users now have navigation to edit or delete pages for related inventory records

The concept here is almost identical to the edit and delete links that we covered in Chapter 7, “Altering FileMaker Data.” There, we added edit and delete links to the product list page Here, we are adding those same links to the portal

Here is the completed code:

<?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’);

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

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

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

$new_row = $record->newRelatedRecord(‘Inventory’);

$new_row->setField(‘Inventory::Location’, $_POST[‘location’]);

$new_row->setField(‘Inventory::Quantity’, $_POST[‘quantity’]);

$result = $new_row->commit();

}

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

Trang 3

$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’);

$portal_records = $record->getRelatedSet(‘Inventory’);

$portal_html = ‘<form action=”08_02.php?recid=’

➥$record->getRecordId() ‘“ method=”post”>’;

$portal_html.= ‘<table border=”1”>’;

$portal_html.= ‘<tr>’;

$portal_html.= ‘<th>Location</th>’;

$portal_html.= ‘<th>Quantity</th>’;

$portal_html.= ‘<th> </th>’;

$portal_html.= ‘</tr>’;

foreach($portal_records as $portal_record) {

$portal_html.= ‘<td>’ $portal_record->getField(‘Inventory::Location’)

➥ ‘</td>’;

$portal_html.= ‘<td>’ $portal_record->getField(‘Inventory::Quantity’)

➥ ‘</td>’;

$portal_html.= ‘<td>’;

$portal_html.= ‘<a href=”08_04.php?recid=’.$portal_record->getRecordId().’”>

➥edit</a>’;

$portal_html.= ‘ ’;

$portal_html.= ‘<a href=”08_05.php?recid=’.$portal_record->

➥getRecordId().’”>delete</a>’;

$portal_html.= ‘</td>’;

}

$portal_html.= ‘<td><input type=”text” name=”location” value=”” /></td>’;

$portal_html.= ‘<td><input type=”text” name=”quantity” value=”” /></td>’;

$portal_html.= ‘<td><input type=”submit” name=”new_portal_row”

➥value=”Save” /></td>’;

$portal_html.= ‘</table>’;

$portal_html.= ‘</form>’;

?>

<html>

<head>

</head>

<body>

<tr>

Trang 4

</tr>

<tr>

</tr>

<tr>

</tr>

<tr>

<th>Price</th>

</tr>

<tr>

<th>Created At</th>

</tr>

<tr>

<th>Created By</th>

</tr>

</table>

</body>

</html>

Here is the completed code with descriptions inline It begins with the usual suspects:

<?php

define(‘FM_HOST’, ‘127.0.0.1’);

Here is the code block that handles any incoming requests for the creation of a new portal row It’s identical to the preceding example

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

$new_row = $record->newRelatedRecord(‘Inventory’);

$new_row->setField(‘Inventory::Location’, $_POST[‘location’]);

$new_row->setField(‘Inventory::Quantity’, $_POST[‘quantity’]);

Trang 5

$result = $new_row->commit();

}

This section is also identical to the prior examples We are just grabbing the field values from the Product record so we can output them in the HTML template section at the end

of the page

$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’);

Next, I am prepping for the foreachloop by compiling the open HTML for the portal

form and table I get the related set, open the form and table tags, and load the header

HTML

$portal_records = $record->getRelatedSet(‘Inventory’);

$portal_html = ‘<form action=”08_02.php?recid=’ $record->getRecordId()

➥ ‘“ method=”post”>’;

$portal_html.= ‘<table border=”1”>’;

$portal_html.= ‘<th>Location</th>’;

$portal_html.= ‘<th>Quantity</th>’;

$portal_html.= ‘<th> </th>’;

Here is the start of the foreachloop that creates the guts of the portal HTML

foreach($portal_records as $portal_record) {

$portal_html.= ‘<td>’ $portal_record->getField(‘Inventory::Location’)

➥ ‘</td>’;

$portal_html.= ‘<td>’ $portal_record->getField(‘Inventory::Quantity’)

➥ ‘</td>’;

$portal_html.= ‘<td>’;

The following line is new to this example, but should look familiar because I used a

similar technique in Chapter 7 for the View Product page I am using the getRecordId() method to pull the internal record ID out of the portal record object so I can include it in the URL that points to the edit page We will look at the edit page in the next example

$portal_html.= ‘<a href=”08_04.php?recid=’.$portal_record->getRecordId()

➥.’”>edit</a>’;

Trang 6

This line just inserts a nonbreaking space between the edit link and the delete link:

$portal_html.= ‘ ’;

Here is the delete link It’s just like the edit link except that it points to a different page and is displayed as “delete,” of course

$portal_html.= ‘<a href=”08_05.php?recid=’.$portal_record->getRecordId()

➥.’”>delete</a>’;

These lines close out the td,tr, and foreachloop:

$portal_html.= ‘</td>’;

}

Next, we have the code that draws the new related record row It’s identical to the

previous example

$portal_html.= ‘<td><input type=”text” name=”location” value=”” /></td>’;

$portal_html.= ‘<td><input type=”text” name=”quantity” value=”” /></td>’;

$portal_html.= ‘<td><input type=”submit” name=”new_portal_row”

➥value=”Save” /></td>’;

Now, just close the table, the form, the PHP block, and output the HTML template exactly like before

$portal_html.= ‘</table>’;

$portal_html.= ‘</form>’;

?>

<html>

<head>

</head>

<body>

<tr>

</tr>

<tr>

</tr>

<tr>

Trang 7

</tr>

<tr>

<th>Price</th>

</tr>

<tr>

<th>Created At</th>

</tr>

<tr>

<th>Created By</th>

</tr>

</table>

</body>

</html>

Editing a Related Record

Editing a related record is exactly the same as editing any other record That being the

case, this example is going to be the same as the Edit Record example in Chapter 7 except that it will be pointed at an Inventory record instead of a Product record See Figure 8.16 for an example of the page displayed in a browser

FIGURE 8.16 The edit page for an inventory record

<?php

define(‘FM_HOST’, ‘127.0.0.1’);

Trang 8

$message = ‘’;

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

$edit = $fm->newEditCommand(‘Inventory’, $_REQUEST[‘recid’]);

$edit->setField(‘Location’, $_POST[‘location’]);

$edit->setField(‘Quantity’, $_POST[‘quantity’]);

$edit->execute();

$message = ‘<p>Your changes have been saved</p>’;

}

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

$location = $record->getField(‘Location’);

$quantity = $record->getField(‘Quantity’);

?>

<html>

<head>

</head>

<body>

<?php echo $message; ?>

<input type=”hidden” name=”recid” value=”<?php echo $record->getRecordId();

➥?>” />

<tr>

<th>Location</th>

<td><input type=”text” name=”location”

➥value=”<?php echo $location; ?>” /></td>

</tr>

<tr>

<th>Quantity</th>

<td><input type=”text” name=”quantity”

➥value=”<?php echo $quantity; ?>” /></td>

</tr>

</table>

</form>

</body>

</html>

And here it is again with the few minor changes called out

<?php

define(‘FM_HOST’, ‘127.0.0.1’);

Trang 9

$message = ‘’;

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

Note that, here, we are now pointing the first parameter of the newEditCommand()at the Inventory layout and the setField()methods have been updated to be appropriate to

the Inventory table

$edit = $fm->newEditCommand(‘Inventory’, $_REQUEST[‘recid’]);

$edit->setField(‘Location’, $_POST[‘location’]);

$edit->setField(‘Quantity’, $_POST[‘quantity’]);

$edit->execute();

$message = ‘<p>Your changes have been saved</p>’;

}

Pointing at the Inventory layout in this getRecordById()method:

Pulling values for the fields of the Inventory table:

$location = $record->getField(‘Location’);

$quantity = $record->getField(‘Quantity’);

?>

The only significant change to the HTML section is that we are outputting fields appropri-ate to the table that we are working with

<html>

<head>

</head>

<body>

<?php echo $message; ?>

<input type=”hidden” name=”recid” value=”<?php $record->getRecordId(); ?>” />

<tr>

<th>Location</th>

<td><input type=”text” name=”location”

➥value=”<?php echo $location; ?>” /></td>

</tr>

<tr>

<th>Quantity</th>

Trang 10

<td><input type=”text” name=”quantity”

➥value=”<?php echo $quantity; ?>” /></td>

</tr>

</table>

</form>

</body>

</html>

Deleting a Related Record

I hate to sound like a broken record, but deleting a related record is exactly the same as deleting any other record That being the case, this example is going to be the same as the Delete Record example in Chapter 7 except that it will be pointed at an Inventory record instead of a Product record See Figure 8.17 for an example of the page displayed in a browser

FIGURE 8.17 When a user clicks the delete link on an inventory portal row, a confirmation page opens

<?php

define( ‘FM_HOST’, ‘127.0.0.1’ );

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

define( ‘FM_USER’, ‘esmith’ );

define( ‘FM_PASS’, ‘m4rg0t’ );

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

$page_content = ‘Are you sure you want to delete the ‘.$record->getField

➥(‘Location’).’ inventory record?’;

$page_content = ‘<form action=”08_05.php” method=”post”>’;

$page_content = ‘<input type=”hidden” name=”recid” value=”’.$record->

➥getRecordId().’” />’;

$page_content = ‘<p>’;

$page_content = ‘<input type=”submit” name=”action” value=”Delete” />’;

$page_content = ‘<input type=”submit” name=”action” value=”Cancel” />’;

$page_content = ‘</p>’;

Trang 11

$page_content = ‘</form>’;

} else {

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

$record->delete();

$page_content = ‘<p>Record was deleted.</p>’;

} else {

$page_content = ‘<p>Action cancelled Record was not deleted.</p>’;

}

?>

<html>

<head>

</head>

<body>

<?php echo $page_content; ?>

</body>

</html>

This page begins like all the others:

<?php

define( ‘FM_HOST’, ‘127.0.0.1’ );

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

define( ‘FM_USER’, ‘esmith’ );

define( ‘FM_PASS’, ‘m4rg0t’ );

Point the getRecordById()method at the Inventory layout:

If the actionelement of the $_POSTsuperglobal array has not been set, the user is viewing the page for the first time, so prompt the user to confirm the deletion and include Cancel and Delete buttons:

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

$page_content = ‘Are you sure you want to delete the ‘.$record->getField

➥(‘Location’).’ inventory record?’;

$page_content = ‘<form action=”08_05.php” method=”post”>’;

$page_content = ‘<input type=”hidden” name=”recid” value=”’.$record->

➥getRecordId().’” />’;

$page_content = ‘<p>’;

$page_content = ‘<input type=”submit” name=”action” value=”Delete” />’;

$page_content = ‘<input type=”submit” name=”action” value=”Cancel” />’;

$page_content = ‘</p>’;

$page_content = ‘</form>’;

Deleting a Related Record

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