Summary

This chapter has reviewed the handling of the inevitable errors that go with software systems. Errors arising out of PHP code make up one important area, and database errors another. The special case of an invalid URI causing a "404 error" was taken into consideration. Situations where a "403 error" is appropriate were reviewed, arising when a request is not permitted.

We've devised mechanisms for dealing with all of them, usually recording a good deal of information, including an execution trace, to the database for diagnosis by a developer. By contrast, the user is given only a modest amount of information, so that they know that an error has happened. This is a choice based on avoiding confusion and also on securing the system from hostile interventions.

With a well featured framework in place, our final chapter will move on to discussion of the many types of content that could make use of it.