1. Use the development branch

I’m not using the Package Control version of SublimeCodeIntel (I’ve looked at the version numbers and they are the same, but I couldn’t get it to work). Instead, I’m using a Git checkout of the development branch.

In the Sublime Text menu, go to Preferences -> Browse Packages. From this directory I ran the command:

git clone -b development git@github.com:SublimeCodeIntel/SublimeCodeIntel.git

2. Clear your codeintel cache

Your codeintel cache probably needs clearing if, like me, you’ve had older versions of SublimeCodeIntel installed.

To do this, quit Sublime Text then go to your home directory and delete the entire .codeintel directory (eg. on OS X this is at ~/.codeintel). If you have a config file in there that you’ve made changes to, back it up first.

3. Fix the language-specific config

This appears to have been the key problem for me. Inexplicably, SublimeCodeIntel’s default config disables project scanning for PHP and JavaScript files. Why? Who knows.

To fix it, open the Sublime Text menu and go to Preferences -> Package Settings -> SublimeCodeIntel -> Settings – Default. At the bottom of this file are language-specific settings for Python, JavaScript, and PHP.

Do not edit this config directly. Instead copy its contents completely and paste it into your user settings (Preferences -> Package Settings -> SublimeCodeIntel -> Settings – User). Then delete the PHP and JavaScript settings from the bottom, or at least change the codeintel_scan_files_in_project settings to true.

4. Be patient

When you first begin typing a function name or other entity that triggers codeintel, the status bar will show you that the initial scan is taking place. I’ve noticed that this status message disappears before scanning is actually complete, or it’ll state that scanning is complete when it’s not. Be patient, and it will get there eventually.

I decided to generate a GeoJSON file of the contributor’s locations so it can be displayed wherever and however the open GeoJSON format is supported, not least on GitHub which recently added support for automatic rendering of GeoJSON files.

In order to get the location data for each contributor I would need to scrape it from wordpress.org. In my simple Node script I started by using Node’s HTTP interface to fetch the 3.6 announcement blog post. The content of the post was then loaded into Cheerio which provides a wonderful implementation of jQuery’s core for working with the DOM, and used this to find the list of links in the blog post to wordpress.org profile pages.

Next step was to loop over each profile URL and fetch the page in order to pluck out the location data from the map shown for each user. With 225 contributors, it was clear this was going to be slow. Luckily the async module provides a super simple method for asynchronous iteration, so I used that to asynchronously fetch the profile pages.

The next step was to pluck out the user’s location from the markup using a straight forward regex, and then send this off to Google’s Geocoding API in order to get us the geographic coordinates we’d need. Out of the 225 contributors, 61 didn’t have their location displayed on their profile page.

The final step was to load all the data into the GeoJSON.js module in order to give us a valid GeoJSON file, and then pretty print it using the native JSON.stringify method.

Here’s the end result:

You can find the Node JavaScript in the GitHub repo if you’re interested.

Unfortunately the release announcements have only listed the contributors since version 2.9 (June 2009). If anyone wants to get me the list of contributors for earlier versions I’ll happily update this post. It’d be interesting to see the numbers over the years.

Contributors by Version

Version 3.0 has so far seen the highest number of individual contributors. The latest version – 3.4 – comes in second with 187. I thought I might see a steady increase with each version, but this is not the case, and we’ll see why below.

Also shown is the number of Trac tickets closed with each version. There’s a noticable reduction in the number of tickets closed since version 3.0 which closed over 1,200 tickets, with recent releases closing fewer than half that number. This correlates nicely with the recent drive to clearly define the scope of each release. We can probably all agree that Jane Wells is to thank for playing a big part in keeping WordPress releases on schedule recently.

Version Involvement

WordPress sees long-term involvement from many people. Almost two hundred people have contributed to at least two different versions of WordPress since 2.9. The list got a bit long, so below I’ve listed the 120 people who have contributed to at least three out of the six versions released. While it’s not a good indication of the level of contributions by each person, it does demonstrate active involvment and an ongoing commitment.

Total Contributors

WordPress has seen 541 individual contributors over the three years and six versions since 2.9 in July 2009.

And Finally

