Slashdot Mirror

← Back to Stories (view on slashdot.org)

Recommended Reading List for PHP

Posted by ryuzaki0 on from the i'm-told-that's-a-popular-drug dept.

Steve writes "IBM developerWorks has put together a PHP recommended reading list. It provides resources for developers and admins adopting PHP and tackling advanced topics such as building extensions and writing secure code. There's also a list of books and blogs for keeping up with changes to the language itself."

4 of 128 comments (clear)

  1. ISBN-13 is upon us! by XanC · · Score: 2, Informative

    978-0-13-147149-8

  2. Templating systems by Spy+der+Mann · · Score: 2, Informative

    This one's an ABSOLUTELY MUST-READ for those who don't know what template engines are:

    http://www.sitepoint.com/article/beyond-template-e ngine

  3. 5 good PHP sites by Anthony+Boyd · · Score: 5, Informative

    Their list is great -- I'll be reading some of those articles for weeks before I get through them all. I'm especially interested in the 7 security blunders article. Nice!

    But they did leave off a lot of sites that are useful. Here are a few:

    • PHP Resource Index - a few thousand scripts for downloading, most free, all PHP.
    • PHP Builder Forums -- the PHP Builder site is pretty useful all by itself, but in the forums there are thousands of people willing to answer your PHP questions.
    • PHP Freaks -- one of the guys behind this site wrote a great PHP book. The site is excellent.
    • ADOdb Database Abstraction Layer -- okay, okay, this isn't really a site, so much as a product. But still, it's a very efficient DBAL, and it should be used for every database query.

    Anyone want to pitch in with some more? I'm sure there are some very useful sites that I've completely missed (and which the IBM site missed, too).

    --
    My Greasemonkey scripts for Digg &
  4. Re:Nooo!!!! by Craig+Maloney · · Score: 3, Informative

    The reason people find PHP so insecure is because you can plop a script practically anywhere on the server, and have it run. So, if one of the scripts allows someone to upload somewhere where they shouldn't, BAM, you're compromised.

    I've found this out first-hand with a few PHP scripts I've run. It's amazingly easy to set up, but it's also a discipline in itself to ensure it keeps crackers out.