We all know that when we’re add a script or style to WordPress, we should use wp_enqueue_script( $handle, $src, $deps, $ver, $in_footer ) and wp_enqueue_style( $handle, $src, $deps, $ver, $media ) as in:

function themeslug_enqueue_style() {
wp_enqueue_style( 'core', 'style.css', array('twentytwelve-style') );
}

function themeslug_enqueue_script() {
wp_enqueue_script( 'my-js', 'filename.js', array('jquery') );
}

add_action( 'wp_enqueue_scripts', 'themeslug_enqueue_style' );
add_action( 'wp_enqueue_scripts', 'themeslug_enqueue_script' )

$deps (dependencies), the handle name and an optional parameter, lets you control when/where your script or style should be added. If $deps is array(‘jquery’), your script will be loaded after jquery is loaded.

The problem is, which one exists and in which order are they loaded ?

I’ve written an add-on to Debug Bar that list the loaded scripts and styles, it’s available at:

• GitHub
• WordPress Plugin Directory

Use

Script and styles loaded on the front-end: Go to the front-end, and on the admin bar choose Debug and view Script & Style Dependencies

Back-end: Do the same, on the admin bar choose Debug and view Script & Style Dependencies

Note, the front-end and back-end loads different scripts and styles. Also, different pages on the front-end and back-end can load different scripts and styles.

Changelog
1.0.2 Added styling
1.0.1 Bugfix, fixed listing of styles and their dependencies
1.0 Initial release

XDebug installation

1. Run the Xdebug wizard and follow the instructions.I develop on Mac OS X Mountain Lion, and phpize complained that autoconf is missing.

   Cannot find autoconf. Please check your autoconf installation and the $PHP_AUTOCONF environment variable is set correctly and then rerun this script.

   Luckily Sebastien has the recipe on how to add autoconf to Mountain Lion

2. When you’re editing php.ini, add the following to the [xdebug] section

   xdebug.remote_enable=On
   xdebug.remote_host="localhost"
   xdebug.remote_port=9000
   xdebug.remote_handler="dbgp"
   xdebug.remote_autostart=1

3. Save php.ini and restart your webserver. I do sudo apachectl restart

Debug your WordPress plugin in Sublime Text 2

1. If you haven’t allready, add the SublimeXdebug package using Sublime Package Control
   • Shift-Cmd P and select Package Install
   • Find Xdebug and install it
2. Open the folder with the plugin you want to debug in Sublime Text and save as project (Project -> Save Project As…)
3. Edit project properties (Project->Edit Project) and add the “settings”: {“xdebug” : url-to-your-test-site}. Mine is:
   

   {
   	"folders":
   	[
   		{
   			"path": "/Users/<user>/Sites/wp.local/wp-content/plugins/acf-field-date-time-picker"
   		}
   	],
   	"settings": {
   		"xdebug": { "url": "http://wp.local/" }
   	}
   }

4. Now you’re ready to debug:
   • Select the line where you want a breakpoint. Shift + F8 opens the debug menu. Select Add Breakpoint
   • Shift + F8, and choose Start debugging. Your default broweser will open with the url you set in project properties. Browse to the page where you know the plugin will be triggered, and go back to Sublime Text.
   • Use the following shortcut keys to step through the code:
     • Ctrl+Shift+F6 – Step over
     • Ctrl+Shift+F7 – Step into
     • Ctrl+Shift+F8 – Step out from
     • Ctrl+Shift+F5 – Continue (until next breakpoint)

I’m, slowly .. literally,

I’ll use the GitHub repositories during development, and publish my plugins in the WordPress Plugin Directory

CloudFlare protects and accelerates any website online. Once your website is a part of the CloudFlare community, its web traffic is routed through our intelligent global network. We automatically optimize the delivery of your web pages so your visitors get the fastest page load times and best performance. We also block threats and limit abusive bots and crawlers from wasting your bandwidth and server resources.
www.cloudflare.com

You’ll find the CloudFlare API at https://www.cloudflare.com/docs/client-api.html

Syntax:

define('CLOUDFLARE_APIEMAIL','emailadr'); // replace emailadr with your api email
define('CLOUDFLARE_APIKEY','abc'); // replace abc with your api key
define('APIURL','https://www.cloudflare.com/api_json.html');