It’s unfortunate that it’s not as simple to measure the involvement of all those people who contribute to WordPress in ways other than Trac tickets and patches. There are literally hundreds of people who spend their time helping others on the support forums and mailing lists, those who organise and attend WordCamps and WordPress meetups, and those who build and release plugins & themes. Without those people, the almost ten thousand improvements to WordPress wouldn’t be so useful.

Stats Elsewhere

A few other people have previously generated stats regarding contributors to WordPress. If you know of any more articles on contributor stats, leave a comment and I’ll add them to the list.

• Andrew Nacin’s Visualizing the WordPress 3.0 contributors (2010)
• Peter Westwood’s WordPress 2.5 Contributors (2008)
• Richard Ozh’s WordPress Bug Fixers Heat Map (2007)

Latest version: 1.0- Released June 15th, 2012:

• Initial release.

Description

This plugin allows you to display Pocket 'Read It Later' links next to each post on your blog. You can see an example on the Pocket blog. You can automatically insert the links adjacent to your blog posts or you can use the template tag to insert the links wherever you like.

What the hell is Pocket?

From getpocket.com:

Pocket (formerly Read It Later) helps people who discover an interesting article, video or web page, but don’t have time to view it. Once saved to Pocket, the list of content is visible on any device — phone, tablet or computer. It can be viewed while waiting in line, on the couch or during commutes or travel — even offline.

Check out getpocket.com for all the details and to sign up.

Installation

You can install this plugin directly from your WordPress dashboard:

1. Go to the Plugins menu and click Add New.
2. Search for Pocket Read It Later Links.
3. Click Install Now next to the Pocket Read It Later Links plugin.
4. Activate the plugin.

Alternatively, see the guide to Manually Installing Plugins.

Once activated, check out the front page of your blog. A ‘Read It Later’ link will now show adjacent to each post.

Usage

By default, this plugin adds a ‘Read It Later’ link adjacent to each blog post on your blog. You can control where the ‘Read It Later’ links show up by going to the Settings -> Pocket Links menu in WordPress.

Download

This plugin requires WordPress version 3.3 or later. Tested up to 3.4.2.

Version 1.0 ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

For each of our meta fields, we’ll need to do three things:

1. Store a revision of the meta field when a post is saved
2. Revert to the correct revision of the meta field when a post is reverted
3. Optionally, display the meta field on the revisions screen

In the code below I’m just saving revisions to one meta field, ‘my_meta’. You can of course save revisions to more than one meta field by looping over a list of fields your plugin uses.

Sorry about the poor code formatting in this article. I really need to fix the CSS on my site.

Storing a revision of the meta field when a post is saved

For this we hook into the save_post action and save the post meta data only if the post being saved is a revision. We need to use the low level add_metadata() function because if we use add_post_meta() then the meta data will be stored against the post instead of the revision.

function my_plugin_save_post( $post_id, $post ) {

	$parent_id = wp_is_post_revision( $post_id );

	if ( $parent_id ) {

		$parent  = get_post( $parent_id );
		$my_meta = get_post_meta( $parent->ID, 'my_meta', true );

		if ( false !== $my_meta )
			add_metadata( 'post', $post_id, 'my_meta', $my_meta );

	}

}
add_action( 'save_post', 'my_plugin_save_post' );

Reverting to the correct revision of the meta field when a post is reverted

For this we hook into the wp_restore_post_revision action and update the meta field to the version stored at the revision we’re reverting to. Again we’re using the low level get_metadata() function instead of get_post_meta() so we can grab the meta data from the revision instead of the current post.

function my_plugin_restore_revision( $post_id, $revision_id ) {

	$post     = get_post( $post_id );
	$revision = get_post( $revision_id );
	$my_meta  = get_metadata( 'post', $revision->ID, 'my_meta', true );

	if ( false !== $my_meta )
		update_post_meta( $post_id, 'my_meta', $my_meta );
	else
		delete_post_meta( $post_id, 'my_meta' );

}
add_action( 'wp_restore_post_revision', 'my_plugin_restore_revision', 10, 2 );

Displaying the meta field on the revisions screen

For this we need to hook into the _wp_post_revision_fields action to tell WordPress which fields to show on the revisions screen, and hook into the _wp_post_revision_field_my_meta filter to display the meta field. Note that the filter name is specific for each field, so you’ll need to add a hook for each of your meta fields in the format _wp_post_revision_field_{field_name}.

