The companion downloads extend your practice without making the printed book depend on a web interface or framework that keeps changing. Every exercise and project in this book can be completed with nothing more than PHP and a text editor.
Every file here is free. There is no sign-up, and no email address is asked for.
-
Core syntax and operators on a compact printable reference: program basics, variables and types, conversion, strings, arithmetic, comparison, decisions, match, loops, functions, string handling, indexed arrays, array transformation, and associative arrays.
-
JSON, Sessions, PDO, and Exceptions Quick Reference
The four boundaries where a PHP program meets stored data, on one sheet: JSON encoding and decoding, small-file persistence, session handling, PDO connections and prepared statements, reading rows, exceptions, the errors you meet, and the password API.
-
Request Validation and HTML Output Checklist
One printable page to work down before a form page meets a real visitor: reading the request, validating meaning, trust boundaries, escaping at the output boundary, the states a page has to have, and the inputs to test it with.
-
One printable page to work through before you change a line: what to check before you run, how to read a PHP message, what to do when the program runs and the answer is wrong, and what to verify before calling it finished.
-
Common PHP Errors and Warnings
Forty real PHP messages in roughly the order a beginner meets them, each with what it means, what to check first, and the smallest program that produces it.
-
Three or four questions per chapter across all fourteen chapters, weighted toward tracing, debugging, and building from a blank file, with answers complete enough to check yourself against.
-
Thirty mixed questions covering the whole book in four parts: predict the output, find and fix the defect, short answer, and write the code. Answers are included.
-
Clean files for the four Chapter 14 projects, with the function names the chapter uses, TODO comments keyed to the build milestones, a README carrying the requirements and acceptance tests, JSON fixture data, a server-side catalog, and an empty SQL schema. They run as they stand; they are not solutions.