$response = wp_remote_request(APIURL, array(
    'method'    => 'POST',
    'timeout'   => 60,
    'sslverify' => false,
    'body'      => array(
         'email'    => CLOUDFLARE_APIEMAIL
        ,'tkn'      => CLOUDFLARE_APIKEY
        ,'a'        => 'ACTION' // see https://www.cloudflare.com/docs/client-api.html actions ('a') and parameters
        ,'param1'   => ''
        ,'paramN'   => ''
    )
));

if (is_wp_error( $response )) {
   echo 'Something went wrong! <br />';
} else {
    $json = json_decode( wp_remote_retrieve_body($response), true); // true = return an assoc array  
    print_r($json);  
}

Example:

define('CLOUDFLARE_APIEMAIL','emailadr'); // replace emailadr with your api email
define('CLOUDFLARE_APIKEY','abc'); // replace abc with your api key
define('APIURL','https://www.cloudflare.com/api_json.html');

function is_ip_ok($ip) {
    global $errmsg;
    $errmsg = '';
    $response = wp_remote_request(APIURL, array(
        'method' => 'POST',
        'timeout' => 60,
        'sslverify' => false,
        'body' =>  array(
             'email' => CLOUDFLARE_APIEMAIL
            ,'tkn'   => CLOUDFLARE_APIKEY
            ,'a'     => 'ip_lkup'
            ,'ip'    =>  $ip
        )
    ));
    if (is_wp_error( $response )) {
       $errmsg = $response->get_error_message();
       return true; // don't block if is_ip_ok fails
    } else {
        $json = json_decode( wp_remote_retrieve_body($response), true); // true = return an assoc array
        if ($json['result'] != 'success') {
            $errmsg = $json['msg'];
            return true; // don't block if is_ip_ok fails
        } else {
            if ($json['response'][$ip] == "") {
                return true;
            } else {
                return false;
            }
        }
    }
}

I have a test site at AppFog running WordPress. Being the geek I am, I had to test MemCachier (you’ll find it in AppFog Add-Ons)

MemCachier manages and scales clusters of memcache servers so you can focus on your app. Memcache is commonly used to speed up page load time and increase scalability by allowing you to cache expensive database queries and view renders.

Using the Memcached Object Cache source code as a starting point it was rather simple to implement MemCachier, all I had to do was to modify WP_Object_Cache::close(), WP_Object_Cache::flush() and rewrite the WP_Object_Cache constructor (line 4-28):

// WP_Object_Cache constructor
function WP_Object_Cache() {

include_once('plugins/memcachier/MemcacheSASL.php');

global $memcachier_servers;

if ( isset($memcachier_servers) )
$buckets = $memcachier_servers;
else
$buckets = array(
'default' => array(
getenv("MEMCACHIER_SERVERS")
)
);

reset($buckets);

foreach ( $buckets as $bucket => $servers) {
$this->mc[$bucket] = new MemcacheSASL;
foreach ( $servers as $server ) {
list ( $node, $port ) = explode(':', $server);

$this->mc[$bucket]->addServer($node, $port);
$this->mc[$bucket]->setSaslAuthData(getenv("MEMCACHIER_USERNAME"), getenv("MEMCACHIER_PASSWORD"));

}
}

global $blog_id, $table_prefix;
$this->global_prefix = '';
$this->blog_prefix = '';
if ( function_exists( 'is_multisite' ) ) {
$this->global_prefix = ( is_multisite() || defined('CUSTOM_USER_TABLE') && defined('CUSTOM_USER_META_TABLE') ) ? '' : $table_prefix;
$this->blog_prefix = ( is_multisite() ? $blog_id : $table_prefix ) . ':';
}

$this->cache_hits =& $this->stats['get'];
$this->cache_misses =& $this->stats['add'];
}

Installation

The instructions are simple, and although they’re catered specifically for AppFog, the MemCachier WordPress plugin will work in any of our supported partners. As long as you’ve configured the MEMCACHIER_SERVERS, MEMCACHIER_USERNAME, and MEMCACHIER_PASSWORD environment variables, the plugin will work.
MemCachier blog

1. Add MemCachier to your WordPress site at AppFog
2. Install the plugin by copying it to the plugins/memcachier folder
3. Move plugins/memcachier/object-cache.php to wp-content/object-cache.php

Changelog

1.0

• Initial release

Credits

I’ve only changed the WP_Object_Cache constructor, so the credits goes to ryan and sivel for creating the excellent Memcached Object Cache, and ronnywang for PHPMemcacheSASL