function my_plugin_revision_fields( $fields ) {

	$fields['my_meta'] = 'My Meta';
	return $fields;

}
add_filter( '_wp_post_revision_fields', 'my_plugin_revision_fields' );

function my_plugin_revision_field( $value, $field ) {

	global $revision;
	return get_metadata( 'post', $revision->ID, $field, true );

}
add_filter( '_wp_post_revision_field_my_meta', 'my_plugin_revision_field', 10, 2 );

Putting it all together

Download the example code as a plugin here.

You’ll need to manually add/edit the ‘my_meta’ field using the Custom Fields panel on the post editing screen, then you can play around with viewing and reverting revisions.

Some considerations

The code used to display the meta field on the revisions screen will generate a PHP notice because WordPress looks for the my_meta element of the post object before calling the field callback function. There’s a ticket on Trac somewhere about improvements to the revisions screen but I can’t find it currently.

When you compare two post revisions using the compare functionality on the revisions screen the meta fields won’t be taken into account. Again, the revisions screen in WordPress needs some improvements in this area.

Make sure your device is connected to the same network as your development machine. Go into the Settings -> Wi-Fi menu and find the HTTP proxy settings. On Android, this means a long-press on your Wi-Fi network (Modify Settings, then Show advanced settings). On iOS this means pressing the (i) icon next to your Wi-Fi network.

Switch your proxy over to ‘Manual’ and enter your development environment machine’s network IP address (eg. 192.168.0.4) as the server, and 8888 as the port (Charles’ default port unless you’ve changed it).

Voila. All your HTTP traffic from your device will now route through your host machine (Charles will prompt you to allow access first) and you’ll have access to your local development server. Awesome!

Pro Tip: Are you still editing your hosts file in order to manage the host name mapping for sites on your development environment? Stop it. Just use the Tools -> DNS Spoofing menu in Charles and make life easier for yourself.

Fear not though, it’s really easy. Here’s how:

$args = array(
'headers' => array(
'Authorization' => 'Basic ' . base64_encode( YOUR_USERNAME . ':' . YOUR_PASSWORD )
)
);
wp_remote_request( $url, $args );


That’s it. The correct authentication headers will then be sent with your request (after you’ve replaced YOUR_USERNAME and YOUR_PASSWORD with the obvious).

I’d like to give a quick shout out to my favourite HTTP monitor Charles Proxy. I use Charles almost daily when dealing with server-side HTTP requests and AJAX requests and it makes life much easier. I love it.

• Bugfix for the Get The Image plugin integration.

Description

This plugin simply adds your post thumbnails to your feed as RSS enclosures. Nothing else to it. If you don't use thumbnails or you don't know what enclosures are or why you might want them, then this probably isn't for you.

The plugin supports the Post Thumbnail feature built into WordPress and the Get The Image plugin by Justin Tadlock.

Installation

1. Unzip the ZIP file and drop the folder straight into your wp-content/plugins/ directory.
2. Activate the plugin through the 'Plugins' menu in WordPress.
3. View your feed (you might need to do a hard refresh - ctrl+reload) and any posts that have a thumbnail defined will have an enclosure containing a link to the thumbnail.

Download

This plugin requires WordPress version 2.9 or later.

Version 1.2 ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

It’s not easy to do. (We’re talking about the web interface here, it’s undoubtedly easy for those who use Twitter clients.) This is why I’ve written the Twitter Conversation Bookmarklet.

Update: This bookmarklet is now a web service by me. Check out Twitlr!

Installation

Drag the following link to your browser’s Bookmarks Toolbar:

[twitter conversation]

Usage

Simply press the bookmarklet whenever you’re on a Twitter status page that is part of a conversation, and the entire conversation will be magically loaded onto the page.

Example

The best way to see an example is just to install the bookmarklet and then hit it on a status page. An example status where it works well is this recent tweet by Damien Mulley which is part of a conversation.

Known Issues

• Currently, the bookmarklet won’t return a conversation if you use it on the first tweet that is part of a conversation. It must be used on a tweet that is replying to another. This appears to be a limitation of the Twitter API but I am looking into ways to work around this.

