<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Tue, 22 May 2012 14:32:47 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Phil Sturgeon's Blog: CodeIgniter Base Classes: Keeping it DRY]]></title>
      <guid>http://www.phpdeveloper.org/news/14009</guid>
      <link>http://www.phpdeveloper.org/news/14009</link>
      <description><![CDATA[<p>
In a new post to his blog <i>Phil Sturgeon</i> looks at <a href="http://philsturgeon.co.uk/news/2010/02/CodeIgniter-Base-Classes-Keeping-it-DRY">creating sharable code</a> for your controllers in a <a href="http://codeigniter.com">CodeIgniter</a> application (DRY: Don't Repeat Yourself).
</p>
<blockquote>
The idea is that most of your controllers share something in common with each other. For example: All admin controllers need to make sure a logged in user is present and that they are an administrator. A public controller may want to load a theme for your application and load default user data, navigation links or anything else frontend related.
</blockquote>
<p>
The problem is solved by creating a base controller - in his example its one called MY_Controller that follows the CodeIgniter naming convention and allows you to easily make other controllers that extend it. You'll also need to make a small addition to your config.php file to get the base controllers working correctly and make them able to be found.
</p>]]></description>
      <pubDate>Thu, 11 Feb 2010 09:46:51 -0600</pubDate>
    </item>
  </channel>
</rss>

