Introduction

In the previous lesson, we enhanced our auction list by adding View, Edit, and Delete row actions beneath each Auction ID. Although these links improved the user interface, they were only placeholders.

In this lesson, we’ll make the Edit action functional by creating a dedicated Edit Auction page inside the WordPress administration area. Initially, this page will retrieve an auction from the database and display its existing information in a form. We’ll save the changes in the next lesson.

Breaking the workflow into two lessons makes it easier to understand and follows the same incremental approach we’ve used throughout this series.

Learning Objectives

By the end of this lesson, you’ll be able to:

• Build an Edit Auction administration page.
• Pass an auction ID through a URL.
• Retrieve a single auction from the database.
• Populate a form with existing values.
• Understand how editing workflows begin in WordPress plugins.

How the Workflow Changes

Our administration flow now becomes:

All Auctions
      ↓
Click Edit
      ↓
Edit Auction Page
      ↓
Retrieve Auction
      ↓
Display Existing Values

Notice that we’re still not saving changes yet. Today’s goal is to display the current data.

Step 1 – Update the Edit Row Action

Open:

admin/class-auctions-table.php

Locate the column_id() method.

Replace the Edit action with:

'edit' => sprintf(
	'<a href="%s">Edit</a>',
	admin_url(
		'admin.php?page=flipnzee-edit-auction&auction_id=' . absint( $item->id )
	)
),

Now every Edit link will open the correct auction.

Step 2 – Register a New Submenu

Open:

admin/class-admin.php

Inside register_menu(), add another submenu:

add_submenu_page(
	'flipnzee-auctions',
	'Edit Auction',
	'Edit Auction',
	'manage_options',
	'flipnzee-edit-auction',
	array( $this, 'edit_auction_page' )
);

This page won’t normally appear in the menu because administrators will access it through the Edit link.

Step 3 – Create the Edit Page

Inside class-admin.php, create:

public function edit_auction_page() {

	$auction_id = isset( $_GET['auction_id'] )
		? absint( $_GET['auction_id'] )
		: 0;

	$auction = Flipnzee_Auction_Manager::get_auction(
		$auction_id
	);

	if ( ! $auction ) {

		echo '<div class="notice notice-error"><p>Auction not found.</p></div>';

		return;
	}

	?>

	<div class="wrap">

		<h1>Edit Auction</h1>

		<p>The auction was loaded successfully.</p>

	</div>

	<?php
}

At this stage, we’re simply verifying that the selected auction can be retrieved.

Step 4 – Test the Plugin

Create a fresh ZIP.

Upload the plugin.

Navigate to:

Flipnzee Auctions → All Auctions

Click Edit beneath any auction.

If everything is working correctly, you’ll see:

Edit Auction

The auction was loaded successfully.

This confirms that:

• The row action works.
• The auction ID is passed correctly.
• The Auction Manager retrieves the correct record.
• The administration page loads successfully.

Why Stop Here?

Many beginners try to retrieve, display, validate, and save data in a single lesson.

Breaking the process into smaller steps makes debugging much easier.

Today we verify that the correct auction is loaded.

In the next lesson, we’ll build the complete editing form.

Lesson Summary

In this lesson, we transformed the placeholder Edit link into a working navigation path.

Administrators can now select an auction from the list, open an Edit Auction page, and retrieve the corresponding record from the database.

Although editing isn’t complete yet, we’ve successfully implemented the first half of the editing workflow.

Key Takeaways

• ✓ Row actions can pass record IDs through URLs.
• ✓ Retrieve individual records using the Auction Manager.
• ✓ Separate retrieval from saving.
• ✓ Build editing workflows incrementally.

Common Mistakes

• Forgetting to sanitize the auction ID.
• Accessing the database directly instead of using the Auction Manager.
• Assuming every ID exists.
• Trying to save changes before displaying the existing values.

Git Commands Used

git add .

git commit -m "Lesson 19: Create Edit Auction page"

git push

Testing Checklist

Before continuing:

• ✅ Plugin activates successfully.
• ✅ All Auctions page still loads.
• ✅ Every Edit link opens a new page.
• ✅ Correct auction ID is passed.
• ✅ Auction record is retrieved successfully.
• ✅ “Auction not found” appears only for invalid IDs.

Project Status

✅ Dashboard

✅ Add Auction

✅ Save Auctions

✅ View Auctions

✅ WP_List_Table

✅ Row Actions

✅ Edit Auction Page

⬜ Edit Auction Form

⬜ Save Edited Auction

⬜ Delete Auction

⬜ Bid Engine

⬜ Escrow Workflow

Project Evolution

With the introduction of the Edit Auction page, Flipnzee Auctions now supports navigation from a list of records to an individual record. This pattern is common in many WordPress plugins and content management systems. By retrieving a single auction before attempting to modify it, we’ve established a clean editing workflow that can be expanded safely in future lessons.

Developer’s Notebook

Professional applications rarely perform retrieval, validation, and persistence in one step. Separating these responsibilities improves readability, simplifies testing, and makes future enhancements much easier. Today’s lesson focuses entirely on retrieving the correct record, allowing the next lesson to concentrate solely on editing and saving changes.

Introduction

In the previous lesson, we created the first administration dashboard for Flipnzee Auctions. Although the dashboard displays useful plugin information, administrators still cannot create auctions.

