jimisaacs

<p>In addition to adding numerous extremely useful widgets for developers and users alike, this plugin is a system written on a PHP 5 object oriented structure. In short, it is built for modification and extension. It wraps the WordPress Widget API to allow for an alternative, and in my opinion more robust method to hook into and use it. Widgets are WordPress’s version of user interface modules. They already support an administrative and client-side view. This system simply leverages that with a higher potential in mind.</p>
<p>This plugin started as a collection of widgets that I developed over time and used in numerous projects. I eventually merged them into one conglomerate which is now known as the ‘Extensible Widgets’ plugin. Currently I do not have extensive documentation on the plugin functionality and code-base yet.</p>
<p>A Quick summary is that this plugin in its current state is a PHP widget class manager, as well as a collection of useful widget classes that build on each other for extended functionality. When the plugin is first activated, the widget classes included are not registered automatically, and will not appear within your WordPress widgets administration page. To activate your desired widgets you must go to the ‘Extensible Widgets’ Registration page. From there you can read a short description before registering anything.</p>
<p>This plugin also comes with an Export and Import page. You will notice this functionality is very useful in backing up your current data of all your widgets and ‘Extensible Widgets’ settings. I felt this was a major necessity since while using ‘Extensible Widgets’ these little pieces of data suddenly turn into major aspects in the whole of your website. I needed to give an acceptable method of retrieving, backing up, and restoring that data if something bad happens.</p>
<p>A quick summary of the most useful of the widgets included:</p>
<ul>
<li>Widget Group: Use this widget to create a new widget group, as a widget? Yes… this is where it gets interesting.</li>
<li>Query Posts: A Widget than can create and use a sub-query or use the current global query and output the results in a view template.</li>
<li>Context: More basic options that would be good for any widget, but this widget is specifically used for controlling where widgets appear.</li>
</ul>
<h3>Widgets</h3>
<p>These are the widgets that come with this plugin. No widget here is pre-registered, this is to let you register them as needed. Each widgets builds on another’s functionality, and you may view the hierarchy from within the ‘Extensible Widgets’ registration page.</p>
<h4>Widget Base</h4>
<p>The base for ‘Extensible Widgets’ and not much on its own, it can still serve as a useful dynamic element.</p>
<h4>Context</h4>
<p>More basic options that would be good for any widget, but this widget is specifically used for controlling where widgets appear.</p>
<h4>View</h4>
<p>Use the view template control system and pass custom parameters to display data in any desired format.</p>
<h4>Content</h4>
<p>Use this widget to enter any data (ex: text/HTML/XML/JavaScript) and optionally access it within in a view template.</p>
<h4>Date</h4>
<p>Use this widget to select a view template and handle any arbitrary date.</p>
<h4>Widget Group</h4>
<p>Use this widget to create a new widget group, as a widget? Yes… this is where it gets interesting.</p>
<h4>Query Posts</h4>
<p>A Widget than can create and use a sub-query or use the current global query and output the results in a view template.</p>
<h4>QP Extended</h4>
<p>This is an extended version of the Query Posts widget with a controlled form.</p>
<h4>Twitter</h4>
<p>Use this widget to retrieve statuses from a specified twitter account.</p>


Extensible Widgets

Includes extremely useful widgets for developers and users alike, and is a system written on a PHP 5 object oriented structure.

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>


Extensible Widgets vs WordPressIgniter