Codignator Development

CodeIgniter Overview
CodeIgniter is a powerful PHP framework with a very small footprint, built for developers who need a simple and elegant toolkit to create full-featured web applications.
CodeIgniter was created by EllisLab, and is now a project of the British Columbia Institute of Technology.

This tutorial has been prepared for developers who would like to learn the art of developing websites using CodeIgniter.
It provides a complete understanding of this framework.

Supported Databases
– MySQL (5.1+) via the mysql (deprecated), mysqli and pdo drivers
– Oracle via the oci8 and pdo drivers
– PostgreSQL via the postgre and pdo drivers
– MS SQL via the mssql, sqlsrv (version 2005 and above only) and pdo drivers
– SQLite via the sqlite (version 2), sqlite3 (version 3) and pdo drivers
– CUBRID via the cubrid and pdo drivers
– Interbase/Firebird via the ibase and pdo drivers
– ODBC via the odbc and pdo drivers (you should know that ODBC is actually an abstraction layer)

CodeIgniter was originally developed by Rick Ellis (CEO of EllisLab, Inc.).
The framework was written for performance in the real world, with many of the class libraries, helpers, and sub-systems borrowed from the code-base of ExpressionEngine.
A hat tip goes to Ruby on Rails for inspiring us to create a PHP framework, and for bringing frameworks into the general consciousness of the web community.

Contributing to CodeIgniter
CodeIgniter is a community driven project and accepts contributions of code and documentation from the community.
These contributions are made in the form of Issues or Pull Requests on the CodeIgniter repository on GitHub.
Issues are a quick way to point out a bug. If you find a bug or documentation error in CodeIgniter then please check a few things first:
There is not already an open Issue
The issue has already been fixed (check the develop branch, or look for closed Issues)
Is it something really obvious that you fix it yourself?

Did you find a security issue in CodeIgniter?
Please don’t disclose it publicly, but e-mail us at, or report it via our page on HackerOne.
If you’ve found a critical vulnerability, we’d be happy to credit you in our ChangeLog <../changelog>.