WordPress MU 2.6 beta 1 is out

Donncha released yesterday the first beta version of WordPress-MU 2.6. This version includes the new features of WordPress 2.6.  WordPress MU specific changes include

  • The version number is being bumped to 2.6 rather than 1.6 because of version confusion.
  • Signup page now has a nonce to help defeat spammers.
  • Plugins in wp-content/plugins/ are version checked like in WordPress. mu-plugins isn’t covered just yet.
  • Major object cache changes.
  • And many more bug fixes. Check the timeline for a list of changes.

Download wordpress-mu-2.6-beta1.zip

WP-TagAds monetizing plugin

WP TagAdsis another plugin by Jorge for you to use as a monetizing tool:

WP TagAds is a new way to display ads on your WordPress blog. WP TagAds is an advertising solution tailored for WordPress bloggers, ads are displayed based on the post tags you assign to a post in your WordPress blog. This is different then say Google Adsense where the page is crawled then ads are displayed based on the findings.

With WP TagAds you are served eBay products based the keywords you assign to a post. Don’t like the ads your are seeing, just change the keywords around a little to get the ads you are looking for.

Ads are displayed via a sidebar widget that is included in the plugin and you can place the widget where you like inside your template. You will need a eBay Campaign ID to start making money. A eBay Campaign ID is issued to you free by the eBay Partner Network.

 

See it action here (top right)

WPMU Cleanup – script to delete unused blogs

WPMU Cleanup is a script that checks the WordPress-MU database for blogs that have not been updated for some time. Then, it sends to these blogs authors an email telling them that their blog will be deleted in a few days if they don’t update it. If the blog is not updated in time it it removed from the system.

Here are the instructions:

This script checks the WPMU database for blogs that have not been updated for X days, then sends a notice to the blogowner that the blog will be deleted after Y days.

It also automatically deletes blogs that have not been updated for Y days, then sends an email to the blog owner.

On both occasions, the script will send a report with details on warned and deleted blogs to the administrator.

This script has *NOT* been programmed as a plugin since it is intended to be executed by a cronjob. As it is now it should be run once every 7 days, but you can configure it to do otherwise.

This script is *NOT* a final version and should be used with caution and only if you know what you are doing. I recommend testing it on a testsite rather than a livesite.

A number of projects for WordPress-MU people

There are a few projects for WordPress-MU folks over at jobs.wordpress.net:

  1. asap WPMU installation for beta testers
  2. WP MU & WP MU Plug-in Experience Needed
  3. Seeking to drive Multiple Wordpress sites through One Installation

How to Write Plugins for Wordpress MU – updated

Last year I gave a ink to a short post on the basics of WPMU plugin development by itdamager. It turns out that that post is no longer available online. So is a cached copy of it:

Plugins for Wordpress and Wordpress MU are very similar but there are a few specific MU commands and plugin placement differences you should consider when creating a plugin for WPMU.

  • Wordpress MU plugins can either be globally enabled or individually enabled/disabled by each user, depending on their purpose.
  • Wordpress MU will allow you to check if the user is a site admin or not.
  • Wordpress MU will allow your plugin to use ‘per blog’ settings, or ‘per site’ (sitewide) settings, depending on your needs.
  • Wordpress MU has variables that are useful to plugin development

Global Plugins
Wordpress MU has a special plugins directory called mu-plugins. Any plugin placed within this directory will automatically be enabled globally. Users cannot disable or view the plugins located here. To ‘disable’ a global plugin, delete the plugin file from your server.

User Enabled Plugins
Plugins that users are allowed to enable/disable for themselves are placed in the standard plugins directory. This would include many of the standard plugin’s that are already available for Wordpress. If your plugin will reside here, you can probably follow the standard Wordpress plugin development instructions on the codex.

Site Admins
Certain users, (admin by default) can be given the ability to administrate a WPMU installation.

If you want your plugin’s config screen(s) to be available only to WPMU admins, or certain functions only available to admin users, then you can use the following MU functions to test if a user is a site admin or not:

get_currentuserinfo() – get_currentuserinfo requires no arguments and preloads, if not done already, information about, you guessed it, the current user.

is_site_admin() – is_site_admin, as the name implies, will return true if the user is a site admin, and false if they are not.

By using those two functions you can write code or config screens that are admin specific and unavailable to regular users.

Sitewide Settings
WPMU has commands that allow retrieval/storage of global options.

add_site_option($name, $value) – Adds a new sitewide option to the database.

update_site_option($name, $value) – Updates a sitewide option, adds it if it don’t exist.

get_site_option($name) – Retrieves a sitewide option from the database.

WPMU Variables
Many useful variables are available in Wordpress MU. Here are a few.

$blog_id
$user_id
$current_site
$current_blog
$wpmuBaseTablePrefix
$table_prefix

Contants
VHOST – yes if installed using sub-domains, no if installed using sub-directories.

More MU Specific Commands
For a full list of all commands specific to WPMU, refer to wpmu-functions.php where you will find they are all defined with self explanatory names, in most cases.

StatCounter vs. PayPal

According to the StatCounter blog (more here) there are some problems in the PayPal kingdom. It seems that following an update on PayPal’s web site few issues where reported with the service (confirmed by PayPal and some reported to be solved). However, StatCounter claim that more issues arose:

  • The Paypal Handling Cart feature completely broke down
  • Cross border payments could not be made as the drop down country list did not work
  • Customers have been flooded with hundreds of duplicate subscription emails from Paypal
  • Payments from Paypal are no longer associated with the relevant subscriptions
  • Some customers have been and are being DOUBLE BILLED by Paypal
  • Merchants have not been receiving instant payment notifications or failure notifications
  • Merchants/customers are unable to cancel subscriptions

But the main concern was, in StatCounter opinion, is that PayPal did not acknowledge or offer any assistance. They could not get a response fro PayPal via email, phone or any other means of communication. They added that many StatCounter customers did not receive their invoices and some might have been double billed.

I have been using PayPal for some years now and never had any issues with them. If what StatCounter claim is true I see this issue with great concern. the worst thing a company could do is leave their customers in dark and not supply any information and updates.

Unfiltered MU plugin

As you may know WordPress-MU doe’s not allow the users to use all html tags within their posts and pages. This is to reduce the security risks of allowing running scripts and embeddings unfiltered elements. This is done to all level of users even the systems administrators. However, in some cases, one wants to grant the capability of using unfiltered html tags to system admins or other trusted users. This could be archived by using the Unfiltered MU plugin by Automattic:

Unfiltered MU gives Administrators and Editors the unfiltered_html capability. This prevents WordPress MU from stripping <iframe>, <embed>, etc. from these users’ posts.
The plugin can either be used globally for your entire MU site, or it can be applied on a blog-by-blog basis.
For WordPress MU only. Regular WordPress already offers this feature and does not need this plugin.

If you want to allow unfiltered html to all users (NOT RECOMMENDED) drop the plugin in the mu-plugins directory. To allow it just for certain blogs place the plugin in the plugins directory and enable it on per-blog basis.

Monetize your blog content using Premium text messaging

Just came accross a new plugin by Zong that allows bloggers to charge readers for post, feed or services via SMS:

Content Pay by Zong allows you to monetize your blog content using Premium text messaging. Your reader sends a text message using his mobile phone and he receives a code that gives him access to your content for a determined duration.

Here is the clickable image that appear for paid content:

The clickable image that appear for paid content

and  the window’s information which tell the user how to pay and get access to the content:

The window's information which tell you how to pay and get access to the content