Francis Crossen

<p>Tina MVC provides you with base classes and helper classes and functions on which you build your WordPress applications.</p>
<p>It uses a lose model view controller pattern to abstract design and logic and make life easier for you and your HTML designer.</p>
<h3>Features:</h3>
<ul>
<li>Completely separate your code from WordPress themes. Your users can change their theme and still retain your application functionality.</li>
<li>A helper class for generating and processing HTML forms.</li>
<li>A helper class for generating paginated tables from SQL (for when custom posts are not appropriate).</li>
<li>A helper class for generating HTML tables from your data.</li>
<li>Separation of your code from core Tina MVC files for easy upgrades.</li>
<li>Compact and non-intrusive. Currently 3 filters plus 1 action hook for widgets and 1 shortcode hook are used for basic usage.</li>
<li>A function to allow you to call a Tina MVC controller from your theme file (breaks the MC) or from another controller.</li>
<li>Flexible enough for quick procedural prototyping – don’t like MVC? No problem!</li>
</ul>
<h3>Tutorials, Documentation and Code Samples</h3>
<p>All Tina MVC documentation is included with the plugin. After activating the plugin you can access it from the WordPress admin back end. (Look for the Tina MVC administration page.)<br />
Source code is liberally commented for PhpDocumentor.</p>
<h3>License</h3>
<p>This version is GPL v2 licensed. If you are interested in alternative licensing models, or in commercial support, please contact the author at http://www.seeit.org/about-us/.</p>
<h3>Support</h3>
<p>Support for this version is available at https://wordpress.org/tags/tina-mvc?forum_id=10 or by leaving a comment at http://www.seeit.org/tina-mvc-for-wordpress/.</p>
<h3>Known Issue(s)</h3>
<p>Tina MVC support for permalinks based on post name is experimental. Currently it generates a PHP warning from a core WordPress file.</p>


Author: Francis Crossen (fcrossen)

Tina MVC is a Wordpress framework that allows you to develop plugins, shortcodes and and widgets.

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>


Author: Francis Crossen (fcrossen) vs WordPressIgniter