Here is my second take on running WordPress and WordPress Multisite locally on my Mac (first is here). I just discovered Pow; ”Pow is a zero-config Rack server for Mac OS X. Have it serving your apps locally in under a minute”, and my first thought was “can I run WordPress on Pow?”.  Well, here’s how I did it (I’ll also show you how to install MySQL, PHP 5.4 and Ruby 1.93 on Mac OS X Mountain Lion):

This guide is work in progress, I’ll keep you updated on twitter

Prerequisite

• Mac OS X Mountain Lion. I did this on a fresh Mac OS X Mountain Lion installation.
• Download and install Command Line Tools (Mountain Lion) for Xcode. If you’re not already registered for a free Mac Developer account, do so.
• Download and install Xquartz so that the png.h header exists for compilation of certain brews. Mountain Lion removes X11, which contained many headers.
• Install Homebrew, “The missing package manager for OS X“. Open Terminal, and from the command line run:

  ruby -e "$(curl -fsSkL raw.github.com/mxcl/homebrew/go)"

There’s going to be a lot of cut and past from now on, but in 15 minutes you’re up and running with WordPress on Pow :).

One by one, copy the commands below and run them in Terminal

MySQL

When you run mysql_secure_installation (line 7 below), answer Y to all the questions.

brew install mysql
unset TMPDIR
mysql_install_db --verbose --user=`whoami` --basedir="$(brew --prefix mysql)" --datadir=/usr/local/var/mysql --tmpdir=/tmp
mkdir -p ~/Library/LaunchAgents
ln -sfv /usr/local/opt/mysql/*.plist ~/Library/LaunchAgents
launchctl load -w ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist
/usr/local/opt/mysql/bin/mysql_secure_installation

Add WordPress database and user to MySQL

mysql -u root -p

mysql> CREATE DATABASE wordpress;
mysql> GRANT ALL PRIVILEGES ON wordpress.* TO wordpress@localhost IDENTIFIED BY 'Pa$$w0rd';
mysql> FLUSH PRIVILEGES;
mysql> EXIT

PHP 5.4

PHP is no longer part of the default Homebrew repository, and hence you need to add the Homebrew-PHP repository. WordPress and Pow only needs mysql and php-cgi. If you’d like to add more features, run brew options php54 from the command line to see the available configurations.

brew tap homebrew/dupes
brew tap josegonzalez/homebrew-php
brew install php54 --with-mysql --with-cgi

Ruby upgraded using rbenv

The default Ruby version on Mountain Lion is a bit old (yepp, that’s an understatement). Pow is a Ruby/Rack web server, and it runs best on the latest version of Ruby. rbenv in combination with ruby-build, allows you to install Ruby in your user space.

brew update
brew install rbenv
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile
echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
source .bash_profile
brew install ruby-build
rbenv install --list
rbenv install 1.9.3-p327
rbenv rehash
rbenv global 1.9.3-p327

Pow and Powder

Pow was created to run Rails/Rack applications, but we want to run legacy applications on Pow (ie PHP / WordPress) and need the rack-legacy rack-rewrite gems.
Pow is easy, but Powder makes it even easier, with a lot of management commands for Pow.

gem install rack-legacy rack-rewrite
gem install powder
rbenv rehash
powder install

WordPress

Ta-da, finally there, just have to grab wget first.
The config.ru file, saved in ~/Sites/config, is a configuration file with rewrite rules (think .htaccess) for WordPress. At the moment it doesn’t support multisite, but I’m working on it. Forked the git below and added support for WordPress Multisite

brew install wget
mkdir ~/Sites
cd ~/Sites
git clone git://gist.github.com/4208560.git config
wget http://wordpress.org/latest.tar.gz
tar zxvf latest.tar.gz
mv wordpress myblog
cd ~/Sites/myblog
ln -s ~/Sites/config/config.ru
powder link
powder open

Adding another WordPress site

Yes, you can :)

cd ~/Sites
tar zxvf latest.tar.gz
mv wordpress myblog2
cd ~/Sites/myblog2
ln -s ~/Sites/config/config.ru
powder link
powder open

WordPress Multisite on Pow

I highly recommend that you create a separate database for your multisite, so let’s do that first

mysql -u root -p

mysql> CREATE DATABASE multisite;
mysql> GRANT ALL PRIVILEGES ON multisite.* TO wordpress@localhost IDENTIFIED BY 'Pa$$w0rd';
mysql> FLUSH PRIVILEGES;
mysql> EXIT

next, install WordPress

cd ~/Sites
tar zxvf latest.tar.gz
mv wordpress multisite
cd ~/Sites/multisite
ln -s ~/Sites/config/config.ru
powder link
powder open

When you’re finished adding your site to the multisite database and it’s up and running, edit multisite/wp-config.php and add the following just above the line reading
/* That’s all, stop editing! Happy blogging. */

