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

## Checking if the user has uploaded a picture
So far, providing a picture was optional.
What if we want to force the user to upload a picture?
We will have to cover two scenarios:

1. When the user is creating a new tour, we should verify that the user has uploaded a picture.
2. When the user is editing a tour, we should verify that the user has uploaded a picture before or that they are uploading a picture now.

Instead of implementing a similar check in two different files, let's make this part of the validation function we already have in `tour-crud.php`.
If `$normalizedData['picture']` is undefined, it means that the user didn't previously upload a picture, nor are they in the process of uploading one now.
So we can cover both scenarios with one `if` statement:


# Checking if the user has uploaded a picture
So far, providing a picture was optional.
What if we want to force the user to upload a picture?
We will have to cover two scenarios:

1. When the user is creating a new tour, we should verify that the user has uploaded a picture.
2. When the user is editing a tour, we should verify that the user has uploaded a picture before or that they are uploading a picture now.

Instead of implementing a similar check in two different files, let's make this part of the validation function we already have in `tour-crud.php`.
If `$normalizedData['picture']` is undefined, it means that the user didn't previously upload a picture, nor are they in the process of uploading one now.
So we can cover both scenarios with one `if` statement:


# Checking if the user has uploaded a picture
So far, providing a picture was optional.
What if we want to force the user to upload a picture?
We will have to cover two scenarios:

1. When the user is creating a new tour, we should verify that the user has uploaded a picture.
2. When the user is editing a tour, we should verify that the user has uploaded a picture before or that they are uploading a picture now.

Instead of implementing a similar check in two different files, let's make this part of the validation function we already have in `tour-crud.php`.
If `＄normalizedData['picture']` is undefined, it means that the user didn't previously upload a picture, nor are they in the process of uploading one now.
So we can cover both scenarios with one `if` statement:


Let's learn how to validate file uploads. 

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

Form Validation for File Uploads

Checking if the user has uploaded a picture