form_multiselect()

form_multiselect([$name = ''[, $options = array()[, $selected = array()[, $extra = '']]]]) Parameters: $name (string) – Field name $options (array) – An associative array of options to be listed $selected (array) – List of fields to mark with the selected attribute $extra (mixed) – Extra attributes to be added to the tag either as an array or a literal string Returns: An HTML dropdown multiselect field tag Return type: string Lets you create a standard multiselect field. The firs

CI_Xmlrpc::display_error()

display_error() Returns: Error message string Return type: string Returns an error message as a string if your request failed for some reason. echo $this->xmlrpc->display_error();

CI_DB_result::num_rows()

num_rows() Returns: Number of rows in the result set Return type: int Returns the number of rows in the result set. Usage: see Result Helper Methods.

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., etc.) if you need this type of hierarchy. Views are never called directly, they must be loaded by a controller. Remember that in an MVC framework, the Controller acts as the traffic cop, so it is responsible for fetching a particular view. If you have not read the Controllers page you should do so before continuing. Using the

CI_User_agent::languages()

languages() Returns: An array list of accepted languages Return type: array Returns an array of languages supported by the user agent.

CI_Form_validation::error_array()

error_array() Returns: Array of error messages Return type: array Returns the error messages as an array.

Models

Models are optionally available for those who want to use a more traditional MVC approach. Page Contents ModelsWhat is a Model? Anatomy of a Model Loading a Model Auto-loading Models Connecting to your Database What is a Model? Models are PHP classes that are designed to work with information in your database. For example, let’s say you use CodeIgniter to manage a blog. You might have a model class that contains functions to insert, update, and retrieve your blog data. Here is an example of

CI_Session::unmark_temp()

unmark_temp($key) Parameters: $key (mixed) – Key to be un-marked as tempdata, or an array of multiple keys Return type: void Unmarks a $_SESSION item key (or multiple ones) as “tempdata”.

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 dynamic systems, CodeIgniter uses a segment-based approach: example.com/news/article/my_article Note Query string URLs can be optionally enabled, as described below. URI Segments The segments in the URL, in following with the Model-View-Controller approach, usually represent: example.com/class/function/ID The first segmen

Transactions

CodeIgniter’s database abstraction allows you to use transactions with databases that support transaction-safe table types. In MySQL, you’ll need to be running InnoDB or BDB table types rather than the more common MyISAM. Most other database platforms support transactions natively. If you are not familiar with transactions we recommend you find a good online resource to learn about them for your particular database. The information below assumes you have a basic understanding of transactions. C