PLUSES
The book is very well organized in 24 chapters that are supposed to take roughly one hour each to cover. While the earlier chapters take no more than 20 minutes or so, the later ones may take a little more than one hour if you actually intend to "digest" their contents. On average, I guess it takes you about an hour per chapter.
The coverage of PHP also seems to be quite good (although I am not an advanced programmer and therefore cannot not be totally sure about that). I can't think of anything I might one day like to do with PHP that I didn't find somewhere in the book. True enough, locating this information is not always very easy, but with a little effort you'll end up finding it.
Finally, the layout is not only appealing but also makes the book easy to use.
MINUSES
The blurb on the back cover is a bit too ambitious: it promises you'll "learn how to ... setup a secure PHP environment ... create dynamic charts and graphics on your web pages ... create dynamic web applications using PHP." Well, I guess you might if you read the book four or five times and spent lots of time studying each chapter. Otherwise, I don't think you'll be going quite so far.
While the author writes clearly enough, he sometimes uses a string of technical terms that you're supposed to have memorized. Problem is, sometimes you don't remember them all, and if the context doesn't help, you get lost. Take this sentence as an example: "When you pass arguments to functions they are stored as copies in parameter variables." I had to go back to several different pages to remind myself what the difference between "parameters" and "arguments" was, and also what the heck "parameter variables" was supposed to mean. I think sometimes the author assumes that you'll remember every single new term that is introduced, and he'll be using them to introduce yet another new term in a couple of pages. For programmers with some previous experience that may be okay, but not for novices like me.
Some of the explanations of important new concepts are just barely mentioned in the text and then actually introduced in an example. However, most of the examples consist of a chunk of code without any mention as to what this code will output to the browser or file or whatever, so you just have to guess what will come out as a result. Now, if you're still trying to understand what a particular chunk of code will do, it would help to see what it would result in. More screenshots of code output to a browser, for example, would have helped a lot.
There are also quite a few misprints: double closing parentheses where there should only be one, misplaced line numbers in the middle of the code, etc. Misprints in text are not so serious, because you understand the "code" (i.e. the language) well enough that you can make sense out of it. But misprints in the PHP code that you're trying to learn can be very confusing. All of a sudden you find this "10:" in the middle of a line of code, and by the time you've figured out that it's the number of the next line that has somehow wound up in the middle of the previous line, you've wasted ten minutes of your time.