Comments and bug reports appreciated.

All the information for this plugin can be found over at the WordPress Plugin Directory: Disable WordPress Theme Updates.

Don’t forget you can also disable WordPress core updates and disable WordPress plugin updates too.

Description

There is no built-in way for your visitors to "log out" of password protected posts once they've entered the password. Even logged in users cannot log out of password protected posts by logging out of their account. This plugin solves that problem by providing a link for your visitors to log out of password protected posts.

After installing the plugin, add <?php do_action('posts_logout_link'); ?> somewhere in your theme to display a link for logging out of password protected posts.

Installation

You can install this plugin directly from your WordPress dashboard:

1. Go to the Plugins menu and click Add New.
2. Search for Logout Password Protected Posts.
3. Click Install Now next to the Logout Password Protected Posts plugin.
4. Activate the plugin.
5. Add <?php do_action('posts_logout_link'); ?> somewhere in your theme.

Those people who are logged in to password protected posts will now see a link to log out.

For manual installation, see the guide to Manually Installing Plugins.

FAQ

I can't see a link to log out. What's up?

Have you added the template tag somewhere in your theme? You need to add <?php do_action('posts_logout_link'); ?> somewhere in your theme for the link to show up.

I've added the template tag to my theme but I can't see the log out link. What's up?

Ensure that you have entered a password for a password protected post. The link will not show up if you're not logged into a password protected post.

Can I change the default text in the link?

Sure. Add a second parameter to the template tag with the text you'd like instead. For example: <?php do_action('posts_logout_link','Log out!'); ?>

For those who want even more control, you can also add a third paramter which will be used as the class name on the link element.

Download

Version 0.2 ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

• Correctly encode the redirect_to parameter in the login screen message.

Description

This plugin allows you to quickly swap between user accounts in WordPress at the click of a button. You'll be instantly logged out and logged in as your desired user. This is handy for test environments where you regularly log out and in between different accounts, or for adminstrators who need to switch between multiple accounts.

Features

• Switch user: Instantly switch to any user account from the Users screen.
• Switch back: Instantly switch back to your originating account.
• Switch off: Log out of your account but retain the ability to instantly switch back in again.
• It's completely secure (see the Security section below).
• Compatible with WordPress, WordPress Multisite, BuddyPress and bbPress.

Security

• Only users with the ability to edit other users can switch user accounts. By default this is only Administrators on single site installs, and Super Admins on Multisite installs.
• Passwords are not (and cannot be) revealed.
• Implements WordPress' nonce security system, meaning only those who intend to switch users can switch.
• Full support for administration over SSL (if applicable).

Usage

1. Visit the Users menu in WordPress and you'll see a Switch To link next to each user.
2. Click this and you will immediately switch into that user account.
3. You can switch back to your originating account via the Switch back link on each dashboard screen or in your profile menu in the WordPress toolbar.

See the FAQ for information about the Switch Off feature.

Translations Included

• Arabic by Hassan Hisham
• Chinese Simplified by Tunghsiao Liu
• Farsi (Persian) by Amin Ab
• German by Ralph Stenzel
• Japanese by Yusuke Hayasaki
• Lithuanian by Tommixoft
• Polish by Bartosz Arendt
• Russian by R J
• Slovak by Max Samael

Screenshots

Installation

If you have the WordPress Developer plugin installed then User Switching is a one-click install from the Tools -> Developer screen.

Alternatively, you can install this plugin directly from your WordPress dashboard:

1. Go to the Plugins menu and click Add New.
2. Search for User Switching.
3. Click Install Now next to the User Switching plugin.
4. Activate the plugin.

FAQ

What does "Switch off" mean?

Switching off logs you out of your account but retains your user ID in an authorisation cookie so you can switch straight back without having to log in again manually. It's akin to switching to no user, and being able to switch back.

The Switch Off link can be found in your profile menu in the WordPress toolbar. Once you've switched off you'll see a Switch back link in the footer of your site.

Does this plugin work with WordPress Multisite?

Yes, and you'll also be able to switch users from the Users screen in Network Admin.

Does this plugin work with BuddyPress?

Yes, and you'll also be able to switch users from member profile screens and the member listing screen.

Does this plugin work with bbPress?

