CodeIgniter for Beginners: Build a Complete Web Application

Learn how an MVC framework like CodeIgniter is different to "plain" PHP, and how controllers work to send content to the browser.

Learn how view files are used within the framework to contain the presentation code, and how to display them from a controller.

Add another controller to display a list of articles.

How to deal with changes to the routing configuration file from version 4.4.0 onwards.

Learn how the framework executes action methods in controllers using the router.

Learn a technique for showing multiple views by calling the view method multiple times from the controller.

Learn another technique for showing multiple views by including one view partial inside another.

Learn how to pass data to a view from a controller's action method.

Extract common view code out into a view layout file, reducing code repetition.

Inherit the content from the view layout by extending it.

Inherit the content from the view layout by extending it in the articles index view too.

Pass article data from a controller to a view to display more than static data in the view.

Add the necessary configuration settings to the framework to connect to the database.

A simple way to check if the database connection credentials are correct before continuing.

Learn how database migrations are used to edit the database structure from code, and write the code to create a table in the database to store articles.

Run the migration to create the table in the database, and how to reverse it by rolling it back.

How model classes are configured and used to interact with the database and retrieve data.

How to enable the debugging bar and how to use the dd function to aid development.

Add a method containing an ID and retrieve this value from the URL via a route.

Retrieve an individual record from the database automatically using the model.

Use the site_url function to create portable URLs for links between pages.

Add a page that will contain a form for getting the data for a new record.

Use the form helper to create a form and include HTML input elements to get data from the user.

Include a stylesheet that doesn't require any changes to the HTML content.

Process the form when it's submitted, getting the data from the request.

Use the model class to insert the data automatically without writing any SQL.

Add validation rules to the model to automatically validate the form data.

Display the validation error messages in the form when data aren't valid.

Show the original data in the input fields in the form when it's redisplayed.

Configure the model with different validation messages.

Add a flash message when redirecting back to the show page when the data are valid.

Escape untrusted input when it's displayed to avoid code injection attacks.

Add a page with a route for editing the data of an existing record, showing the existing data in the form controls.

Use the model to update the record when the form is submitted, via a route that uses the POST method.

Create a shared view containing the common form code to remove duplication.

Create an entity class whose objects will represent a single row from the database.

Configure the model class to return entity objects instead of arrays, and use these in the view templates.

Pass an entity object to the model when saving instead of an array of data.

Use the entity class to detect if any data have been changed in the form.

Create the model instance in the constructor of the controller to avoid repetition.

Use a CodeIgniter exception to show a 404 page when the ID of the supplied record doesn't exist in the database.

Add a page to ask for confirmation when deleting a record from the database.

Use the same action method for different HTTP methods, checking the method to decide on the action.

Only match routes when a specified HTTP method is used.

Using URI segments to route automatically without adding specific routes, including the advantages and disadvantages of doing this.

How to specify a name for a route and using it in a view.

Spoof an unsupported HTTP method with a specific hidden field in the form.

Convert some of the existing routes to be RESTful.

Convert the delete route to be RESTful.

Generate the RESTful resource routes automatically in the routes configuration file.

Install the official CodeIgniter Shield package using Composer.

Use the Shield package to register a new user, and log them in and out.

Configure the framework and package to optionally remember or forget the login between sessions.

Find an SMTP server and configure the framework to use it.

Send a test email to check that the SMTP server works from the framework.

Allow users to log in from a magic login link sent to their email if they have forgotten their password.

Require the user to activate their account after registering before they can login.

Customise the registration form to remove the requirement for the username.

Remove the validation for the username when a new user registers.

Add a first name input field to the registration form along with server-side validation.

Use a migration to add a first name column to the users table in the database.

Create and customise a user model class to include the first name when creating a user.

Use the first name property to show this field on the homepage when the user logs in.

Add a page with a form and a route for the user to input a new password.

Add server-side validation for the password reset page and process the form when it's submitted.

Use the user model to update the password in the database.

Redirect to the set password page after logging in using a magic login link.

Add a self-contained code module to hold all the code relating to user administration.

Add a routes config file inside the admin module for routes specific to that module.

Add an index view to list all the registered user accounts.

Use the pagination library to automatically paginate the list of user records on the user index page.

Use a migration to add an index to the created_at field of the database table so it can be used to order the results for pagination.

Add a page to show the details of an individual user record.

Look at different ways to specify the routes in a namespace.

Use the time and date library to display the date in a more readable format.

Add a helper to the admin module and use it to display boolean values in a more readable format.

Enable the banning of users using Shield in the admin module so that a banned user can't login.