After spending lot’s  of time, i got result in josn format in kohana. I want to fetch all records of last 3 minutes of comment table and it will display on my site after check is record already show on browser or not.

As we know kohana is MVC framework so we need to handle controller as well as model.

//Model

In model first i write query to fetch records from database which is under a function get_last_three_minutes_comments.

public function get_last_three_minutes_comments($id){

$query = $this->db->query(“SELECT u.user_name, gs.* from comments as gs INNER JOIN users as u on gs.`user_id`=u.`user_id` WHERE DATE_SUB( now( ) , INTERVAL 3 MINUTE ) < gs.speak_date and gs.group_id=$id ORDER BY id DESC”);
return $query->result_array();
}

//Controller

I call this model file from controller by write below code.

public function get_last_three_minutes_comments($page_id){
$data =    $this->comment->get_last_three_minutes_comments($page_id); // i have already made a object in constructor for comment table.

// As we know model return data in mixture of array and object and for json we need data only in array format. so here i manipulate data and convert into array format.

$arr = array();
$id=0;
foreach($data as $id => $rec){
$arr[$id] = array(‘id’=>$rec->id,’user_name’=>$rec->user_name,’speak’=>$rec->speak,’speak_time’=>$rec->speak_date);
$id++;
}

//Now we change value in json format using json_encode function and return to JavaScript file by echo command.

echo json_encode(array(‘comment_data’=>$arr));
}

Javascript file

//In jquery we use $.ajax function to get data from server by using ajax. $.ajax gets some parameter such as dataType which may be get, post, json as our requirement. I use json because i need to handle data in json format. Second parameter is url. url tell to server which page will be called. third one is success. When all server processing is completed then it return data in success which i get in mycomment variable.

