postpostmodern

<p>Churro is a plugin that allows developers to easily create pages and functionality, in a style similar to CodeIgniter.  By itself, Churro will not add any functionality to your WordPress site.</p>
<p>Tested with WordPress and WordPress MU 2.8.0 ~ 3.0.5<br />
Requires PHP 5.  PHP 4 is like 10 years old, you know?</p>
<h3>Churro Basics</h3>
<p>= URLs =<br />
Churro requires friendly urls rather than query strings.  Your url will usually be mapped as following: <code>yoursite.com/class/method/variables</code></p>
<h4>Controllers</h4>
<p>The controller will be directly mapped to a file and class with the same name.  For example,<br />
        yoursite.com/contact<br />
will look for a file named contact.php in the /churro/ directory.  This file should have a class contact that extends Churro.  Without a defined method, it will default to index.  All methods accessible through URLs will have ‘Action’ appended to it.  The following code will provide scaffolding for <code>yoursite.com/contact</code> and <code>yoursite.com/contact/submit</code></p>
<pre><code><?php
class contact extends Churro {
    public function indexAction(){

    }

    public function submitAction(){

    }
}
</code></pre>
<h4>Models</h4>
<p>Churro gives you access to several important WordPress Models through the <code>$this</code> keyword.  The <code>$wp</code>, <code>$wpdb</code>, and <code>$wp_query</code> classes, as well as <code>$blog_id</code> in MU are all availble without using the global keyword, eg <code>$this->wpdb</code>.</p>
<h4>Views</h4>
<p>Your views belong in your normal theme directory.  If you are using multiple themes, you can override the direcotry using <code>$this->Theme( 'directory-name' )</code> any place in the controller.  To specify a view to use, <code>$this->View( 'file-name' )</code>.  Seperating logic from  views is the most important thing to remember in Churro.  To set varaibles in your view, use <code>$this->vars->var_name</code> in the controller, and <code>$var_name</code> in your view.</p>
<h4>Ajax / Javascript</h4>
<p>If you use the excellent jQuery javascript library, Churro will detect ajax requests and automatically return JSON.  Churro defines a constant <code>ISAJAX</code> on each request.  With a little planning, it is very easy to create a dynamic application in a way that is totally accessible without javascript.</p>
<h3>Learning Churro</h3>
<p>There is much more functionality in Churro than outlined here.  As of September 2, 2009, there is no complete, formal, documentation for writing code with Churro.  Stay tuned to <a href="http://labs.findsubstance.com/" title="The passionate voice for interactive brand strategy and creative experiences" rel="nofollow ugc">Substance Labs</a> for tutorials.</p>


Churro

dynamodan

<p>A WordPress plugin that integrates CodeIgniter</p>
<p>Why a CodeIgniter/Wordpress integration plugin?</p>
<ol>
<li>
<p>I (along with many others) like CodeIgniter for it’s features such as ActiveRecord and MVC disciplines, plus I have a ton of cool libs and stuff in CodeIgniter that I would like to use in the WordPress environment</p>
</li>
<li>
<p>I’m getting tired of building custom user, login, and session management systems for CodeIgniter. WordPress has them already.</p>
</li>
<li>
<p>I’m getting tired of building custom look and feel and templates for CodeIgniter, WordPress already is that, and has thousands of themes available.</p>
</li>
<li>
<p>I’m getting tired of building custom feature X for CodeIgniter, when it may already exist in WordPress either natively or as a plugin.</p>
</li>
</ol>
<p>Why did I create this plugin, even though some others already exist? Because I wanted to:</p>
<ol>
<li>
<p>easily integrate CodeIgniter without invading its core very much, or optionally, not at all.</p>
</li>
<li>
<p>show CodeIgniter output in a page, preserving all WordPress menu structure, template structure etc.</p>
</li>
<li>
<p>not require template editing, so that templates can be easily swapped out and the CodeIgniter itegration still work.</p>
</li>
<li>
<p>allow customizing of the CodeIgniter APPPATH and BASEPATH variables, so that the system and application folders can be put somewhere outside the plugins folder (or docroot altogether for that matter)</p>
</li>
<li>
<p>handle segmented urls in CodeIgniter fashion, including paths that aren’t valid in WordPress (i.e. via WordPress 404 hooks), and dispatch to appropriate CodeIgniter controller functions.</p>
</li>
</ol>
<h3>Tips</h3>
<ul>
<li>If your CodeIgniter controller sets the $this->content[‘page_title’], such as <code>$this->content['page_title'] = 'Blast off!';</code><br />
then this plugin will set the template-rendered title to “Blast off!” via a WordPress API registered ‘the_title’ filter hook.</li>
<li>If you choose to tick the “CodeIgniter grabs all SEO urls” checkbox, beware that CodeIgniter will return its own 404 page (along<br />
with http header!) on any non-root urls, i.e. permalinks.  This behaviour can be set within CodeIgniter by adjusting the routes.php<br />
file to point to a valid controller, like this: <code>$route['404_override'] = 'welcome';</code></li>
</ul>
<h3>TODO</h3>
<p>(I don’t know if these are even possible, or I might have already done them)</p>
<ul>
<li>provide a way to make CodeIgniter automatically use WordPress’ database settings, from within the plugin (yes I know I could intrude CodeIgniter core to do this, but it’s what I wanted to avoid)</li>
<li>provide a mechanism to instantiate CodeIgniter <em>only</em> on the overridden page, rather than all frontend urls.</li>
</ul>


Churro vs WordPressIgniter