WP-Hive upgrade prevents WordPress login

I upgraded the wp-hive plug-in to version 0.5 earlier today. It wasn’t an active plugin for me and I needn’t have upgraded it. But I did it earlier today and didn’t think twice about it.

Later, I found out that I could not login into WordPress as an administrator. Everything else seemed to be working fine. Site was up and running as usual, but I couldn’t access my dashboard.

When I checked the WordPress database through phpMyAdmin the wp_options table was perfect. I was soon able to figure out that this was not a WordPress problem.

So I started troubleshooting by trying to undo my last set of actions, one of which was upgrading the wp-hive plugin. Renaming the wp-hive folder gave an serious error and brought the site down. With that I was able to narrow down the problem to the file

/wp-contents/db.php

I remmed out the line

/*require_once( WP_CONTENT_DIR . ‘/plugins/wp-hive/do-prefix.php’);
*/

Everything is back to normal for me now because I dont use wp-hive.

I didn’t find anything about this problem in Google, so I decided to write this down.

How to: Use TGFI.net SEO plugin

This is a sample post created after the installation of TGFI SEO plugin.

This sample post should help me verify if I’m able to configure meta data at an individual post level.

What this means is, after this posting this, if I access this post through its permalink and view the html source I should see some meta data for this post.

This plug-in sure doesn’t sound like big deal to me, because I am required to use the wordpress dashboard instead of a blog client. TGFI SEO plugin will give you yet another form just below the editor on which we can fill in the post level meta data for SEO.

One thing that must be done for the plugin to work is from the FAQ:

Q: The titles aren’t showing up for me, or seem to be partially working. What’s wrong?

A: Make you you have <?php wp_head(); ?> in your header.php file between your HTML <head> tags.

I hope it is worth the effort.

Solution to WordPress MU xmlrpc bug

If you are reading this, you probably landed here looking for a fix that will help you use a desktop client on WP-MU. Well, you are not alone.

My previous post on using Scribefire on WP-MU, certainly was not the most elegant way of solving the xmlrpc problem, but it worked then. When I upgraded to Firefox 3.5.1 and Scribefire 3.4.1, the fix stopped working. I was busy at work and could not sit down to study the problem, so I simply stopped posting to the other blogs I really want to write.

Thankfully, this weekend I could fix the problem. I know now that a fix was available since April ’09, but it perhaps took so long to show up in google or it was just my clumsy googling. Daniel Llewellyn has written this small piece of code which solves this problem elegantly.

To solve the problem (xmlrpc bug) so that you use desktop clients on WP-MU do the following:
1. Download the text file with Daniel’s code
2. Rename the text file as wpmublogger-getusersblogs.php
3. Upload the php file to your WP-MU installation to the mu-plugins folder under the wp-content folder.

Thats it and now you’re now ready to go. When I tested, Scribefire 3.4.1 detected all 7 blogs that were configured to a particular user account.

Thank you, Daniel, for sharing the trick. One small piece of code that solves a bug bothering so many WP-MU users.

How to : Scribefire on WordPress MU

Using a blog client software with WordPress MU does seem to be problem. After 30 minutes of googling, I still couldn’t find one thing that provided any conclusive answers.

I’ve always been a Scribefire fan and wanted it to work with WP MU.

The WP MU forums already have this post on how to make Scribefire work.

To date the solution seems to have remained the same. I tested this out on WP MU 2.8.1, Firefox 3.0.11, Scribefire 3.4.1 on a site that does not use wild card subdomains.

These are the steps:

  1. Set-up your WP MU site without wild card subdomains – eg: http://mysite.com/blog1 instead of http://blog1.mysite.com – if you didnt have one already.
  2. In the main domain and in all blogs, enable XML RPC publishing by accessing Settings->Writing.
  3. Install Firefox with the ScribeFire add-on, if you dont have one already.
  4. Now add a new account to ScribeFire, to any of the WordPress.com or WordPress blog not powered by MU. This step should be easy. Close ScribeFire.
  5. Re-open ScribeFire, edit the new account you created in step 4.
  6. Change the blog URL to http://mysite.com/blog1/.
  7. Change API URL to http://mysite.com/blog1/xmlrpc.php
  8. Update Login credentials and Press “OK”.
  9. Ignore the errors given by ScribeFire.
  10. Close ScribeFire.
  11. When you re-open ScribeFire, it has already become this willing work horse.
  12. Repeat steps 4 to 11 to add additional blogs.