Any good non-beginner php books?

how about http://www.hotscripts.com

yes, Wrox the better one

is the wrox book strong on objects? I've already written a couple of portal sites. I know that I can get lots of information from php.net about individual functions and I have the New Riders Paul Dubois MySQL book which is excellent.
I'm really looking to increase my efficiency so that I don't have to rewrite the same code over and over and it seems that OOP is the way to go for that.

Wrox Professional PHP Programming doesn't talk much about object ;-/

check it out
http://www.amazon.com/exec/obidos/ASIN/0735709971/qid=992290796/sr=1-3/ref=sc_b_3/104-3866026-3223161

Web Application Development with PHP 4.0 by Tobias and Till...  They spend an entire chapter or five diving into deep topics including OOP (and they even get philisophical on when to bother using this approach).

jasendorf : then what have i said......

I didn't know, sorry.  Amazon was down when I was looking through these.  Maybe put the title with your post next time so it's not reliant on another site.  I haven't memorized all of the ISBN numbers of the books I have yet  :)

The wrox book seems good. And it seems that OOP is slowish (according to article in Zend) on php so that side isn't a priority - perhaps a comment rather than a proposed answer would be better here :-)

Wrox seem also to have a new php book out - have you seen it?

I don't mean to be too rude here, but you asked for "a book that is strong on OOP and assumes that I have a reasonable php knowledge, and is not of the type "how to make a shopping cart" mySQL coverage is irrelevant."

Now you've changed your question.  And although I agree that the Wrox books are good (particularly PHP Programming), they don't satisfy your original question as well as Web Application Development by Tobias and Till.  I suppose I could have listed every book in my library here (hell, I could have even thrown in Mastering Regular Expressions and McGraw Hill's PHP3 Programming Browser Based Applications) and hoped that you found one of those titles interesting.  Instead I gave you a definitive answer to the question you asked, which it appears you didn't even give a second look (that is unless you bought the book in the following 24 hours and read it or already own it).

I'll know better next time.  If someone asks for "a" book, give them five.  If someone asks for a book "strong on OOP", they don't really want to know about OOP.  And above all, don't actually propose an answer to a question, just piddlef**k around with comments and sling them against the wall and hope that something sticks.

From my point of view, your 'proposed answer' was the same as the previous comment - I am aware that you weren't to know that. Regarding answers versus comments: I tend to think that an answer should be used in a case where this solves a specific problem - a difference in perspective I suppose.

I got the points somehow!

Thanks!