/* Multisite */
define('WP_ALLOW_MULTISITE', true);

You will need to refresh your browser to continue, then go to Tools > Network Setup.

In Network Setup, select Sub-domains (more about why, below), fill in the Network Details and click Install. On the next page follow step 1 and 2. You don’t need a .htaccess file, config.ru added above handles rewrites.

Why sub-domains:

In Pow, once a virtual host is installed, it’s also automatically accessible from all subdomains of the named host. For example, the http://multisite.dev/ virtual host added above can also be accessed at http://subdomain.multisite.dev/ and http://blog.multisite.dev/, which is perfect for a WordPress Multisite installation.

“My Permalink Demo” plugin:

<?php
/*
Plugin Name: My Permalink Demo
Plugin URI: http://soderlind.no/archives/2012/11/01/wordpress-plugins-and-permalinks-how-to-use-pretty-links-in-your-plugin/
Description: Demo plugin to show how to implement your custom permalink for your plugin. To test, add the [mypermalink] or [mypermalink val="ipsum"] shortcode to a page or post.
Version: 1.0.1
Author: Per Soderlind
Author URI: http://soderlind.no/
*/

if (!class_exists('my_permalink')) {
    class my_permalink {

        function __construct(){
            // demo shortcode
            add_shortcode('mypermalink', array(&$this,'my_permalink_demo_shortcode'));

            // permalink hooks:
            add_filter('generate_rewrite_rules', array(&$this,'my_permalink_rewrite_rule'));
            add_filter('query_vars', array(&$this,'my_permalink_query_vars'));
            add_filter('admin_init', array(&$this, 'my_permalink_flush_rewrite_rules'));
            add_action("parse_request", array(&$this,"my_permalink_parse_request"));
        }

        /**************************************************************************
         * Demo shortcode
         * A simple shortcode used to demonstrate the plugin.
         *
         * @see http://codex.wordpress.org/Shortcode_API
         * @param array $atts shortcode parameters
         * @return string URL to demonstrate custom permalink
         **************************************************************************/
        function my_permalink_demo_shortcode($atts) {
            extract(shortcode_atts(array(
                // default values
                'val'       =>   'lorem'
            ), $atts));
            return sprintf('<a href="%s">My permalink</a>',$this->my_permalink_url($val));
        }

        /**************************************************************************
         * Create your URL
         * If the blog has a permalink structure, a permalink is returned. Otherwise
         * a standard URL with param=val.
         *
         * @param sting $val Parameter to custom url
         * @return string URL
         **************************************************************************/
        function my_permalink_url($val) {
            if ( get_option('permalink_structure')) { // check if the blog has a permalink structure
                return sprintf("%s/my-permalink/%s",home_url(),$val);
            } else {
                return sprintf("%s/index.php?my_permalink_variable_01=%s",home_url(),$val);
            }
        }

        /**************************************************************************
         * Add your rewrite rule.
         * The rewrite rules array is an associative array with permalink URLs as regular
         * expressions (regex) keys, and the corresponding non-permalink-style URLs as values
         * For the rule to take effect, For the rule to take effect, flush the rewrite cache,
         * either by re-saving permalinks in Settings->Permalinks, or running the
         * my_permalink_flush_rewrite_rules() method below.
         *
         * @see http://codex.wordpress.org/Custom_Queries#Permalinks_for_Custom_Archives
         * @param object $wp_rewrite
         * @return array New permalink structure
         **************************************************************************/
        function my_permalink_rewrite_rule( $wp_rewrite ) {
            $new_rules = array(
                 'my-permalink/(.*)$' => sprintf("index.php?my_permalink_variable_01=%s",$wp_rewrite->preg_index(1))
                 /*
                 // a more complex permalink:
                 'my-permalink/([^/]+)/([^.]+).html$' => sprintf("index.php?my_permalink_variable_01=%s&my_permalink_variable_02=%s",$wp_rewrite->preg_index(1),$wp_rewrite->preg_index(2))
                 */
            );

            $wp_rewrite->rules = $new_rules + $wp_rewrite->rules;
            return $wp_rewrite->rules;
        }

        /**************************************************************************
         * Add your custom query variables.
         * To make sure that our parameter value(s) gets saved,when WordPress parse the URL,
         * we have to add our variable(s) to the list of query variables WordPress
         * understands (query_vars filter)
         *
         * @see http://codex.wordpress.org/Custom_Queries
         * @param array $query_vars
         * @return array $query_vars with custom query variables
         **************************************************************************/
        function my_permalink_query_vars( $query_vars ) {
            $query_vars[] = 'my_permalink_variable_01';
            /*
            // need more variables?:
            $query_vars[] = 'my_permalink_variable_02';
            $query_vars[] = 'my_permalink_variable_03';
            */
            return $query_vars;
        }

        /**************************************************************************
         * Parses a URL into a query specification
         * This is where you should add your code.
         *
         * @see http://codex.wordpress.org/Query_Overview
         * @param array $atts shortcode parameters
         * @return string URL to demonstrate custom permalink
         **************************************************************************/
        function my_permalink_parse_request($wp_query) {
            if (isset($wp_query->query_vars['my_permalink_variable_01'])) { // same as the first custom variable in my_permalink_query_vars( $query_vars )
                // add your code here, code below is for this demo
                printf("<pre>%s</pre>",print_r($wp_query->query_vars,true));
                exit(0);
            }
        }

        /**************************************************************************
         * Flushes the permalink structure.
         * flush_rules is an extremely costly function in terms of performance, and
         * should only be run when changing the rule.
         *
         * @see http://codex.wordpress.org/Rewrite_API/flush_rules
         **************************************************************************/
        function my_permalink_flush_rewrite_rules() {
            $rules = $GLOBALS['wp_rewrite']->wp_rewrite_rules();
            if ( ! isset( $rules['my-permalink/(.*)$'] ) ) { // must be the same rule as in my_permalink_rewrite_rule($wp_rewrite)
                global $wp_rewrite;
                $wp_rewrite->flush_rules();
            }
        }
    } //End Class
} //End if class exists statement

