When I saw this book at the local bookstore (one of only 10 PHP related books in stock), I thought, "Awesome! I've been looking for some more securing applications techniques." It turned out to be a big let down.
The book is roughtly 750 pages (large print), the first 50 or so was an introduction and gave a few bad examples vs. good examples of code (which was good, and actually made me think the rest of the book was going to be good), then jumped directly into "here's 650 pages worth of class based applications for you to use". The last 40-50 pages of the book was a chapter called something to the effect of "Optimizing and Securing PHP". Of the whole book, this was the most dissapointing aspect, split equally between the 2 topics. I thought the whole book was going to be about writing secure PHP, not just 20 pages.
Even the sample code they gave was in my opinion, poor. The author encouraged a strong misuse of OOP, having every single script have its own class dedicated to it. For example, one of the 50 "ready to use applications" was for handling users for their intranet. They wrote a class with methods for updating the user's information, adding a user, selecting the user's email address from the database, etc. The goal of OOP is to be abstract so that it can be used in more than one area, something the author didn't bother to learn before he wrote this book.
Even the optimizing portion of the last chapter was a big let down. It felt like there was really only one example of code optimization. The rest of the pages explained how to make a particular PEAR script do a speed test on your code. How is that supposed to help me if I'm not even certain how to write it more efficiently?
I'm not interested in a book that shovels me a bunch of code the author wrote. If I wanted free code, there's tons of sites out there for that. I want a book that's going to teach me how to think more securely and write more securely and think about the best/most optimized way to write a particular portion of code. Sadly, this book isn't it.