Handling Multiple Environments

Developers often desire different system behavior depending on whether an application is running in a development or production environment. For example, verbose error output

2016-10-15 16:32:24
Models

Models are optionally available for those who want to use a more traditional MVC approach. Page Contents

2016-10-15 16:32:30
Profiling Your Application

The Profiler Class will display benchmark results, queries you have run, and $_POST data at the bottom of your pages. This information can be useful during development

2016-10-15 16:32:34
Views

A view is simply a web page, or a page fragment, like a header, footer, sidebar, etc. In fact, views can flexibly be embedded within other views (within other views, etc.,

2016-10-15 16:32:46
PHP Style Guide

The following page describes the coding styles adhered to when contributing to the development of CodeIgniter. There is no requirement to use these styles in your own CodeIgniter

2016-10-15 16:32:33
CodeIgniter URLs

By default, URLs in CodeIgniter are designed to be search-engine and human friendly. Rather than using the standard “query string” approach to URLs that is synonymous with

2016-10-15 16:32:10
Creating Drivers

Driver Directory and File Structure Sample driver directory and file structure layout:

2016-10-15 16:32:12
Using CodeIgniter Libraries

All of the available libraries are located in your system/libraries/ directory. In most cases, to use one of these classes involves initializing it within a

2016-10-15 16:32:46
Creating Libraries

When we use the term “Libraries” we are normally referring to the classes that are located in the libraries directory and described in the Class Reference of this user guide

2016-10-15 16:32:12
Web Page Caching

CodeIgniter lets you cache your pages in order to achieve maximum performance. Although CodeIgniter is quite fast, the amount of dynamic information

2016-10-15 16:32:47