if (class_exists('my_permalink')) {
    $my_permalink_var = new my_permalink();
}
?>

How to test the “My Permalink Demo” plugin

• Save the code above as wp-content/plugins/ps_my_permalink.php
• Activate the “My Permalink Demo” plugin
• add the [mypermalink] or [mypermalink val="ipsum"] shortcode to a page or post

Tools

• Debugging permalink errors is hard, I highly recommend Rewrite Analyzer (it helped me).

Changelog

1.0.2

• Thanks to Paul, the plugin now only flushes the rewrite rules when needed.

1.0.1

• Fixed a bug in my_permalink_url() that gave 404 for blogs in a subdirectory

1.0.0

• Initial release

You don’t need this fix any more, the latest version works with multi site.

2.0 WARNING: Old settings will not be retained
Changelog

Here’s a quick fix (test it before deploying to production) that lets you use the cbnet Multi Author Comment Notification 1.1.2 plugin in a WordPress multisite environment:

Replace:

$user_array = array();
$query = "SELECT ID FROM $wpdb->users";
$result = $wpdb->get_results($query, ARRAY_A);
foreach ( (array)$result as $key=>$row ) {
$data = get_userdata($row['ID']);
$data->wp_user_level = intval($data->wp_user_level);
$userid = $data->ID;
$username = $data->user_login;
$fullname = $data->first_name.' '.$data->last_name;
$email = $data->user_email;
$level = @key($data->wp_capabilities);
$user_array[$data->wp_user_level][] = array($userid, $username, $fullname, $email, $level);
}

With:

$user_array = array();
$get_users_args = array(
'blog_id' => get_current_blog_id()
);
$current_blog_base_prefix = (is_multisite()) ? $wpdb->base_prefix . get_current_blog_id() . '_' : $wpdb->base_prefix;
$result = get_users($get_users_args);
foreach ($result as $row) {
$data = get_userdata($row->ID);
$data->wp_user_level = intval(get_user_meta($row->ID, $current_blog_base_prefix . 'user_level',true));
$userid = $data->ID;
$username = $data->user_login;
$fullname = $data->first_name.' '.$data->last_name;
$email = $data->user_email;
$level = @key(get_user_meta($row->ID, $current_blog_base_prefix . 'capabilities',true));
$user_array[$data->wp_user_level][] = array($userid, $username, $fullname, $email, $level);
}

Provided as-is, aka not supported (yet)

Please use the comments field below if you find bugs, typos etc.

Features

