NewClarity

Mike Schinkel

WPLib is a plugin designed to be used as a Must-Use plugin or to be embedded in a theme to enable the development of complex yet robust and performant WordPress applications and websites.
WPLib is a foundation library upon which robust applications can be developed. WPLib is not intended for use by end-users but instead by professional PHP developers who are tasked with building specific applications or sites on the WordPress platform by their company or their clients.
Think of developing with WPLib to be somewhat like:
<blockquote>“The joy of programming in Lavarel while respecting everything about WordPress that makes it an ideal platform for developing content management solutions.”</blockquote>
The WPLib source code is hosted and development occurs <a href="https://github.com/wplib/wplib/" rel="nofollow ugc">on GitHub</a> and the documentation site will soon be located at <a href="https://wplib.org" rel="nofollow ugc">wplib.org</a>.
<h3>Documentation</h3>
You will find documentation in its current state on the <a href="https://github.com/wplib/wplib/wiki" rel="nofollow ugc">wiki</a>.

WPLib

A Foundation Library for Agency and Corporate Developers.

dynamodan

A WordPress plugin that integrates CodeIgniter
Why a CodeIgniter/Wordpress integration plugin?
<ol>
<li>
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
</li>
<li>
I’m getting tired of building custom user, login, and session management systems for CodeIgniter. WordPress has them already.
</li>
<li>
I’m getting tired of building custom look and feel and templates for CodeIgniter, WordPress already is that, and has thousands of themes available.
</li>
<li>
I’m getting tired of building custom feature X for CodeIgniter, when it may already exist in WordPress either natively or as a plugin.
</li>
</ol>
Why did I create this plugin, even though some others already exist? Because I wanted to:
<ol>
<li>
easily integrate CodeIgniter without invading its core very much, or optionally, not at all.
</li>
<li>
show CodeIgniter output in a page, preserving all WordPress menu structure, template structure etc.
</li>
<li>
not require template editing, so that templates can be easily swapped out and the CodeIgniter itegration still work.
</li>
<li>
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)
</li>
<li>
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.
</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> 
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 
with http header!) on any non-root urls, i.e. permalinks. This behaviour can be set within CodeIgniter by adjusting the routes.php 
file to point to a valid controller, like this: <code>$route['404_override'] = 'welcome';</code></li>
</ul>
<h3>TODO</h3>
(I don’t know if these are even possible, or I might have already done them)
<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 only on the overridden page, rather than all frontend urls.</li>
</ul>

WPLib vs WordPressIgniter