Yes, and you'll also be able to switch users from member profile screens.

Does this work as a mu-plugin?

Yes, but you'll need to install user-switching.php into the root of your mu-plugins directory, not in the user-switching subdirectory. This is a restriction of WordPress.

What capability does a user need in order to switch accounts?

A user needs the edit_users capability in order to switch user accounts. By default only Administrators have this capability, and with Multisite enabled only Super Admins have this capability.

Can regular admins on Multisite installs switch accounts?

No. This can be enabled though by installing the User Switching for Regular Admins plugin.

Are any plugin hooks called when users switch accounts?

Yes. When a user switches to another account, the switch_to_user hook is called with the new and old user IDs passed as parameters.

When a user switches back to their original account, the switch_back_user hook is called with the new (original) and old user IDs passed as parameters. Note that the old user ID can be boolean false if the user is switching back after they've been switched off.

When a user switches off, the switch_off_user hook is called with the old user ID as a parameter.

Download

This plugin requires WordPress version 3.1 or later.

Download the plugin on WordPress.org.

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

• Update to the new style button from Instapaper. The original black version no longer works.

Description

This plugin allows you to display Instapaper ‘Read later’ links next to each post on your blog just like on Give Me Something To Read. You can either automatically insert the links adjacent to your blog entries, or you can just use the template tag to insert the links wherever you like.

What the hell is Instapaper?

From instapaper.com:

Instapaper is a fast, easy, free tool to save web pages for reading later. When you find something you want to read, but you don’t have time now, you click ‘Read Later’. When you do have time to read, you visit Instapaper on your computer or phone and get whatever you wanted to read.

Check out instapaper.com for all the details and to sign up.

Can I see an example?

See some screenshots here.

Installation

1. Unzip the ZIP file and drop the folder straight into your ‘wp-content/plugins-’ directory.
2. Activate the plugin through the ‘Plugins’ menu in WordPress.
3. Check out the front page of your blog. A ‘Read Later’ link will now show adjacent to each post.

Usage

By default, this plugin displays a ‘Read Later’ link adjacent to each blog entry on your blog. If you wish to control where the links are displayed, you can go to the Settings -> Read Later Links menu and choose between a few display options.

If you choose to disable automatic placement, you’ll need to add the following code to your theme in order insert the ‘Read Later’ link for each post:

<?php do_action('read_later'); ?>

The code must be inside the WordPress loop.

Thanks

• Marco Arment for making Instapaper

Download

This plugin requires WordPress version 2.7 or later. Tested up to 3.4.2.

Version 1.2 ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

• Remove some now-redundant processing of the screenshot URLs.

Description

This plugin provides a simple way of displaying up-to-date information about specific plugins hosted on the WordPress Plugin Directory in your blog posts and pages. It is intended for plugin authors who want to display details of their own plugins from the WP Plugin Directory on their blog and want those details to remain up to date. It’s also useful for bloggers who may blog about plugins and would like the details in their blog posts to remain up to date.

Er, what?

You want to blog about a particular plugin on your blog and include various details of it in your blog post (eg. the number of downloads or the last updated date). You could manually type this information into your post but this means that in a few days/weeks/months’ time the information will be out of date.

This plugin allows you to use shortcodes in your blog posts and pages which fetches this information right from the WordPress Plugin Directory, therefore ensuring the information always remains up to date.

Here’s an example

This plugin uses shortcodes so it’s ridiculously easy to include any information about a particular plugin in your post or page:

This plugin has been downloaded [plugin downloaded] times!

This will produce the following content in your blog post:

This plugin has been downloaded 1,650 times!

The download count will remain current without you having to touch your blog post again.

Is this plugin for me?

This plugin is only going to be of use to you if:

1. You are a plugin author and you want a ridiculously easy way to include up to date information about any of your plugins in your blog posts or pages.
2. You are the author of a blog that highlights plugins of interest and you want to ensure that information in your posts remains up to date.

Installation

1. Unzip the ZIP file and drop the folder straight into your wp-content/plugins directory.
2. Activate the plugin through the ‘Plugins’ menu in WordPress.
3. Now read the usage guidelines below.

Usage

