2. Who am I?
⢠Author of programmersvoice.com
⢠AG Auth - Easiest Auth Library for CI
⢠AG Asset - simple Asset Management Library
⢠Author of CodeIgniter 1.7 Professional Development
3. CodeIgniter 2.0.0
⢠Whatâs been removed
⢠Whatâs been deprecated
⢠Whatâs changed
⢠Whatâs new
⢠Tips for upgrading
5. Goodbye Scaffolding
⢠Deprecated for a number of versions
⢠Wasnât a very good implementation
⢠Has now been removed for CodeIgniter 2.0.0
6. Au revoir Plugins
⢠Removed in favour of Helpers
⢠Nobody was ever sure what they were for
⢠Plugins & Helpers were too similar
⢠You should update your Plugins to Helpers
9. PHP 4
⢠Support now dropped for PHP 4
⢠YAY!!
⢠New CI 2 features may not support PHP 4
⢠All legacy features will no longer support PHP 4 as of 2.1.0
11. Application Directory
⢠How many of you move your application directory out of the
system directory?
⢠That wonât be an issue in CI2
12. index.php
⢠Configuration values can now be stored here.
⢠Allows a single application to have multiple front controllers
with different configuration values.
⢠Routing overrides now added.
⢠Limits your application to one controller.
39. Packages
⢠Allows for easy distribution of resources in a single directory.
⢠Can have itâs own library files, models, config files etc.
⢠Placed in application/third_party
⢠MojoMotor addons are packages
50. Add Package Path
⢠Before you can load a package, you need to tell the Loader
where to look for it.
⢠$this->load-
>add_package_path(APPPATH.'third_party/package_name/');
⢠$this->load->library(âpackage_nameâ);
51. Remove Package Path
⢠When finished using a Packages resources.
⢠When you want to use multiple Packages.
⢠$this->load-
>remove_package_path(APPPATH.'third_party/package_nam
e/');
52. PackageView Files
⢠Disclaimer: not finished
⢠Save the original view path
⢠Set the view path to that of the Package
⢠Load views, etc
⢠Set the path back to the original
53. // ... save the original view path, and set to our package view folder
$orig_view_path = $this->load->_ci_view_path;$this->load->_ci_view_path = APPPATH.'third_party/package_name/views/';// ... code using the package's view files// ... then return the view path to the application's original view path$this->load->_ci_view_path = $orig_view_path;
$orig_view_path = $this->load->_ci_view_path;$this->load->_ci_view_path = APPPATH.'third_party/package_name/views/';// ... code using the package's view files// ... then return the view path to the application's original view path$this->load->_ci_view_path = $orig_view_path;
$orig_view_path = $this->load->_ci_view_path;$this->load->_ci_view_path = APPPATH.'third_party/package_name/views/';// ... code using the package's view files// ... then return the view path to the application's original view path$this->load->_ci_view_path = $orig_view_path;
54. Mercurial/BitBucket
⢠In development code is now hosted on BitBucket
⢠Easier to get *your* code in the CI core
⢠Allows community to help squish bugs
⢠No SVN!! (Sorry but I really do hate Subversion)
60. Upgrading your Models
⢠CodeIgniter 1.7.2 Models extend Model
⢠CodeIgniter 2.0.0 Models extend CI_Model
61. Lazy mans Model Upgrade
⢠Create a new Library file: MY_Model.php
<?php
class Model extends CI_Model
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
62. Lazy mans Model Upgrade
⢠Create a new Library file: MY_Model.php
<?php
class Model extends CI_Model
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
63. Lazy mans Model Upgrade
⢠Create a new Library file: MY_Model.php
<?php
class Model extends CI_Model
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
64. Lazy mans Model Upgrade
⢠Create a new Library file: MY_Model.php
<?php
class Model extends CI_Model
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
65. Controllers
⢠Controllers are currently unchanged
⢠Ellis Lab are evaluating changing the Controller class from
Controller to CI_Controller
66. Lazy mans Controller Upgrade
⢠Create a new Library file: MY_Controller.php
<?php
class Controller extends CI_Controller
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
67. Lazy mans Controller Upgrade
⢠Create a new Library file: MY_Controller.php
<?php
class Controller extends CI_Controller
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
68. Lazy mans Controller Upgrade
⢠Create a new Library file: MY_Controller.php
<?php
class Controller extends CI_Controller
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
69. Lazy mans Controller Upgrade
⢠Create a new Library file: MY_Controller.php
<?php
class Controller extends CI_Controller
{
function __construct()
{
parent::__construct();
} // construct()
} // class
?>
70. Summary
⢠Plugins,Validation Library & Scaffolding have been removed
⢠PHP 4 support dropped
⢠Drivers & Packages
⢠Model Class renamed
⢠Mercurial/Bitbucket
Hello, Iâm going to be talking to you today about CodeIgniter 2, the in development version of CodeIgniter. My name is Adam Griffiths and before I dive into my talk I wanted to go through who I am and why you should listen to me!
Ok so Iâm Adam Griffiths. I created and authored all of the tutorials on Programmers Voice. This was a hugely popular CodeIgniter focussed tutorial blog where I posted tutorials, articles and screencasts on CodeIgniter and supplementary subjects such as jQuery and Git.
I am the guy behind AG Auth, quite possibly the eaisest Authentication Library for CodeIgniter, just extend a new Controller class to get a full authentication system with admin panel!
I also created AG Asset, another simple library that enables you to manage your CSS files, images and script files and provides an easy way to pre-load CSS and JavaScript if you have a lot of files to include.
Finally I am the author of CodeIgniter 1.7 Professional Development, the first advanced book on CodeIgniter covering topics such as User Authentication, Twitter oAuth, Facebook Connect, Web Services and REST, and a neat little chapter with ym tips on releasing code to the community.
On with the talk. So, CodeIgniter 2. Itâs a bit of a jump from 1.7.2. In this talk Iâm going to take you though all of the things that have been removed (and what you should use in itâs place), everything thatâs now deprecated. Weâll also look at all the changes in CodeIgniter 2 and finally all the new goodies we get to play with.
Iâll also give you a few tips for upgrading your projects to CodeIgniter 2.
Goodbye Scaffolding. Scaffolding was a way to easily create records in your database, kind of like a mini PHPMyAdmin. But it wasnât a very good implementation. You would set a scaffolding key and turn it on in your controllers, but if somebody knew your key they could easily start to mess around with your data if you didnât turn it off on a production server. Scaffolding has now been removed for CodeIgniter 2.0.0.
Au revoir plugins. Now I didnât really expect plugins to be removed without first being deprecated, but Iâm not all that surprised itâs been removed either. Plugins have been removed in favour of helpers, and now many people knew what plugins were for. I know that plugins were supposed to be community created and be single purpose, they should have only one function in them. Helpers were supposed to be created by EllisLab and be more official and multi-purpose. But people used the two interchangably as they were extremely similar to each other. So if youâre still using plugins you should update these to be helpers.
The Validation Class has also been removed after being deprecated since v 1.7.0. Version 1.7.0 saw the Form Validation Class being added to the framework in place of the Validation Class. Therefore you should use the more powerful Form Validation Class.
PHP 4! There have been numerous forum posts, tweets, blog posts and I have even had a few emails asking when CodeIgniter was going to drop support for PHP 4. Ellis Lab have always said they will only drop support for PHP 4 when the user base becomes small enough that when the change occurs theyâre not putting a considerable amount of developers out in the cold. New CodeIgniter 2 features may not support PHP 4, it might work but nobody cares. All legacy features will no longer have support for PHP 4 as of 2.1.0.
Ok so a quick show of hands. How many of us here move the application directory out of the system directory before starting a project?
This wonât be an issue in CI 2 as the application directory now exists in the top level alongside the system folder and the index.php front controller. I know itâs never been exactly hard to move the application directory, you literally just move it, no need to edit any settings but Ellis Lab have obviously seen that a lot of people do this anyway, and itâs always good to have clear separation so in CodeIgniter 2, weâll be able to just jump into the code rather than spend (albeit a minute) time moving directories.
Ok so onto the index.php front controller. Nothing major has been changed here but thereâs a few things you might like to know.
You can now store configuration values in this file. This allows you to share one application between multiple front controllers using different configuration values.
Routing overrides have now been added to this file as well. This allows you to set your default controller in this file rather than your routes.php configuration file. However, using this method will limit your application to one controller, although you will still be able to call different functions in that controller.
Ok so now weâre getting into the good stuff. So whatâs new?
Weâll kick this section off with a biggy. Drivers.
Drivers are a new type of library with CodeIgniter 2.0.0. They allow you to have a parent class with any number of child classes. Children can access functions of their parent, but not their siblings. An example of a library that would take advantage of this new type of library is the Database Library.
Ellis Lab have now started to host their in-development code on BitBucket, the github for mercurial hosting. Mercurial is a distributed version control system much like git.
This is good for a few reasons. Firstly itâs easier to get your own code in the CodeIgniter core. Whereas it was possible before itâs much easier to issue a pull request than the older channels. It also allows the community to help squish bugs, and in a few cases a community member has been given responsibility for a few support tickets.
And finally, no subversion!! I really hate SVN, so this is the best thing for me!! :)