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

## Static resources and their limitations
Previously, we looked at serving static resources, in particular `index.html` and `favicon.ico`.
These are the things a browser can deal with: it can show an HTML page and use the `favicon.ico` as a visual icon inside the browser tab.

However, if all we could do was return `.html` files and images to the browser, we could never build an actual web application.
A `.html` file can't do the following: 
* It cannot process data that a user provides by filling in a form.
* It cannot talk to a database and produce a list of available products.
* It cannot remember that it’s me and say “Hey Matthias, welcome back!”. 

This is due to the  `.html` file being a static resource. If the browser fetches it the second time, it will be the same file as when it fetched it the first time.



# Static resources and their limitations
Previously, we looked at serving static resources, in particular `index.html` and `favicon.ico`.
These are the things a browser can deal with: it can show an HTML page and use the `favicon.ico` as a visual icon inside the browser tab.

However, if all we could do was return `.html` files and images to the browser, we could never build an actual web application.
A `.html` file can't do the following: 
* It cannot process data that a user provides by filling in a form.
* It cannot talk to a database and produce a list of available products.
* It cannot remember that it’s me and say “Hey Matthias, welcome back!”. 

This is due to the  `.html` file being a static resource. If the browser fetches it the second time, it will be the same file as when it fetched it the first time.



Learn how to create and serve dynamic resources.

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

Dynamic Resources

Static resources and their limitations