Design and Architectural Goals Our goal for CodeIgniter is maximum performance, capability, and flexibility in the smallest, lightest possible package. To meet this goal we are committed to benchmarking, re-factoring, and simplifying at every step of the development process, rejecting anything that doesn’t further the stated objective. From a technical and architectural standpoint, CodeIgniter was created with the following objectives: Dynamic Instantiation.  In CodeIgniter, components are loaded and routines executed only when requested, rather than globally. No assumptions are made by the system regarding what may be needed beyond the minimal core resources, so the system is very light-weight by default. The events, as triggered by the HTTP request, and the controllers and views you design will determine what is invoked. Loose Coupling.  Coupling is the degree to which components of a system rely on each other. The less components depend on each other the more reusabl...

  Model-View-Controller CodeIgniter is based on the Model-View-Controller development pattern. MVC is a software approach that separates application logic from presentation. In practice, it permits your web pages to contain minimal scripting since the presentation is separate from the PHP scripting. The  Model  represents your data structures. Typically your model classes will contain functions that help you retrieve, insert, and update information in your database. The  View  is the information that is being presented to a user. A View will normally be a web page, but in CodeIgniter, a view can also be a page fragment like a header or footer. It can also be an RSS page, or any other type of “page”. The  Controller  serves as an  intermediary  between the Model, the View, and any other resources needed to process the HTTP request and generate a web page. CodeIgniter has a fairly loose approach to MVC since Models are not required. If you don’...

Application Flow Chart The index.php serves as the front controller, initializing the base resources needed to run CodeIgniter. The Router examines the HTTP request to determine what should be done with it. If a cache file exists, it is sent directly to the browser, bypassing the normal system execution. Security. Before the application controller is loaded, the HTTP request and any user submitted data is filtered for security. The Controller loads the model, core libraries, helpers, and any other resources needed to process the specific request. The finalized View is rendered then sent to the web browser to be seen. If caching is enabled, the view is cached first so that on subsequent requests it can be served. https://codeigniter.com/userguide3/overview/appflow.html

GitHub Git  is a distributed version control system. Public Git access is available at  GitHub . Please note that while every effort is made to keep this code base functional, we cannot guarantee the functionality of code taken from the develop branch. Beginning with version 2.0.3, stable versions are also available via  GitHub Releases . Click here to Download  or  https://codeload.github.com/bcit-ci/CodeIgniter/zip/3.1.13

  Installation Instructions CodeIgniter is installed in four steps: Unzip the package. Upload the CodeIgniter folders and files to your server. Normally the  index.php  file will be at your root. Open the  application/config/config.php  file with a text editor and set your base URL. If you intend to use encryption or sessions, set your encryption key. If you intend to use a database, open the  application/config/database.php  file with a text editor and set your database settings. If you wish to increase security by hiding the location of your CodeIgniter files you can rename the system and application folders to something more private. If you do rename them, you must open your main  index.php  file and set the  $system_path  and  $application_folder  variables at the top of the file with the new name you’ve chosen. For the best security, both the system and any application folders should be placed above web root so that t...

codeigniter Controller and How to open in browser  <? php class Blog extends CI_Controller { public function index () { echo 'Hello World!' ; } public function comments () { echo 'Look at this!' ; } } Load in browser example . com / index . php / blog / example . com / index . php / blog /comments https://codeigniter.com/userguide3/general/controllers.html

Load Library  $this -> load -> library ( 'session' ); Set data in  session $this -> session -> set_userdata ( 'some_name' , 'some_value' ); Get data session $data= $this -> session -> some_name