Book Image

CodeIgniter 1.7

Book Image

CodeIgniter 1.7

Overview of this book

CodeIgniter (CI) is a powerful open-source PHP framework with a very small footprint, built for PHP coders who need a simple and elegant toolkit to create full-featured web applications. CodeIgniter is an MVC framework, similar in some ways to the Rails framework for Ruby, and is designed to enable, not overwhelm. This book explains how to work with CodeIgniter in a clear logical way. It is not a detailed guide to the syntax of CodeIgniter, but makes an ideal complement to the existing online CodeIgniter user guide, helping you grasp the bigger picture and bringing together many ideas to get your application development started as smoothly as possible. This book will start you from the basics, installing CodeIgniter, understanding its structure and the MVC pattern. You will also learn how to use some of the most important CodeIgniter libraries and helpers, upload it to a shared server, and take care of the most common problems. If you are new to CodeIgniter, this book will guide you from bottom to top. If you are an experienced developer or already know about CodeIgniter, here you will find ideas and code examples to compare to your own.
Table of Contents (21 chapters)
CodeIgniter 1.7
Credits
About the Authors
About the Reviewer
Preface

Errors and error pages


While developing, it is a good idea to see programming errors that really help us. But it may not be a good idea letting our visitors to see those errors, for example, a missing semicolon would end up showing the following screen to our visitor:

While this helps you, you need to refrain from showing this to your visitors. Open your index.php file and find this line in it:

error_reporting(E_ALL);

Change it, or better comment it and add:

error_reporting(0);

Now, after uploading the file, no errors will be shown any more. But other errors such as "404 Page Not Found", will require some tweaking. We will try to make them more useful for our visitors, for example, if they try to load a non-existent controller they will see this screen:

This is of no help to our visitors. If we want to help them in case they reach that error page, we need to modify the application/errors/error_404.php file. When we open it we will see something like this:

<?php header("HTTP/1.1 404 Not...