• Settings page (Settings->Read Offline)
• Read Offline widget (output shown in the image above)
• Read Offline shortcode
• You can download a pdf, epub or mobi file containing the current post or page (you have to add the Read Offline widget to see the download links)
• The download filename is based on the posts slug ($post->post_name)
• Adds meta data to the file
  • Title (PDF, ePub and mobi)

    $post->post_title

  • Author (PDF, ePub and mobi)

    get_the_author_meta('display_name',$post->post_author)

  • Subject (mobi)

    implode(' ,',array_map("get_cat_name", wp_get_post_categories($post->ID)))

  • Publisher (ePub)

    setPublisher(get_bloginfo( 'name' ), get_bloginfo( 'url' ))

  • Identifier (uPub)

    $post->guid

  • Source URL (ePub)

    $post->guid

  • Language (ePub)

    $iso6391 = ( '' == get_locale() ) ? 'en' : strtolower( substr(get_locale(), 0, 2) );

• Option: Add download links to the top and bottom of a post or page.
• Permalink support (/read-offline/”postid”/”post-name”.”type”). I’ve written a how-to add permalink to plugins guide.
• Option: Add a custom style to the ePub and PDF file
• Option: Google Analytics read-offline event tracking. You can find these under Content » Events in your Google Analytics reports. Assumes you’re using the Asynchronous version of Google Analytics.
• languages/read-offline.po for easy translation.

To-do / Wish List

• Bookmark posts
• Export post / page as Word (.docx)
• Add unique headers/footers
• more ? Please post a comment if you have any suggestions

Use

There are 3 ways you can add the Read Offline link

1. At the top or bottom of each post and/or page (See Settings->Read Offline)
2. Using the Read Offline widget
3. Using the [readoffline] shortcode

The [readoffline] shortcode has the following parameters

• format=”epub”, default: format=”pdf,epub,mobi”
• text=”Read %title offline:”, default: text=”". %title% will be replaced with the post or page title
• icononly=”true”, default=”false”

Examples

• [readoffline] is the same as [readoffline text="" format="pdf,epub,mobi" icononly="false"]
• [readoffline text="Download %title%:" format="epub"]

Credits:

The plugin is using the following libraries

• Epub , License: GNU LGPL, Attribution required for commercial implementations, requested for everything else.
• Zip, License: GNU LGPL, Attribution required for commercial implementations, requested for everything else.
• phpMobi, License: Apache license (version 2.0)
• mpdf, License: GNU General Public License version 2

The plugin is using the following icons

• PDF icon from the Fugue Icons set by Yusuke Kamiyamane, released under a Creative Commons attribution license
• ePub and mobi icons by Doug Smith, also released under a Creative Commons attribution license

Changelog

0.1.9

• Fixed a bug in permalinks that gave 404 for blogs in a subdirectory. Also removed code that gave error when downloading an ePub.

0.1.8

• Added Google Analytics read-offline event tracking. You can find these under Content » Events in your Google Analytics reports. Assumes you’re using the Asynchronous version of Google Analytics

0.1.7

• Minor bug fix

0.1.6

• Added the option to add custom css to PDF

0.1.5

• In Settings->Read Offline, added the option to add custom css to EPub
• Added languages/read-offline.po for easy translation.

0.1.4

• Added permalink support (/read-offline/”postid”/”post-name”.”type”). I’ve written a how-to add permalink to plugins guide
• removed the obsolete download.php

0.1.3

• epub will now validate against http://www.epubconversion.com/ePub-validator-iBook.jsp
• Added language variable to the epub file, ISO 639-1 two letter tag based on the WordPress get_locale()

0.1.2

• Fix typo in download.php, was including  ”Epub.inc.php”,  correct is “EPub.inc.php”

0.1.1

• Bugfix, v0.1.0 will give you “gray screen of death”, so please upgrade to this version

0.1.0

• Added the Read Offline shortcode
• Added, in Settings->Read Offline, option to add Read Offline to top and/or bottom of post and page

0.0.2

• Filename based on the posts slug
• Added meta data

0.0.1

• Initial release

Here’s an example I’ve created. This is still very beta, the table.php I’ve written is based upon the Custom List Table Example plugin, and I haven’t created the class-piklist-table.php backend yet:

The following piklist array:

Creates this table:

If I have whet your appetite and you want to learn more about Piklist, start with the WordCamp NYC 2012 presentation (coding starts 13 minutes into the presentation):

After you’ve viewed the presentation, read the Piklist tutorials and documentation.