php[architect]

by Clay Loveless

Imagine a world in which you work harmoniously with other developers, never fearing that your code changes will overwrite theirs—or worse, that their changes will overwrite yours. A world where all of your modifications are backed up, and where you can always perform an “undo” operation when your code tweaks take a turn for the worse. Sound like a dream come true? Welcome to the Subversion-managed life.

by Martin Psinas

In need of a very simple gallery application to host your images? Look no further! Author Martin Psinas explains the entire process of creating a drop-in gallery script that is extremely simple to deploy.

by Simone Grassi

If you've ever developed a robust administration system to allow your users to manage their own content, you've probably also needed a permissions system to govern privileges. Simone Grassi and Bernhard Gaul have teamed up to help you along the path, by describing their own permissions system.

by Jason Sweat

You have probably heard a lot about Design Patterns--a technique that helps you design rock-solid solutions to practical problems that programmers everywhere encounter in their day-to-day work. Even though there has been a lot of buzz, however, no-one has yet come up with a comprehensive resource on design patterns for PHP developers---until today. In this excerpt from Jason E. Sweat's book php|architect's Guide to PHP Design Patterns, you'll learn about the Iterator pattern, whether custom-built, or with PHP 5's new Standard PHP Library.

by Marcus Baker

Your classes are your nouns and your methods are your verbs. The rule certainly is easy to apply, as you can just underline all of the nouns and verbs in your requirements docu-ment. There, object oriented design is easy! You are probably wondering what all of the fuss is about when such a simple rule is available. Columnist Marcus Baker dispels your assumptions.

by Ben Ramsey

This year has seen an increased focus on PHP security, and this is good for the language, developers, and business community. One phrase that comes to mind when discussing secure coding practices is Chris Shiflett’s mantra of “filter input, escape output.” While we know what this means in a general sense, practical examples elude us. Ben Ramsey provides part one of his input filtering series, chock full of code examples.

by Chris Shiflett

As a language, PHP is often criticized for the shortcomings of its developers. Of course, those of us within the community know that these criticisms have little merit. Rather than bemoan the ignorance of the naysayers, however, Chris Shiflett discusses "theory," an important characteristic of the web application security discipline, as it relates to developing secure PHP applications.