Gain insights into modern PHP by delving into POST requests, forms, sessions, and redirects to build a CRUD app with authentication, focusing on pure PHP without frameworks.

Learn PHP Without a Framework by Matthias Noback.png

php-setup.tar.gz

php-job

php-favi

php-pub

php-public

php-error

php-mult

php-tests

PHP for the Web is a terrific introduction on how to use modern PHP effectively. While there is a lot of material out there about building applications with PHP, most of them focus on using a framework like Laravel or Symfony. By working with pure PHP, you will be able to focus on the core ideas instead of how a particular framework implements them.

In this course, you will learn how to use multiple web technologies like POST requests, forms, sessions, and redirects to build a CRUD application with an authentication system.

By the end, you will have all the ingredients at your disposal to go out and build stunning, dynamic PHP web applications.

PHP for the Web: Learn PHP without a Framework

# Problem statement
This challenge builds on top of the previous one, so we will continue to work on the project that we have already created. 

**Next steps:**

- Split the existing `/tasks` page in a `/list-tasks` page and a `/create-task` page. The form goes to the `/create-task` page, and the list of previously created tasks goes to `/list-tasks`. Both pages need to be accessible only when you are logged in. 
- On the `/create-task` page, when the request method is `POST`, start by normalizing the submitted data and validating it. For now, the only validation rule is that the task can't be an empty string. When form validation fails, show an error next to the `task` form field.
- Instead of storing the tasks in the session, we are going to store the tasks in a JSON file called `data/tasks.json`. A new task should be stored as an array: `['username' => $_SESSION['authenticated_user'], 'task' => $normalizedData['task']]`. After saving, redirect the user to `/list-tasks`.
- Now that tasks are stored in `tasks.json`, the `/list-tasks` page should load the tasks from this file and show them. Make sure that you only show the tasks of the currently logged in user! This is one way to accomplish that:


# Problem statement
This challenge builds on top of the previous one, so we will continue to work on the project that we have already created. 

**Next steps:**

- Split the existing `/tasks` page in a `/list-tasks` page and a `/create-task` page. The form goes to the `/create-task` page, and the list of previously created tasks goes to `/list-tasks`. Both pages need to be accessible only when you are logged in. 
- On the `/create-task` page, when the request method is `POST`, start by normalizing the submitted data and validating it. For now, the only validation rule is that the task can't be an empty string. When form validation fails, show an error next to the `task` form field.
- Instead of storing the tasks in the session, we are going to store the tasks in a JSON file called `data/tasks.json`. A new task should be stored as an array: `['username' => ＄_SESSION['authenticated_user'], 'task' => ＄normalizedData['task']]`. After saving, redirect the user to `/list-tasks`.
- Now that tasks are stored in `tasks.json`, the `/list-tasks` page should load the tasks from this file and show them. Make sure that you only show the tasks of the currently logged in user! This is one way to accomplish that:


Let's implement the features we recently learned in the previous project. 

Getting Started

Serving Resources

Serving PHP Scripts

Forms

Cookies

Sessions

Authentication

PHP Project Structure

CRUD Part 1: Create

CRUD Part 2: The Rest

File Uploads

Error Handling

Automated Testing

Conclusion

Project Challenge: Create and List Tasks

Problem statement