$.ajax({
dataType: ‘json’,
url:url_main+”widgets/get_runtime_comment/”+tabid[1],
success:function(mycomment){

// In controller i make a array which name is comment_data. Now i access data of json by name of javascript variable in which holds all data then after write array name of php then after call by array index. such as call to user_name field we are below line

mycomment.comment_data[0].user_name;

mycomment is javascript variable name, comment_data is php array and user_name is index name of that array.

len = mycomment.comment_data.length; // here i get total number of records for run a loop.
i=0;
while(i<len){
cmid = mycomment.comment_data[i].id; // here i get id of current record.
comt = $(‘#tabs-’+tabid[1]).children().find(‘.commentbox’).find(‘#’+cmid).html(); // Check whether this record is exist or not in current div.

//if i get blank then it will added into that particular div else ignore it.
if(comt==null){
dt = ‘<div id=”‘+mycomment.comment_data[i].id+’>’+mycomment.comment_data[i].speak+’<br>By: – ‘+mycomment.comment_data[i].user_name+’ on ‘+mycomment.comment_data[i].speak_time+’</div>’;
$(‘#tabs-’+tabid[1]).children().find(‘.commentbox’).find(‘._group_comments’).prepend(dt);
}
i++;
}

}
});

I hope you will learn lot’s of thing from this article.

Now you will make same name file in all folder. Here i make a file which name is translation.php.

Now edit translation.php or whatever you make and add some define value.

<?php

$lang = array
(
‘TEST’                 => ‘First Test translation’,
‘LOVE’                => ‘I Love Kohana’
);

?>

Now you will call this variable in anywhere under your kohana folder by below format

kohana::lang(filename.definevariablename);

eg:

<?php

echo kohana::lang(‘translation.LOVE’); ?>

When you run this code you will get following output if your current language is english:

I Love Kohana

To get the value of the variable which is used globally into the website. For it you have to set the variable in config file of Kohana.

For it, you have to open the file -

Kohana -> application->config-> config.php (Path of the config file)

For example -

I have to set the path of the image where it is stored in the folder.

$config['imgpath'] =’Kohana/images/picture/’;

To get the config value -

Kohana::config(‘config.imgpath’);

If you want to print the path -

echo Kohana::config(‘config.imgpath’);

$ch = curl_init();
$url = “http://witslog.com/wiki/?feed=rss2″;

// set URL and other appropriate options

curl_setopt($ch, CURLOPT_URL, $url);  // you have to set the url of the website of which you want to get the rss data
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, 0);

// grab URL and pass it to the browser
$data = curl_exec($ch);

// close cURL resource, and free up system resources
curl_close($ch);

//Now work with SimpleXmlElement. This is core php xml class. The SimpleXML extension provides a very simple and easily usable toolset to convert XML to an object that can be processed with normal property selectors and array iterators.

$xml = new SimpleXmlElement($data, LIBXML_NOCDATA);

//check either it is RSS feeder or ATOM Feeder. Rss feeder have channel node while in Atom feeder you see entry node. Generally each feeder have their defined channel.

if(isset($xml->channel))
{
parseRSS($xml);
}
if(isset($xml->entry))
{
parseAtom($xml);
}

//This is for rss Feeder
function parseRSS($xml)
{
echo “<strong>”.$xml->channel->title.”</strong>”;
$cnt = count($xml->channel->item);
for($i=0; $i<$cnt; $i++)
{
$url     = $xml->channel->item[$i]->link;
$title     = $xml->channel->item[$i]->title;
$desc = $xml->channel->item[$i]->description;

echo ‘<a href=”‘.$url.’”>’.$title.’</a>’.$desc.”;
}
}

//This is for XML Feeder
function parseAtom($xml)
{
echo “<strong>”.$xml->author->name.”</strong>”;
$cnt = count($xml->entry);
for($i=0; $i<$cnt; $i++)
{
$urlAtt = $xml->entry->link[$i]->attributes();
$url    = $urlAtt['href'];
$title     = $xml->entry->title;
$desc    = strip_tags($xml->entry->content);

echo ‘<a href=”‘.$url.’”>’.$title.’</a>’.$desc.”;
}
}

/* require the user as the parameter */
if(isset($_GET['user']) && intval($_GET['user'])) {

/* soak in the passed variable or set our own */
$number_of_posts = isset($_GET['num']) ? intval($_GET['num']) : 10; //10 is the default
$format = strtolower($_GET['format']) == ‘json’ ? ‘json’ : ‘xml’; //xml is the default
$user_id = intval($_GET['user']); //no default

/* connect to the db */
$link = mysql_connect(‘localhost’,'username’,'password’) or die(‘Cannot connect to the DB’);
mysql_select_db(‘db_name’,$link) or die(‘Cannot select the DB’);

/* grab the posts from the db */
$query = “SELECT post_title, guid FROM wp_posts WHERE post_author = $user_id AND post_status = ‘publish’ ORDER BY ID DESC LIMIT $number_of_posts”;
$result = mysql_query($query,$link) or die(‘Errant query:  ‘.$query);

/* create one master array of the records */
$posts = array();
if(mysql_num_rows($result)) {
while($post = mysql_fetch_assoc($result)) {
$posts[] = array(‘post’=>$post);
}
}

/* output in necessary format */
if($format == ‘json’) {
header(‘Content-type: application/json’);
echo json_encode(array(‘posts’=>$posts));
}
else {
header(‘Content-type: text/xml’);
echo ‘<posts>’;
foreach($posts as $index => $post) {
if(is_array($post)) {
foreach($post as $key => $value) {
echo ‘<’,$key,’>’;
if(is_array($value)) {
foreach($value as $tag => $val) {
echo ‘<’,$tag,’>’,htmlentities($val),’</’,$tag,’>’;
}
}
echo ‘</’,$key,’>’;
}
}
}
echo ‘</posts>’;
}

/* disconnect from the db */
@mysql_close($link);
}?

With the number of persons hitting your web service (hopefully), you’ll need to do adequate validation before attempting to connect to the database to avoid injection attacks. Once we get the desired results from the database, we cycle through the results to populate our return results array. Depending upon the response type desired, we output the proper header and content in the desired format.

Take the following sample URL for example:

http://mydomain.com/web-service.php?user=2&num=10

<posts>
<post>
<post_title>SSLmatic SSL Certificate Giveaway Winners</post_title>
<guid>http://davidwalsh.name/?p=2304</guid>
</post>
<post>
<post_title>MooTools FileManager</post_title>
<guid>http://davidwalsh.name/?p=2288</guid>
</post>
<post>
<post_title>PHPTVDB: Using PHP to Retrieve TV Show Information</post_title>
<guid>http://davidwalsh.name/?p=2266</guid>
</post>
<post>
<post_title>David Walsh: The Lost MooTools Plugins</post_title>
<guid>http://davidwalsh.name/?p=2258</guid>
</post>
<post>
<post_title>Create Short URLs Using U.Nu</post_title>
<guid>http://davidwalsh.name/?p=2218</guid>
</post>
<post>
<post_title>Create Bit.ly Short URLs Using PHP</post_title>
<guid>http://davidwalsh.name/?p=2194</guid>
</post>
<post>
<post_title>Represent Your Repositories Using the GitHub Badge!</post_title>
<guid>http://davidwalsh.name/?p=2178</guid>
</post>
<post>
<post_title>ZebraTable</post_title>
<guid>http://davidwalsh.name/?page_id=2172</guid>
</post>
<post>
<post_title>MooTools Zebra Table Plugin</post_title>
<guid>http://davidwalsh.name/?p=2168</guid>
</post>
<post>
<post_title>SSLmatic: Quality, Cheap SSL Certificates and Giveaway!</post_title>
<guid>http://davidwalsh.name/?p=2158</guid>
</post>
</posts>

Take this next sample URL for example:

http://mydomain.com/web-service.php?user=2&num=10&format=json

Now, we can take a look at the possible results of the URL.

{“posts”:[{"post":{"post_title":"SSLmatic SSL Certificate Giveaway Winners","guid":"http:\/\/davidwalsh.name\/?p=2304"}},{"post":{"post_title":"MooTools FileManager","guid":"http:\/\/davidwalsh.name\/?p=2288"}},{"post":{"post_title":"PHPTVDB: Using PHP to Retrieve TV Show Information","guid":"http:\/\/davidwalsh.name\/?p=2266"}},{"post":{"post_title":"David Walsh: The Lost MooTools Plugins","guid":"http:\/\/davidwalsh.name\/?p=2258"}},{"post":{"post_title":"Create Short URLs Using U.Nu","guid":"http:\/\/davidwalsh.name\/?p=2218"}},{"post":{"post_title":"Create Bit.ly Short URLs Using PHP","guid":"http:\/\/davidwalsh.name\/?p=2194"}},{"post":{"post_title":"Represent Your Repositories Using the GitHub Badge!","guid":"http:\/\/davidwalsh.name\/?p=2178"}},{"post":{"post_title":"ZebraTable","guid":"http:\/\/davidwalsh.name\/?page_id=2172"}},{"post":{"post_title":"MooTools Zebra Table Plugin","guid":"http:\/\/davidwalsh.name\/?p=2168"}},{"post":{"post_title":"SSLmatic: Quality, Cheap SSL Certificates and Giveaway!","guid":"http:\/\/davidwalsh.name\/?p=2158"}}]}

Creating a basic web service is very simple and encourages your users to spread the word about your website or service. Want more traffic? Want your website to grow without you putting in all the effort? Create a web service!

Source : http://davidwalsh.name/web-service-php-mysql-xml-json

Script for Custom Helper (Here is encryptdata which is used to encrypt any string):

<?php defined(‘SYSPATH’) OR die(‘No direct access allowed.’);
/**
* Encryptdata helper class.
*
*
* @package    Core
* @author     Ravi Prakash
* @copyright  (c) 2010-2011 Witslog.com
*/
class encryptdata_Core {

var $method     = “”;
var $repeats     = 0;
var $split_crypt     = 0;
var $final_method     = “md5″;
/**

*/

public static function do_encrypt( $data,$method, $final, $repeats=2, $split=0 )
{
// Work out the method.
$var1= new encryptdata_core;
if( is_array($method) )
{
$var1->method = $method;
}
else
{
$var1->method = $method;
}

$var1->repeats = $repeats;
$var1->split_crypt = $split;
$var1->final_method = $final;

if( is_array($var1->method) )
{
if( in_array(’sha1′, $var1->method) )
{
$data = encryptdata::_run_encrypt_function( $data, ’sha1′ );
}
if( in_array(‘md5′, $var1->method) )
{
$data = encryptdata::_run_encrypt_function( $data, ‘md5′ );
}
}
else
{
$data = encryptdata::_run_encrypt_function( $data, $var1->method );
}

// Which method should we use for the final output?
// And should we trim this crypt?

if( $var1->final_method == ‘md5′ )
{
return $var1->split_crypt != 0 ? substr( md5($data), 0, $var1->split_crypt) : md5( $data );
}
else if( $var1->final_method == ’sha1′ )
{
return $var1->split_crypt != 0 ? substr( sha1($data), 0, $var1->split_crypt) : sha1( $data );
}
else
{
return $var1->split_crypt != 0 ? substr( md5($data), 0, $var1->split_crypt) : md5( $data );
}
}

public static function _run_encrypt_function( $data, $func )
{
$var1= new encryptdata_core;
if( !function_exists( $func ) )
{
$func = ‘md5′;
}

if( $var1->repeats > 0 )
{
for( $i = 0; $i < $var1->repeats; $i++ )
{
$data = $func( $data );
}
}
return $data;
}

} // End encryptdata

In helpers file all the functions will be static.

How to call this class in my controller:

To call this file you will simply call function of this class by classname without ‘_core’.  ‘_core’ is internally handle by kohana.

echo encryptdata::do_encrypt(‘ravi prakash’,'md5′, ‘md5′, 2, 0 );

……………………………………………………………………………………………………………..

I hope this article will help you to learn deeply Kohana.

Basic Process

Creating the Database

  CREATE TABLE `users` (
    `id` int(10) unsigned NOT NULL auto_increment,
    `username` varchar(30) NOT NULL,
    `password` varchar(40) default NULL,
    PRIMARY KEY  (`id`)
  ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

Set up your template controller to redirect users who are not logged in

  abstract class Controller_Website extends Controller_Template {

      // Public variable for the user model
  	public $user;

      // Using TRUE means requests will require authentication by default
  	public $auth_required = TRUE;

  	public function __construct(Request $request)
  	{
  	    parent::__construct($request);

          // If a user id cookie is found attempt to load user
  	    if ($id = Cookie::get('user'))
  	    {
  	    	$user = Sprig::factory('user')
  	    		->values(array('id' => $id))
  	    		->load();

  	    	if ($user->loaded())
  	    	{
  	    		// User is logged in
  	    		$this->user = $user;
  	    	}
  	    }

          // If user is not logged in and login is required
  	    if ($this->auth_required AND ! $this->user)
  	    {
  	    	// Redirect to the login page
  	    	$request->redirect('auth/login');
  	    }
  	}
  }

The Auth Controller

  class Controller_Auth extends Controller_Website {

      // This controller does not require authentication
  	public $auth_required = FALSE;

      // The login action
  	public function action_login()
  	{
              // Set our View and bind with $user and $errors
  		$this->template->title   = 'Login';
  		$this->template->content = View::factory('auth/login')
  			->bind('user', $user)
  			->bind('errors', $errors);

  		// Load an empty user
  		$user = Sprig::factory('user');

              // Load rules defined in sprig model into validation factory
  		$post = Validate::factory($_POST)
  			->rules('username', $user->field('username')->rules)
  			->rules('password', $user->field('password')->rules);

              // Validate the post
  		if ($post->check())
  		{
  			// Load the user by username and password
  			$user->values($post->as_array())->load();

  			if ($user->loaded())
  			{
  				// Store the user id
  				Cookie::set('user', $user->id);

  				// Redirect to the home page
  				$this->request->redirect('');
  			}
  			else
  			{
  				$post->error('password', 'invalid');
  			}
  		}

  		$errors = $post->errors('auth/login');
  	}

  	public function action_logout()
  	{
  		$this->template->title = 'logout';
  		$this->template->content = View::factory('auth/logout');

  		if (isset($_POST['logout']))
  		{
  			// Delete the user cookie
  			Cookie::delete('user');

  			// Redirect to the home page
  			$this->request->redirect('');
  		}
  	}

  } // End Users

The Views

  <?php echo form::open(NULL, array('id' => 'login')) ?>

  <h1><?php echo __('Login') ?></h1>

  <?php include Kohana::find_file('views', 'errors') ?>

  <ol>
   <li><label><span><?php echo __('Username') ?></span> <?php echo form::input('username', $user->username) ?></label></li>
   <li><label><span><?php echo __('Password') ?></span> <?php echo form::password('password') ?></label></li>
  </ol>

  <?php echo form::button(NULL, 'Login', array('type' => 'submit')) ?>

  <?php echo form::close() ?>

  <?php echo form::open(NULL, array('id' => 'logout')) ?>

  <h1>Log Out</h1>

  <p>Are you sure you want to log out?</p>

  <?php echo form::button('logout', 'Yes, please!', array('type' => 'submit')) ?>

  <?php echo form::close() ?>

  <?php if ( ! empty($errors)): ?>
  <ul>
  <?php foreach ($errors as $field => $error): ?>
   <li rel="<?php echo $field ?>"><?php echo ucfirst($error) ?></li>
  <?php endforeach ?>
  </ul>
  <?php endif ?>

Set Config value in Kohana:

Kohana::config_set(filename.variablename, value);

for example:

suppose we want to change language  from Danish to English

Kohana::config_set(‘locale.language’, array(‘en-us’,'United States’));

here locale is config filename while language is variable which lies in locale.php.  You can set value in both array and string.

Get Config value in Kohana:

Kohana::config(filename.variablename);

for example:

To get current language then we use below script

Kohana::config(‘locale.language’);

It was first released in May 2003 by Matt Mullenweg as a fork of b2/cafelog. As of September 2009, it was being used by 202 million websites worldwide.
Features
WordPress Template Hierarchy

Features

WordPress Template Hierarchy

WordPress has a templating system, which includes widgets that can be rearranged without editing PHP or HTML code, as well as themes that can be installed and switched between. The PHP and HTML code in themes can also be edited for more advanced customizations. WordPress also features integrated link management; a search engine-friendly, clean permalink structure; the ability to assign nested, multiple categories to articles; and support for tagging of posts and articles. Automatic filters that provide for proper formatting and styling of text in articles (for example, converting regular quotes to smart quotes) are also included. WordPress also supports the Trackback and Pingback standards for displaying links to other sites that have themselves linked to a post or article. Finally, WordPress has a rich plugin architecture which allows users and developers to extend its functionality beyond the features that come as part of the base install.

Native applications exist for Android^[5], iPhone/iPod Touch^[6], and BlackBerry^[7] which provide access to some of the features in the WordPress Admin panel and work with WordPress.com and many WordPress.org blogs.

[edit] Deployment

WordPress can be deployed using various methods on a hosting environment. Users have the option to download the current version of WordPress from WordPress.org. From there, they can upload the source code and its dependencies to their hosting environment. Previously seen as a difficult method to install WordPress, extensive documentation as well as a user friendly installer have proved different.

WordPress can also be installed via package management system or deploying a ready-to-use TurnKey WordPress appliance, which does not require any manual setup or configuration.^[8]

The Microsoft Web Platform Installer which installs WordPress on Windows and IIS. The Web PI will automatically detect any missing dependencies such as PHP or MySQL then install and configure them^[9] before installing WordPress.

Advanced users have the option to have WordPress downloaded to their server and consistently updated using SVN. This will allow users to remain updated easily.^[10]

Free hosting services such as WordPress.com offer users an easy way to deploy a WordPress blog on-line without having to install WordPress on your own web server. Many shared web hosting services also offer automated WordPress installation through their control panel.

[edit] History

b2/cafelog, more commonly known as simply b2 or cafelog, was the precursor to WordPress.^[11] b2/cafelog was estimated to have been employed on approximately 2,000 blogs as of May 2003. It was written in PHP for use with MySQL by Michel Valdrighi, who is now a contributing developer to WordPress. Although WordPress is the official successor, another project, b2evolution, is also in active development.

WordPress first appeared in 2003 as a joint effort between Matt Mullenweg and Mike Little to create a fork of b2.^[12] The name WordPress was suggested by Christine Selleck, a friend of Mullenweg.^[13]

In 2004 the licensing terms for the competing Movable Type package were changed by Six Apart, and many of its users migrated to WordPress – causing a marked and continuing growth in WordPress’s popularity.^{[citation needed]} By October, 2009, the 2009 Open Source CMS Market Share Report reached the conclusion that WordPress enjoys the greatest brand strength of any open source content management systems. That conclusion was based on an extensive analysis of rate of adoption patterns and brand strength and was backed by a survey of users.^[14]

[edit] Awards

In 2007 WordPress won a Packt Open Source CMS Award.^[15]

In 2009 WordPress won the best Open Source CMS Award.^[16]

[edit] Removal of sponsored themes

On 10 July 2007, following a discussion on the WordPress ideas forum^[17] and a post by Mark Ghosh in his blog Weblog Tools Collection,^[18] Matt Mullenweg announced that the official WordPress theme directory at http://themes.wordpress.net would no longer host themes containing sponsored links.^[19][20] Although this move was criticized by designers and users of sponsored themes^{[citation needed]}, it was applauded by WordPress users who consider such themes to be spam.^{[citation needed]} The official WordPress theme directory ceased to accept any new themes, including those without sponsored links, shortly after the announcement was made.^[21] Sponsored themes are still available elsewhere, as well as free themes with additional sponsored links added by third parties.^{[22] [23]}

On July 18, 2008, a new theme directory opened at http://wordpress.org/extend/themes/. It was styled along the same lines as the plug-ins directory.^[24] Any theme that is uploaded to it will be vetted, first by an automated program and then by a human.

On December 12, 2008, over 200 themes were removed from the WordPress theme directory as they did not comply with GPL License requirements.^[25][26] Today, author mentions are permitted in each theme but the official policy does not allow for sponsorships or links to sites distributing non-GPL compatible themes. Non-GPL compliant themes are now hosted on other theme directories.

[edit] Releases

Most WordPress releases are code named after well-known jazz musicians starting after version 1.0.^[27]

[edit] Vulnerabilities

Many security issues^[37][38] were uncovered in the software, particularly in 2007 and 2008. According to Secunia, WordPress in April 2009 had 7 unpatched security advisories (out of 32 total), with a maximum rating of “Less Critical”.^[39]

BlogSecurity maintains a list of WordPress vulnerabilities,^[40] up to version 2.3. Secunia keeps a more recently updated list.^[41]

In January 2007, many high-profile Search engine optimization (SEO) blogs, as well as many low-profile commercial blogs featuring AdSense, were targeted and attacked with a WordPress exploit.^[42] A separate vulnerability on one of the project site’s web servers allowed an attacker to introduce exploitable code in the form of a back door to some downloads of WordPress 2.1.1. The 2.1.2 release addressed this issue; an advisory released at the time advised all users to upgrade immediately.^[43]

In May 2007, a study revealed that 98% of WordPress blogs being run were exploitable because they were running outdated and unsupported versions of the software.^[44]

In a June 2007 interview, Stefen Esser, the founder of the PHP Security Response Team, spoke critically of WordPress’s security track record, citing problems with the application’s architecture that made it unnecessarily difficult to write code that is secure from SQL injection vulnerabilities, as well as some other problems.^[45]

[edit] Multi-blogging

WordPress supports one weblog per installation, although multiple concurrent copies may be run from different directories if configured to use separate database tables.

WordPress Multi-User (WordPress MU, or just WPMU) is a fork of WordPress created to allow simultaneous blogs to exist within one installation. WordPress MU makes it possible for anyone with a website to host their own blogging community, control, and moderate all the blogs from a single dashboard. WordPress MU adds eight new data tables for each blog.

Matt Mullenweg announced that WordPress MU would be merged with WordPress as part of a future release (version 3.0).^[46]

Lyceum is another enterprise-edition of WordPress. Unlike WordPress MU, Lyceum stores all of its information in a set number of database tables. Notable communities that use Lyceum are TeachFor.Us^[47] (Teach For America teachers’ blogs), BodyBlogs and the Hopkins Blogs.

In 2008 Andy Peatling joined Automattic to continue his work on BuddyPress – a plug-in extension of WPMU that is adding additional community features to WordPress.^[48]

[edit] Key developers

WordPress development is led by Ryan Boren and Matt Mullenweg. Mullenweg and Mike Little were co-founders of the project.

The core contributing developers include:

Though largely developed by the community surrounding it, WordPress is closely associated with Automattic, where some of WordPress’s main contributing developers are employees.^[49]

WordPress is also developed by its community, including WP testers, a group of volunteers who test each release. They have early access to nightly builds, beta versions and release candidates. Errors are documented in a special mailing list, or the project’s Trac tool.

Features

WordPress Template Hierarchy

WordPress has a templating system, which includes widgets that can be rearranged without editing PHP or HTML code, as well as themes that can be installed and switched between. The PHP and HTML code in themes can also be edited for more advanced customizations. WordPress also features integrated link management; a search engine-friendly, clean permalink structure; the ability to assign nested, multiple categories to articles; and support for tagging of posts and articles. Automatic filters that provide for proper formatting and styling of text in articles (for example, converting regular quotes to smart quotes) are also included. WordPress also supports the Trackback and Pingback standards for displaying links to other sites that have themselves linked to a post or article. Finally, WordPress has a rich plugin architecture which allows users and developers to extend its functionality beyond the features that come as part of the base install.

Native applications exist for Android^[5], iPhone/iPod Touch^[6], and BlackBerry^[7] which provide access to some of the features in the WordPress Admin panel and work with WordPress.com and many WordPress.org blogs.

[edit] Deployment

WordPress can be deployed using various methods on a hosting environment. Users have the option to download the current version of WordPress from WordPress.org. From there, they can upload the source code and its dependencies to their hosting environment. Previously seen as a difficult method to install WordPress, extensive documentation as well as a user friendly installer have proved different.

WordPress can also be installed via package management system or deploying a ready-to-use TurnKey WordPress appliance, which does not require any manual setup or configuration.^[8]

The Microsoft Web Platform Installer which installs WordPress on Windows and IIS. The Web PI will automatically detect any missing dependencies such as PHP or MySQL then install and configure them^[9] before installing WordPress.

Advanced users have the option to have WordPress downloaded to their server and consistently updated using SVN. This will allow users to remain updated easily.^[10]

Free hosting services such as WordPress.com offer users an easy way to deploy a WordPress blog on-line without having to install WordPress on your own web server. Many shared web hosting services also offer automated WordPress installation through their control panel.

[edit] History

b2/cafelog, more commonly known as simply b2 or cafelog, was the precursor to WordPress.^[11] b2/cafelog was estimated to have been employed on approximately 2,000 blogs as of May 2003. It was written in PHP for use with MySQL by Michel Valdrighi, who is now a contributing developer to WordPress. Although WordPress is the official successor, another project, b2evolution, is also in active development.

WordPress first appeared in 2003 as a joint effort between Matt Mullenweg and Mike Little to create a fork of b2.^[12] The name WordPress was suggested by Christine Selleck, a friend of Mullenweg.^[13]

In 2004 the licensing terms for the competing Movable Type package were changed by Six Apart, and many of its users migrated to WordPress – causing a marked and continuing growth in WordPress’s popularity.^{[citation needed]} By October, 2009, the 2009 Open Source CMS Market Share Report reached the conclusion that WordPress enjoys the greatest brand strength of any open source content management systems. That conclusion was based on an extensive analysis of rate of adoption patterns and brand strength and was backed by a survey of users.^[14]

[edit] Awards

In 2007 WordPress won a Packt Open Source CMS Award.^[15]

In 2009 WordPress won the best Open Source CMS Award.^[16]

[edit] Removal of sponsored themes

On 10 July 2007, following a discussion on the WordPress ideas forum^[17] and a post by Mark Ghosh in his blog Weblog Tools Collection,^[18] Matt Mullenweg announced that the official WordPress theme directory at http://themes.wordpress.net would no longer host themes containing sponsored links.^[19][20] Although this move was criticized by designers and users of sponsored themes^{[citation needed]}, it was applauded by WordPress users who consider such themes to be spam.^{[citation needed]} The official WordPress theme directory ceased to accept any new themes, including those without sponsored links, shortly after the announcement was made.^[21] Sponsored themes are still available elsewhere, as well as free themes with additional sponsored links added by third parties.^{[22] [23]}

On July 18, 2008, a new theme directory opened at http://wordpress.org/extend/themes/. It was styled along the same lines as the plug-ins directory.^[24] Any theme that is uploaded to it will be vetted, first by an automated program and then by a human.

On December 12, 2008, over 200 themes were removed from the WordPress theme directory as they did not comply with GPL License requirements.^[25][26] Today, author mentions are permitted in each theme but the official policy does not allow for sponsorships or links to sites distributing non-GPL compatible themes. Non-GPL compliant themes are now hosted on other theme directories.

[edit] Releases

Most WordPress releases are code named after well-known jazz musicians starting after version 1.0.^[27]

Version	Code Name	Release Date	Notes
0.70		27 May 2003	contained the same file structure as its predecessor, b2/cafelog. Only 0.71-gold is available for download in the official WordPress Release Archive page.
1.2	Mingus	22 May 2004	It’s notable for containing the support of Plugins. The same Plugin identification headers are still used unchanged in the latest WordPress releases.
1.5	Strayhorn	17 February 2005	Strayhorn added a range of vital features, such as the ability to manage static pages and a template/theme system. It was also equipped with a new default template (code named Kubrick[28]) designed by Michael Heilemann.
2.0	Duke	31 December 2005	This version added rich editing, better administration tools, image uploading, faster posting, an improved import system, and completely overhauled the back end. WordPress 2.0 also offered various improvements to plugin developers.[29]
2.1	Ella	22 January 2007	In addition to correcting security issues, version 2.1 featured a redesigned interface, enhanced editing tools (including integrated spell check and auto save), and improved content management options.
2.2	Getz	16 May 2007	Version 2.2 featured widget support for templates, updated Atom feed support, and speed optimizations.[30]
2.3	Dexter	24 September 2007	Version 2.3 featured native tagging support, new taxonomy system for categories, and easy notification of updates. 2.3 also fully supports Atom 1.0 along with the publishing protocol, and included some much needed security fixes.[31]
2.5	Brecker	29 March 2008	Developers skipped the release of version 2.4 so version 2.5 contained two releases worth of new code. WordPress 2.5 saw a complete overhaul of the administration interface and the WordPress website was also redesigned to match the new style.[32]
2.6	Tyner	15 July 2008	Tyner contained new features that made WordPress a more powerful CMS: you can now track changes to every post and page and easily post from wherever you are on the web.[33]
2.7	Coltrane	11 December 2008	It once again saw the administration interface completely redesigned. It also introduces an automated upgrade feature, and automatic installation of plugins from within the administration interface.[34]
2.8	Baker	10 June 2009	Baker offered improvements in speed, and automatic installation of themes from within the administration interface. It also introduces the CodePress editor for syntax highlighting and a redesigned widget interface.[35]
2.9	Carmen	19 December 2009	Carmen offers a global undo feature, a built-in image editor, batch plugin updating, and numerous under-the-hood tweaks.[36]

[edit] Vulnerabilities

Many security issues^[37][38] were uncovered in the software, particularly in 2007 and 2008. According to Secunia, WordPress in April 2009 had 7 unpatched security advisories (out of 32 total), with a maximum rating of “Less Critical”.^[39]

BlogSecurity maintains a list of WordPress vulnerabilities,^[40] up to version 2.3. Secunia keeps a more recently updated list.^[41]

In January 2007, many high-profile Search engine optimization (SEO) blogs, as well as many low-profile commercial blogs featuring AdSense, were targeted and attacked with a WordPress exploit.^[42] A separate vulnerability on one of the project site’s web servers allowed an attacker to introduce exploitable code in the form of a back door to some downloads of WordPress 2.1.1. The 2.1.2 release addressed this issue; an advisory released at the time advised all users to upgrade immediately.^[43]

In May 2007, a study revealed that 98% of WordPress blogs being run were exploitable because they were running outdated and unsupported versions of the software.^[44]

In a June 2007 interview, Stefen Esser, the founder of the PHP Security Response Team, spoke critically of WordPress’s security track record, citing problems with the application’s architecture that made it unnecessarily difficult to write code that is secure from SQL injection vulnerabilities, as well as some other problems.^[45]

[edit] Multi-blogging

WordPress supports one weblog per installation, although multiple concurrent copies may be run from different directories if configured to use separate database tables.

WordPress Multi-User (WordPress MU, or just WPMU) is a fork of WordPress created to allow simultaneous blogs to exist within one installation. WordPress MU makes it possible for anyone with a website to host their own blogging community, control, and moderate all the blogs from a single dashboard. WordPress MU adds eight new data tables for each blog.

Matt Mullenweg announced that WordPress MU would be merged with WordPress as part of a future release (version 3.0).^[46]

Lyceum is another enterprise-edition of WordPress. Unlike WordPress MU, Lyceum stores all of its information in a set number of database tables. Notable communities that use Lyceum are TeachFor.Us^[47] (Teach For America teachers’ blogs), BodyBlogs and the Hopkins Blogs.

In 2008 Andy Peatling joined Automattic to continue his work on BuddyPress – a plug-in extension of WPMU that is adding additional community features to WordPress.^[48]

[edit] Key developers

WordPress development is led by Ryan Boren and Matt Mullenweg. Mullenweg and Mike Little were co-founders of the project.

The core contributing developers include:

• Dougal Campbell
• Mark Jaquith
• Donncha Ó Caoimh
• Andy Skelton
• Michel Valdrighi
• Peter Westwood

Though largely developed by the community surrounding it, WordPress is closely associated with Automattic, where some of WordPress’s main contributing developers are employees.^[49]

WordPress is also developed by its community, including WP testers, a group of volunteers who test each release. They have early access to nightly builds, beta versions and release candidates. Errors are documented in a special mailing list, or the project’s Trac tool.

History

Kohana was originally created as a project fork^[3] of the CodeIgniter PHP framework under the name Blue Flame. The principal reason for the fork was to create a more community-based web application framework as many users were frustrated with CodeIgniter’s lack of bug fixes and inclusion of new features requested by the community. In July 2007, Blue Flame was renamed to Kohana to avoid possible trademark issues^[4]. The name Kohana was chosen when the developers began looking through Native American dictionaries to find words that would have little copyright conflict. Kohana is the Sioux word for ’swift.’ It is also the Japanese word for ‘tiny flower’ (??), Ukrainian (spelled ??????) and Polish (kochana) word for ‘beloved’ (only of feminine gender) and the name of a famous killer whale (Kohana) — none of which have any relation to the original intended meaning.

While the initial release of Kohana was essentially an improved version of CodeIgniter, by the end of 2007 the Kohana development team had released version 2.0 which was a complete re-write from the ground up. The new version 2.0 was strictly a PHP5 framework and has formed the basis for all other releases since.

Differences between Kohana and CodeIgniter

• Strict PHP5 OOP. Offers many benefits: visibility protection, automatic class loading, overloading, interfaces, abstracts, and singletons.^[5]
• Kohana has joined the GoPHP5 initiative. All releases from 2.2 on will conform with this project.^[5]
• Continues CodeIgniter design patterns. Anyone who has used CodeIgniter will quickly understand Kohana’s structure and design patterns.^[5]
• Community, not company, driven. Kohana is driven by community discussion, ideas, and code. Kohana developers are from all around the world, each with their own talents. This allows a rapid and flexible development cycle that can respond to bugs and requests within hours, instead of days or months.^[5]
• GET, POST, COOKIE, and SESSION arrays all work as expected. Kohana does not limit your access to global data, but offers the same filtering and XSS protection that CodeIgniter does.^[5]
• Cascading resources, modules, and inheritance. Controllers, models, libraries, helpers, and views can be loaded from any location within your system, application, or module paths. Configuration options are inherited and can be dynamically overwritten by each application.^[5]
• No namespace conflicts. Class suffixes, like _Controller, are used to prevent namespace conflicts. This allows a User’s controller and Users model to both be loaded at the same time.^[5]
• True auto-loading of classes. This includes libraries, controllers, models, and helpers. This is not pre-loading, but true dynamic loading of classes, as they are instantiated.^[5]
• Helpers are static classes, not functions. For example, instead of using form_open(), you would use form::open().^[5]
• Library drivers and API consistency. Libraries can use different “drivers” to handle different external APIs transparently. For example, multiple session storage options are available (database, cookie, and native), but the same interface is used for all of them. This allows new drivers to be developed for existing libraries, which keeps the API consistent and transparent.^[5]
• Powerful event handler. Kohana events can by dynamically added to, replaced, or even removed completely. This allows many changes to Kohana execution process, without modification to existing system code.^[5]
• Kohana features a built-in ORM library, whereas CodeIgniter does not.^[6]

Third-party vendors

Release history

Sites using Kohana

Infinity Ward – Kohana V2