1. Write a new blog post or page, or open an existing post or page for editing.
2. In the ‘Plugin Info’ box on that screen, type the slug of the plugin like this:
   
   (The plugin slug is the last part of the URL of the plugin’s page on wordpress.org.)
3. Add a shortcode to your blog entry like this: [plugin downloaded] and save the post. (That’s the word ‘plugin’ and not the slug of your plugin by the way).
4. Take a look at your post and the number of dowloads of the plugin will be displayed.

Which attributes can I display?

Below is a list of all the available shortcodes.

Plain info:

• [plugin author_name] – The plugin author’s name
• [plugin author_url] – The URL of the plugin author’s homepage
• [plugin compatibility] – The compatibility concensus with the most recent version of WordPress (as a %)
• [plugin compat_with] – The version of WordPress used for the compatibility concensus (ie. the latest WordPress version, eg. “2.8.5″)
• [plugin download_url] – The URL of the plugin’s ZIP file
• [plugin donate_url] – The URL of the plugin’s donation page
• [plugin downloaded] – The all time download count with comma-separated thousands (eg. “12,345″)
• [plugin homepage_url] – The URL of the plugin’s homepage
• [plugin link_url] – The URL of the plugin’s page on the WP Plugin Directory
• [plugin name] – The plugin name
• [plugin profile_url] – The URL of the author’s profile on WP.org
• [plugin requires] – The ‘Requires at least’ WP version number
• [plugin rating] – The plugin’s star rating as a whole number out of 5 (given by visitors to wp.org)
• [plugin slug] – The plugin slug
• [plugin tags] – A comma-separated list of the plugin’s tags
• [plugin tested] – The ‘Tested up to’ WP version number
• [plugin updated_ago] – How long ago the plugin was last updated (eg. “20 days ago”)
• [plugin updated] – The date the plugin was last updated, formatted according to your Date Format settings under Settings->General (eg. “20 January 2009″)
• [plugin version] – The plugin version number

Formatted info (eg. links and ordered lists):

Most shortcodes which display a formatted link can have their default link text overridden by adding a ‘text’ parameter. For example: [plugin homepage text=’Homepage’] will display a link to the plugin homepage with the link text ‘Homepage’.

• [plugin author] – A formatted link to the plugin author’s homepage with the author’s name as the link text (if the author doesn’t have a homepage this will just display their name)
• [plugin description] – The full description of the plugin
• [plugin download] – A formatted link to the plugin’s ZIP file with ‘Download’ as the link text
• [plugin donate] – A formatted link to the plugin’s donation page with ‘Donate’ as the link text
• [plugin homepage] – A formatted link to the plugin’s homepage with ‘Visit plugin homepage’ as the link text
• [plugin link] – A formatted link to the plugin’s page on the WP Plugin Directory with the plugin name as the link text
• [plugin profile] – A formatted link to the author’s WP.org profile page with the author’s name as the link text
• [plugin screenshots] – The list of the screenshots attached to the plugin (an <ol> list of <img> tags with descriptions)
• [plugin changelog] – The list of changelog entries
• [plugin latest_change] – Just the latest changelog entry
• [plugin other_notes] – The ‘Other Notes’ section of the plugin

Some less useful raw data:

• [plugin downloaded_raw] – The all time download count as a raw number (eg. “12345″)
• [plugin num_ratings] – The number of people who’ve rated the plugin on wp.org
• [plugin rating_raw] – The plugin’s actual average rating as a score out of 100 (given by visitors to wp.org)
• [plugin updated_raw] – The date the plugin was last updated, in the format “yyyy-mm-dd”

The geek stuff

The plugin information is collected from wp.org each time you save your post or page. It is updated hourly using WordPress’ cron system and uses the Plugin API available in WordPress 2.7 or later. The plugin data is stored as an associative array in a custom field called ‘plugin-info’, and the plugin slug you enter is saved as a custom field called ‘plugin’. For supergeeks, this means you can also access the plugin data using get_post_meta(), but I’ll let you figure that out for yourself.

Todo list

• A shortcode for a standard information box which contains all the essential plugin info in a nice format.
• Possibly allow shortcodes in the title of posts.
• Clickable shortcoces listed on the post editing screen.
• A shortcode for a link to the author’s wordpress.org profile page (pending support in the Plugin API).
• A shortcode for the ‘Other Notes’ section of the plugin (pending support in the Plugin API).
• A simple UI for adding the plugin slug info to posts so you don’t have to use the Custom Fields directly.
• Periodically update the data for all of your plugins from wordpress.org.

