Overview
Title: Professional CodeIgniter
Author: Thomas Myer
336 pages (paperback)
Publisher: Wrox (July 28, 2008)
Language: English
ISBN-10: 0470282452
ISBN-13: 978-0470282458
Description of book and excerpts on Publisher’s Website
Modular Extensions makes CodeIgniter modular. Modules are groups of independent CI components (typically, model, controller, view arranged in one application sub-directory) that can be dropped into CodeIgniter applications. HMVC stands for Hierarchical Model View Controller, which is a fancy way of saying nested modules!
Module Controllers can be used as normal Controllers or HMVC Controllers and they can be used to help you build view partials.
1) Start with a clean CI install.
2) Set $config[’base_url’] correctly for your installation.
3) Access the URL domain/subdir/index.php/welcome => shows Welcome to CodeIgniter
4) Drop Modular Extensions libraries into application/libraries and application/helpers directories as specified.
5) Access the URL domain/subdir/index.php/welcome => shows Welcome to CodeIgniter
6) Create module directory structure application/modules/welcome/controllers.
7) Move controller application/controllers/welcome.php to application/modules/welcome/controllers/welcome.php.
8) Access the URL domain/subdir/index.php/welcome => shows Welcome to CodeIgniter
9) Create directory application/modules/welcome/views.
10) Move view application/views/welcome_message.php to application/modules/welcome/views/welcome_message.php
11) Access the URL domain/subdir/index.php/welcome => shows Welcome to CodeIgniter
You now have a running Modular Extensions installation.
Installation Guide Hints:
-Steps 1-3 tell you how to get a standard CI install working - if you have a clean/tested CI install, skip to step 4.
-Steps 4-5 show that normal CI still works after installing ME - it shouldn’t interfere with the normal CI setup.
-Steps 6-8 show ME working alongside CI - controller moved to the ME “welcome” module, the view file remains in the CI application/views directory - ME can find module resources in several places, including the application directory.
-Steps 9-11 show ME working with both controller and view in “welcome” module - there should be no files in the application/controllers or application/views directories.
Q. What are modules, why should I use them?
A. http://en.wikipedia.org/wiki/Module
Q. What is Modular HMVC, why should I use it?
A. Modular HMVC = Multiple MVC triads
This is most useful when you need to load a view and its data within a view. Think about adding a shopping cart to a page. The shopping cart needs its own controller which may call a model to get cart data. Then the controller needs to load the data into a view. So instead of the main controller handling the page and the shopping cart, the shopping cart MVC can be loaded directly in the page. The main controller doesn’t need to know about it, and is totally isolated from it.
In CI we can’t call more than 1 controller per request. Therefore, to achieve HMVC, we have to simulate controllers. It can be done with libraries, or with this “Modular Extensions HMVC” contribution.
The differences between using a library and a “Modular HMVC” HMVC class is:
1) No need to get and use the CI instance within an HMVC class
2) HMVC classes are stored in a modules directory as opposed to the libraries directory.
Q. Is Modular Extensions HMVC the same as Matchbox?
A. Yes and No. Like Matchbox, ME makes modules “portable” to other installations. For example, if you make a nice self-contained model-controller-view set of files you can bring that MVC into another project by copying just one folder - everything is in one place instead of spread around model, view and controller folders.
ME is different from Matchbox because you can nest those modules. So, from another controller, you can get some of the nice output from the original, tidy MVC set without calling a controller via URI (i.e., another http call using file_get_contents() or curl). You can get controller output without having to go out through the http interface again.
Modular HMVC means modular MVC triads. Matchbox and Modular Extensions allows related controllers, models, libraries, views, etc. to be grouped together in module directories and used like a mini application. But, ME goes one step further and allows those modules to “talk” to each other.
Note:
You can find more FAQ at the wiki page Modular Extensions - FAQ
All controllers can contain an $autoload class variable, which holds an array of items to load prior to running the constructor. This can be used instead of module/config/autoload.php, however using the file takes precedence over the class variable.
Modules::run() output is buffered, so any data returned or output directly from the controller is caught and returned to the caller. In particular, $this->load->view() can be used as you would in a normal controller, without the need for return.
Controllers can be loaded as class variables of other controllers using $this->load->module(’module/controller’); or simply
$this->load->module(’module’); if the controller name matches the module name.
Any loaded module controller can then be used like a library, ie: $this->module_controller->do_stuff(), but it has access to its own models and libraries independently from the caller.
Module controllers can have independent methods, located in a module/methods directory, these methods act as libraries extending their parent controller and have access to the parent controller features.
Loading a method is achieved from a module controller by using $this->load->method(’method’); or from a view by using modules:run(), if the method name is not defined in the controller then the method subclass will be loaded and its own index() method will be called, however if the controller actually has the method, it will be called as normal.
Controllers also have a instance() method that can be used instead of get_instance() in libraries and helpers etc.
ie: $ci = controller::instance();
Of course all module controllers are accessible from the URL via module/controller/method or simply module/method if the module and controller names match.
However if you add the _remap() method to your controllers you can prevent unwanted access to them and redirect or flag an error as you like.
Download new version 4.2: File:modular extensions 4206.zip
Note: Version 4.2 is not backward compatible with version 4.0
Your modules output will be buffered by the modules::run() function and the explicit return used in earlier versions is no longer required.
Using a Module as a view partial from within a view is as easy as writing:
<?php echo modules::run('module', $data, 'method') ?>
The $data and ‘method’ above are optional. The default method is index.
Using language files
application/modules/home/language/home_lang.php
Put this in your controller-file:
$this->load->language('home');
On your view-file:
<?php echo $this->lang->line('name');?>
If you want to specify the language of the language-file you are going to use, you can alter the first line in something like:
$this->load->language('home','english');
Using debug
The debug_helper has two debug methods you might like to look at.
debug($any_object); will display the $any_object and list its loaded libraries, using $this will display the current module.
debug_in($any_object) or debug_in($any_array) will do a full dump on the subject.
NOTE:
If you debug_in() the CodeIgniter Core ($CI), you will get a page full of recursive arrays. This is not an issue because most of the recursions are only references back into $CI core objects.
Do not use the MY_Controller extension in your application/libraries directory. This will cause CodeIgniter to bypass loading Modular Extensions and modules will not function. If you need to run methods in a base controller define them in another module controller and use the controller autoload functionality.
MY_ prefixed resources are not loaded by ME when they are inside the module directory (e.g., MY_directory_helper.php is not loaded when it is in the modulename/helpers directory). This is because ME doesn’t check for MY_ extensions in modules. To get new functionality using helpers, plugins, models, etc… either make a new named file and load that resource or put your MY_ prefixed resource up in the requisite application directory (helpers for a MY_ helper, libraries for a MY_ library, etc...).
NOTE:
Do you get notices or error-messages? You might want to have a look at the wiki page
Modular Extensions - Notices and errors as well.
Spanish User Guide (1.6.3) in both PDF and HTML - http://www.conocimientovirtual.edu.co/descargas.html
Chinese User Guide (1.6.3) in HTML(Wiki) - http://codeigniter.org.cn/user_guide
For changes between different versions see: Language Changes
- BRAZILIAN / PORTUGUESE (UTF-8)Português Brasil (translation: Matheus Bombonato, utf-8 encoding: Marcelo Oliveira)
- BRAZILIAN / PORTUGUESE Português Brasil (Matheus Bombonato)
- CROATIAN Hrvatski 1.6.2 (Zoran Vucinic)
- CZECH (UTF8), version 1.6.2 (bretik)
- GALICIAN http://www.derekallard.com/img/post_resources/galician1_6_1.zip
- FRENCH CI_1.6.3_french_metalking.zip (metalking - html accents)
- FRENCH 1.6.3_french_tomcode.zip (tomcode)
- FRENCH 1.6.2_french_tomcode.zip (tomcode)
- FRENCH 1.6.1_french_tomcode.zip (tomcode)
- GERMAN 1.6.3_german_tomcode.zip (tomcode)
- GERMAN 1.6.2_german_tomcode.zip (tomcode)
- GERMAN 1.6.1_german_tomcode.zip (tomcode)
- HUNGARIAN File:hungarian163.zip (Thoer), (1.6.3)
- ITALIAN http://www.rollcage.it/external/codeigniter/italian_1.6.zip (gyo)
- PERSIAN http://www.kishmate.com/CodeIgniter/language/1.6.3_persian.zip (Borzoo Mossavari)
- PERSIAN http://www.kishmate.com/CodeIgniter/language/1.6.2_persian.zip (Borzoo Mossavari)
- RUSSIAN http://rmcreative.ru/files/translations/ci_russian_163.zip (Alexei Shulga / Alexander ‘Sam Dark’ Makarov)
- SPANISH Version 1.6.3 (Miguel Herrero)
- SPANISH http://www.derekallard.com/img/post_resources/spanish_1_6_1.zip (ReynierPM, fdog)
- SWEDISH http://www.derekallard.com/blog/post/swedish-language-pack-for-codeigniter-16/ (Mikael Johansson)
- TURKISH File:turkish 163 utf8.zip (Fatih BAZMAN / fatigue (1.6.3)), (Note: UTF8 Encoded)
- BULGARIAN http://www.derekallard.com/img/post_resources/bulgarian.zip
- CHINESE chinese for 1.5.4 (by speedu)
- DANISH Danish language pack (1.5.4) (daath, Zacharias)
http://mirror.ordo.dk/codeigniter.com/danish_1.5.x.zip (daath, Zacharias)
- DUTCH Updated Dutch translations
WARNING! The php-files all end with an empty code after the ‘?>’ They could give a ‘header already sent’ error.
- FRENCH http://codeigniter.nouvelle-aire.net/ (mEga)
french translation (all new - accents fixed) (metalking.net)
ci_v1.5_lang_french_corr.zip (tomcode), (Note: fixed one left accent in db_lang.php of metalking’s version)
- GALICIAN http://www.derekallard.com/img/post_resources/galician1_5_3.zip
- GERMAN File:ci GermanTranslations 1.5.4.zip (UnrealMinds), (Note: umlauts as html entities)
File:codeigniter language german.zip (ArtemisX), (Note: umlauts as html entities)
http://www.berndmatzner.de/codeigniter/ci_lang_german_1.5.1.zip (bmatzner), (Note: including Sentry language file)
- ITALIAN http://www.rollcage.it/external/codeigniter/italian_1.5.zip (gyo)
- JAPANESE http://www.cilab.info/data/japanese_translations1.5.zip
Japanese version user guide is also available at: http://userguide.cilab.info/
- ROMANIAN http://www.derekallard.com/img/post_resources/romanian.zip (Marius Visan)
- SPANISH http://www.derekallard.com/img/post_resources/spanish_1.5.x.zip (ReynierPM)
http://www.tractores.co.cr/spanish_1.6.x.zip
- TURKISH File:turkish 153 utf8.zip (M.Musa Ülker - musaulker), (Note: UTF8 Encoded)
File:turkish 153 windows1254.zip (M.Musa Ülker - musaulker), (Note: Windows-1254 Encoded)
- FRENCH http://codeigniter.nouvelle-aire.net/ (mEga)
- SPANISH http://www.derekallard.com/img/post_resources/spanish_1.4.x.zip (ReynierPM)
- CHINESE http://my.opera.com/yarco/homes/blog/chinese.tar.gz (by yarco)
- GERMAN http://tomcode.com/inside/codeigniter/zips/ci_german_translations_1.3.3_v1.zip (tomcode)
- POLISH http://prdownloads.sourceforge.net/rkcmf/polish_code_igniter.zip?download (riklaunim, groadin)
- SPANISH http://www.semjanelas.net/codeigniter/ci_spanish_1.3.3.zip (ReynierPM)
- ITALIAN http://www.rollcage.it/external/codeigniter/italian_1.3.zip (gyo)
]]>
FreakAuth
CI drop-in authentification system.
Classroombookings
Room booking system for schools.
MyFina
Web-based personal financial management system.
68 Knowledge Base
68KB is a knowledge base script. It was built with the site owner in mind and to be as simple to work with as possible.
Linkster, PHP Link Directory
Growing out of a need for simple categorical organization, Linkster aims to be the simple solution. Specifically built for link directories, such as a collection of your business partners. Demo available here.
MaxSite CMS
WordPress-like blog CMS. In heavy development. Documentation is in Russian only for now.
Planet CI
Planet CI is a Feed/RSS agregator reader using PHP. Its similar to planetplanet but its on perl langguage. Planet CI using codeigniter and simple pie. you can se the demo at planet.ilkom.org.
BlogFrog blog aggegate service
MindZinger is mainly a question-answer site for students and tutors. Also it has a section that is pretty similar to hotornot.com, and a forum (based on phpbb2), etc. Registration is free. All created on top of a plain code igniter installation by www.pengekcs.com - you can reach me on yahoo at pengekcs [at] yahoo [dot] com
BambooInvoice is free open-source invoicing software intended for small businesses and independent contractors. code is available Also see this forum thread.
Motortopia. A motor enthusiast social networking site focused on peoples passion for motor vehicles. Site features Web 2.0 interface, cross-browser compatability, degradability, accessability and web standards compliance.
ToDlaCiebie.pl - website built entirely with CI, collects best gift ideas from Polish e-shops (’to dla ciebie’ means ‘this is for you’).
Nuherbs.com - Chinese herbs and medicine site built in CI. Has product ordering and full account access.
PeterBaker.net - Portfolio for the photographer, built in CI and using jquery for some effects.
Snowshoe Conditions - A site for people to check back-country snow conditions before heading out for the day, everything is user-submitted.
Creatieve-Cursussen.nl - Dutch website listing creative courses. Also uses Jquery and a google maps api class.
BritCaster.com - An aggregator and hub for podcasts - UK focused. Generates aggregated RSS feeds for serialised content and a unique custom keyword RSS creator (FeedMe!).
Sign-Up-Sheet - Super simple web based sign-up-sheet program.
BadgeTracker - A web app, built using CI, that handles activity registration and camp management for summer camps.
Classroombookings. An open-source easy to use web-based room booking system for schools.
Zoekipedia. Dutch Wikipedia searchengine. build in CI 1.5.2 Project from Auke Jongbloed and under constant development.
Webacana. Brazilian movie rental service (like Netflix). build in CI 1.5.1 Project from Jesse Jr and under constant development too.
More Chevrolet. Auto dealer site build completely with Code Igniter, with full administrative and CMS.
Reggae Planet, Metal Town, Punk Space. Polish e-shops for reggae, metal and punk music fans.
Gayticketshop.nl - Dutch webshop for ordering tickets for (gay) parties and events. Built and maintained in latest CI version.
Solid.lt. Lithuanian hosting provider.
WebHostNinja.com. Price and feature comparison for web hosting.
Music News Generator - lets you generate music release news code (BB-Code, XHTML code and any other) for blogs, forums etc. using data recieved from Discogs and Last.fm music community sites.
morel cornnery. a project Meeting site based on CI 1.5.4 from dakar senegal .
Franchise Bean. An online resource for franchise companies that allows to set up profiles and generate leads.
Digital Design a website built on CI 1.4.1, jquery js/ajax library and some google api flavour. Still under construction. They plan to release the source when they are done.
Interlink Airlines Still under construction, due for release soon. Complete rewrite of Airline booking system + admin facility + major features upgrade.
GranitiWorld - Just a personal site about Graniti, Italy.
Lovetech - Personal website. Started Dec 06. Heading for commerical cms. Or for charity. Or both. Still practicing, Finland.
SLVouge - Web Site for an already active Second Life Fashion Magazine. Not yet finished and still in development.
overfood.com - The site currently features a restaurant search of the Chefmoz database with restaurants mapped using Google Maps. The search uses xajax for an autocomplete when searching by city. It also uses the mootools accordion effect to switch between search types.
Mobilu.lt. Lithuanian site. It’s cell phones classifieds system. Built on CI 1.5.3. Uses a little bit of XAJAX library.
Blog System. An Indonesian CMS Blog, will release the source when it have done.
Prodotti Tipici - Vendita online di prodotti tipici | Italian special alimentar products e-Commerce
Party Ideas and Party Planning - at bestpartyever.com - CI,1.6.1
Rumah Sakit Ciranjang - Ciranjang Hospital Website. Based on CI 1.6
Dik’s Photography - Indonesian Photographer Website. Based on CI 1.5
SpicY Web+Design - Website based on CI 1.5
Network Artisan - UK catering supplier based on CI 1.5.
422 South - VFX House website based on CI 1.5
Michel-Ange Kuntz - Photo blog - Built using CI 1.5. Back-office : “Partikule CMS” based on CI 1.5.
Wissam Joubran website - Wissam Joubran luthier web site. Front-end based on Code Igniter. Back-office : “Partikule CMS” based on Code Igniter.
Aleksandra Sheybal & Family - first version of private family website (it’s still growing with features - if it’s too small - please remove it from list ;-))
Thomas Welsh Builders, LLC Built using CI 1.5, has property management backend and more - 100% CI!
c7 mobile blog - Personal moblog, updated to Code Igniter over one evening.
BrownieTheCow.org - School testing activist web site. All Code Igniter (front and backend) and a bit of jQuery.
Wissahickon Restoration Volunteers - Environmental group / member-supported, volunteer-driven nonprofit. All CI.
www.theclientele.co.uk - web site for the band ‘the clientele’ (merge records).
pipasforthepeople.com - band web site. tour dates, blog stuff and the rest of the site all done with CI.
Pixels and Code, LLC - Forward-thinking web design and development
Systematix Computer Training - UK commercial training website rewritten in CI 1.5.1
Jongbloed MultiMedia. Home of Dutch Freelance webdeveloper Auke Jongbloed. Front and back-end build in CI 1.5.2 using mootools for effects.
Club 3D . Graphics and Multimedia card company. Front and back-end build in CI 1.5.2 extended with Xajax library.
MonPatelin.fr. French website of local classifieds.
RMCreative. Sam Dark’s custom blog written from scratch with CI.
Lirikita. Lyric and video download written from scratch with CI.
Scholl. Shoes and foot care company - polish version written from scratch with CI.
]]>
Title: Professional CodeIgniter
Author: Thomas Myer
336 pages (paperback)
Publisher: Wrox (July 28, 2008)
Language: English
ISBN-10: 0470282452
ISBN-13: 978-0470282458
Description of book and excerpts on Publisher’s Website
Title: CodeIgniter for Rapid PHP Application Development
Author: David Upton
220 pages (Paperback)
Publisher: Packt Publishing (July 23, 2007)
Language: English
ISBN-10: 1847191746
ISBN-13: 978-1847191748
http://www.packtpub.com/codeigniter-php-application-development-mvc/book
Amazon
PHPClasses
Derek Allard’s Blog
(Post your review here...)
]]>Create a page for each book and post your reviews to the according page.
]]>
Q: What does the abbreviation ME stand for?
A: In forum threads and the wiki ME is used as a abbreviation for Modular Extensions.
Q: How can I load a module from within a view?
A: Put the following line in your view file
<?php echo modules::run('MODULE', $data, 'METHOD') ?>
Explanation:
MODULE = The name of the module you want to use (required). Example: ‘blog’
$DATA = The data which will be available in the method. This can be either a string or an array. (optional)
METHOD = The controller->method you want to use. The default method is index. (optional). Example: ‘blog_read’
You may return a value as the output of a module controller or you can output a view or simply use echo, because the output is buffered and returned it can be used as needed.
Example:
<?php
class Blog extends Controller {
function blog()
{
parent::Controller();
}
function blog_read($id)
{
$data['title'] = 'Title '. $id;
$this->load->view('blog_read',$data); //return is NOT required for views.
return $some_data; //return CAN be used if needed.
}
}
Q: How can I load a model in a controller of a module?
A: Take the following code as an example:
// Loading a model
$this->load->model('mymodelname');
// Using a model
$this->mymodelname->function();
mymodelname = The name of the model you want to load.
function = The function of the model you want to use.
The model can be stored in the application folder (system/application/models/mymodelname.php) or in the models folder of a module (system/application/modules/mymodule/models/mymodelname.php)
Q: How can I make a difference between the front-end and the back-end (admin) of my web application?
A: There are more roads leading to Rome. One of your opportunities is to make two applications. But before you do this, you might want to split the application part and the system part of CodeIgniter as described at the wikipage Better Server Setup for CI first. In the coming step-by-step plan I will however reference to CodeIgniter as it comes out of the box.
1) Go to your ‘system’ directory.
2) Copy the directory ‘application’, but paste it into the same directory. In Microsoft Windows Explorer your mapstructure will become like:
- CodeIngiter_1_6_3
- system (dir)
- application (dir)
- cache (dir)
- codeigniter (dir)
- database (dir)
- fonts (dir)
- helpers (dir)
- language (dir)
- libraries (dir)
- logs (dir)
- plugins (dir)
- scaffolding (dir)
- copy of application (dir)
- user_guide (dir)
- index.php
3) Rename the directory ‘copy of application’ and call it backend.
4) Rename the directory ‘application’ and call it frontend.
5) Create a new folder in the CodeIgniter_1_6_3 directory. For example: ‘myadmin’.
6) Copy the index.php file into ‘myadmin’.
7) Open CodeIngiter_1_6_3/index.php to change the application_folder variable (line 44) and give it the name of your frontend. In this example: $application_folder = “frontend”;
8) Open CodeIngiter_1_6_3/myadin/index.php to change the system_folder variable (line 26) and update the system folder location. In this example: $system_folder = “../system”;
9) Open CodeIngiter_1_6_3/myadin/index.php to change the application_folder variable (line 44) and give it the name of your backend. In this example: $application_folder = “backend”;
I noticed my view files get confusing because of all the little checks that have to be made when displaying values. For example
// data
array(
array('start_date'=>'2008-01-01','total'=>'10'),
array('start_date'=>'0000-00-00','total'=>'0')
);
// view
<?php foreach($rows as $row): ?>
<tr>
<td><?php if($row['start_date'] != '0000-00-00') echo $row['start_date'] ?></td>
<td><?php if($row['total'] != '0') echo $row['start_date'] ?></td>
</tr>
<?php endforeach ?>
This is why i created the display helper.
Code
The code is split up in two parts. There are constants and there is the display_helper.php file
The constants are added to the config/constants.php files and make it easier for you to change the default value where ever you used it.
/*
| -----------------------------------------------------------------------
| Defaults
| -----------------------------------------------------------------------
*/
define('DEFAULT_DATETIME', '0000-00-00 00:00:00');
define('DEFAULT_DATETIME_NO_SEC', '0000-00-00 00:00');
define('DEFAULT_DATE', '0000-00-00');
define('DEFAULT_TIME', '00:00:00');
define('DEFAULT_NUMBER', '0');
Add as many constants as you need.
The display_helper.php file contains the functions used in the view file
/*
| ----------------------------
| show value if it's not the same as the default value
| ----------------------------
*/
function display($value,$default,$replacement = NULL)
{
return ($value == $default)?(( ! is_null($replacement))?$replacement:''):$value;
}
/*
| ----------------------------
| check if value is (not) the same as the default value
| ----------------------------
*/
function is_default($value,$default)
{
return ($value == $default)?TRUE:FALSE;
}
/*
| ----------------------------
| show value or a formatted string with the value in it when the value exists
| ----------------------------
*/
function display_isset($value,$str='')
{
if( ! isset($value))
{
return '';
}
if($str != '')
{
return sprintf($str,$value);
}
return $value;
}
It are only a few functions but they make view files a lot easier to read.
Usage
The example view code with the helper is
<?php foreach($rows as $row): ?>
<tr>
<td><?php echo display($row['start_date'],'0000-00-00') ?></td>
<td><?php echo display($row['total'],'0') ?></td>
</tr>
<?php endforeach ?>
// or with the constants
<?php foreach($rows as $row): ?>
<tr>
<td><?php echo display($row['start_date'],DEFAULT_DATE) ?></td>
<td><?php echo display($row['total'],DEFAULT_NUMBER) ?></td>
</tr>
<?php endforeach ?>
An example of the display_isset function
// without helper
<p<?php if(isset($class)): ' class="'.$class.'"'; endif ?>>hello world</p>
// with helper
<p<?php echo display_isset($class,' class="%s"') ?>>hello world</p>
Updates
29-08-2008 : added replacement parameter to display function. Usage ;
display($row['start_date'],DEFAULT_DATE,date('Y-m-d'))
]]>
The changes below is to version 5 of ME.
Add this method to the Controller class (which resides in libraries/Controller.php):
/**
* Loads the IgnitedRecord class and the Model class, also acts as a wrapper for Loader::model().
*
* This enables an other way to instantiate IgnitedRecord's child classes:
* @code
* $this->load->ORM();
* $this->load->model('a_child_class');
* // or as a wrapper for model()
* $this->load->ORM('a_child_class','pages');
* @endcode
*
* @param $model The model name of the model to load, if false ORM() will not load any derived classes (models)
* @param $name The name parameter is passed to the model() function, determining if the property name should differ from the default
* @param $db_conn The database connection passed to the model() function
*/
function ORM($model = false, $name = FALSE, $db_conn = FALSE){
if(!class_exists('IgnitedRecord'))
{
// change this line if the IgnitedRecord file is stored elsewhere
require_once(APPPATH.'models/ignitedrecord/ignitedrecord.php');
}
if($model != false)
{
$this->model($model,$name,$db_conn);
}
}
In the model() method of the Controller class, you have to add this, right before the return statement:
$CI =& get_instance();
if( ! isset($CI->$_alias))
{
$CI->$_alias = $this->$_alias;
}
The code below assigns the models correctly, so IgnitedRecord can find them.
]]>When linking to your files, you should provide a title for the link simply stating the version for which the translation has been done in the format “Version x.x.x” (without the quotes). After the link, you can optionally state the name of the translator in the format “translated by author” (without the quotes, and with your name instead of “author").
Now, you can either upload your archive right here on the wiki, in which case you are going to use the following code
[File:file.zip|Version x.x.x] translated by author
Alternatively, if you’ve uploaded the file somewhere else, do like this
[url=http://example.com/file.zip]Version x.x.x[/url] translated by author
Most of the time, what people will be looking for is CodeIgniter language packs and thus we should position those at the top.
Some nationalities might be in the fortunate situation of having the user guide translated into their language, so this should be the second set of links.
At the bottom of the article, the category should be placed. That way, other users can see the article when viewing the language contributions category.
When the article is done, it the markup should look somewhat like this
[b]CodeIgniter language packs[/b]
[quote]
[File:file.zip|Version x.x.x] translated by author
[File:file.zip|Version x.x.x] translated by author
[/quote]
[b]User Guide translations[/b]
[quote]
None available.
[/quote]
[[Category:Contributions::Languages]]
]]>