In this lesson, we’ll build our first administration form.

Instead of inserting records directly into the database, administrators will be able to create auctions using the familiar WordPress Dashboard.

This marks an important milestone in the project because it connects our user interface to the database through the Auction Manager class.

Learning Objectives

By the end of this lesson, you’ll be able to:

• Create your first administration form.
• Submit form data securely.
• Insert auction records into the database.
• Use the Auction Manager class from the administration interface.
• Understand why business logic should remain separate from the user interface.

Our Architecture

Remember the design we’ve adopted throughout this project.

Administrator

        │

        ▼

Admin Form

        │

        ▼

Auction Manager

        │

        ▼

Database

Notice that the form never communicates directly with the database.

Instead, it delegates the work to the Auction Manager.

Why Not Use SQL Here?

Imagine writing SQL inside every administration page.

Soon your project would become difficult to maintain.

Instead:

• Forms collect information.
• Auction Manager performs the work.
• Database stores the results.

Each component has one responsibility.

Step 1 – Create a New Menu

Open:

admin/class-admin.php

Inside the register_menu() method, immediately below add_menu_page(), add:

add_submenu_page(
	'flipnzee-auctions',
	'Add Auction',
	'Add Auction',
	'manage_options',
	'flipnzee-add-auction',
	array( $this, 'add_auction_page' )
);

Step 2 – Create the Add Auction Page

Inside the class, add the following method.

public function add_auction_page() {

	?>

	<div class="wrap">

		<h1>Add Auction</h1>

		<form method="post">

			<table class="form-table">

				<tr>

					<th>Listing ID</th>

					<td>

						<input
							type="number"
							name="listing_id"
							min="1"
							required
						>

					</td>

				</tr>

				<tr>

					<th>Start Price</th>

					<td>

						<input
							type="number"
							step="0.01"
							name="start_price"
							required
						>

					</td>

				</tr>

				<tr>

					<th>Reserve Price</th>

					<td>

						<input
							type="number"
							step="0.01"
							name="reserve_price"
						>

					</td>

				</tr>

				<tr>

					<th>Buy Now Price</th>

					<td>

						<input
							type="number"
							step="0.01"
							name="buy_now_price"
						>

					</td>

				</tr>

			</table>

			<?php submit_button( 'Create Auction' ); ?>

		</form>

	</div>

	<?php
}

Step 3 – Why Listing ID?

Some readers may wonder why we’re asking for a Listing ID instead of a website title.

The answer is simple.

Website listings already belong to the Flipnzee Analytics plugin.

Rather than storing duplicate information, Flipnzee Auctions simply references the existing listing.

For now, we’ll enter the Listing ID manually.

Later in this series, we’ll replace this field with a dropdown that automatically displays verified listings from Flipnzee Analytics.

Step 4 – Upload the Plugin

Create a new ZIP.

Upload it.

Activate the plugin.

Open:

Flipnzee Auctions

↓

Add Auction

You should now see your first administration form.

Although the form doesn’t yet save data, we’ve successfully built the user interface.

We’ll connect it to the Auction Manager in the next lesson.

Lesson Summary

In this lesson, we created our first administration form for Flipnzee Auctions.

Rather than inserting data directly into the database, we focused on building a clean user interface that will soon communicate with the Auction Manager.

This layered approach keeps the plugin organized and prepares us for more advanced functionality.

Key Takeaways

• ✓ WordPress administration pages use standard HTML forms.
• ✓ Keep forms separate from database logic.
• ✓ Prepare for future integrations instead of duplicating data.
• ✓ Build one layer at a time.

Common Mistakes

• Writing SQL directly inside administration pages.
• Mixing business logic with HTML.
• Duplicating listing information.
• Building complicated forms before the backend is ready.

Git Commands Used

git add .

git commit -m "Lesson 11: Add Auction form"

git push

Project Status

✅ Development environment

✅ Plugin skeleton

✅ Plugin installation

✅ Plugin lifecycle

✅ .gitignore

✅ Data architecture

✅ Database table

✅ Auction Manager

✅ Retrieve auction records

✅ WordPress admin menu

✅ Plugin dashboard

✅ Add Auction page

⬜ Save auction

⬜ List auctions

⬜ Edit auctions

⬜ Bid engine

⬜ Escrow workflow

⬜ Website transfer

⬜ Version 1.0

Project Evolution

When we first planned this plugin, we considered storing all website information inside Flipnzee Auctions.

As the project evolved, we recognized that Flipnzee Analytics already provides verified website listings. Rather than duplicating that data, the auction plugin now references listings through a listing_id.

This architectural refinement keeps both plugins modular and easier to maintain while allowing them to work together as part of the broader Flipnzee ecosystem.

Developer’s Notebook

One of the biggest advantages of separating the user interface from the business logic is flexibility. Today we’re creating a simple administration form, but tomorrow the same Auction Manager methods could be called from REST APIs, AJAX requests, WP-CLI commands, or even another plugin. By keeping responsibilities separate, we avoid rewriting the core logic every time a new interface is introduced.

Looking Ahead

In Lesson 12, we’ll connect this form to the Auction Manager so that submitting it actually creates a new auction in the database. We’ll also introduce WordPress nonces to protect the form against unauthorized submissions, an essential security practice for professional plugin development.