Download

This plugin requires WordPress version 2.7 or later.

Version 0.8.2 ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

Description

This hotfix adds support for RSS enclosures to MagpieRSS, the RSS parser behind the fetch_rss() function in WordPress. It also forces MagpieRSS to use UTF-8 character encoding, which fixes some issues with feeds that contain non-ASCII characters.

Is this plugin for me?

This plugin is only going to be of use to you if:

1. You are fetching feeds on your blog with the fetch_rss() function and want to parse enclosures contained in the feed; or
2. You are fetching feeds on your blog either with the RSS Sidebar Widget or with fetch_rss() and question marks are showing up somewhere in the feed where special characters are supposed to be.

Installation

1. Unzip the ZIP file and drop the folder straight into your wp-content/plugins directory.
2. Activate the plugin through the ‘Plugins’ menu in WordPress.
3. That’s it! You can now parse enclosures contained in feeds fetched by WordPress.

Download

ZIP file from downloads.wordpress.org

FAQ

For FAQs, including how to parse enclosures in your feed, please see the plugin’s FAQ page on wordpress.org.

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

Description

Fixes the media uploader HTTP Error that some WordPress configurations suffer from.

If your WordPress 2.5 installation shows an HTTP Error when uploading files using the media uploader, then this plugin should fix that problem. Simply upload and activate the plugin, then you’ll be able to upload files with no problem.

Technical details:

The plugin adds a few lines to WordPress’ .htaccess file which deactivates mod_security on the file which handles file uploads.

Installation

1. Unzip the ZIP file and drop the folder straight into your wp-content/plugins/ directory.
2. Activate the plugin through the ‘Plugins’ menu in WordPress.
3. That’s it! Try uploading a file with the media uploader and the HTTP error should be gone.

Download

ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment!

Description

This plugin replaces the most common JavaScript libraries in WordPress with the corresponding files on Google AJAX Libraries.

“The AJAX Libraries API is a content distribution network and loading architecture for the most popular open source JavaScript libraries.”

Note that this plugin does not actually replace or remove any files from your WordPress installation. It simply replaces any references to them with references to the corresponding files on Google AJAX Libraries.

Installation

1. Unzip the ZIP file and drop the folder straight into your wp-content/plugins/ directory.
2. Activate the plugin through the ‘Plugins’ menu in WordPress.
3. That’s it!

Which Libraries are Supported?

The current version of the plugin supports the following JavaScript libraries:

• jQuery
• Prototype
• Scriptaculous
• MooTools
• Dojo

Download

ZIP file from downloads.wordpress.org
You should use the ‘Use Google Libraries’ WordPress plugin instead now.

All the information for this plugin can be found over at the WordPress Plugin Directory: Disable WordPress Plugin Updates.

Don’t forget you can also disable WordPress core updates too.

• WordPress 3.4 and 3.5 compatibility.
• WordPress 3.4 or later is now a requirement.

Description

If you publish many password protected posts (or even if you don't), you may end up using the same password for every post. With this plugin you can define a global post password from your 'Settings -> Global Post Password' menu, and switch password protection on or off from the writing screen with just one click. When you change the global password, all password protected posts are automatically updated with the new password.

Note that this plugin does not automatically enable password protection on every post. It allows you to use a global password for every post that you choose to password protect.

Screenshots

1. 

   Switching a post's password protection on or off.

2. 

   The settings screen.

Installation

• Unzip the ZIP file and drop the folder straight into your wp-content/plugins/ directory.
• Activate the plugin through the ‘Plugins’ menu in WordPress.
• Visit the ‘Settings -> Global Post Password’ menu in WordPress and set a global post password.

Now whenever you write or edit a post or page you’ll be able to switch password protection on or off with one click, instead of having to manually type in a password for each post. You can change the password whenever you like.

More Information

Please see the plugin’s page on the WordPress Plugin Directory for more information, including FAQs.

Download

ZIP file from downloads.wordpress.org

Any comments, questions, queries, suggestions, complaints, etc, please leave a comment below!