pluggable.php [WordPress]

So, you’re using WordPress and you just spent hours looking for the perfect theme to fit your new hybrid kitten-and-knitting blog. You upload the theme’s files into the appropriate folder, navigate to the themes page in the administrative interface, and click “activate.” So far, so good, right? Later, you notice that anytime you save a page, post, or option, you’re greeted with an error much like the following:

Warning: Cannot modify header information – headers already sent by (output started at /home/user/public_html/ccc/wp-content/themes/broken-theme/includes/theme-options.php:172) in /home/user/public_html/ccc/wp-includes/pluggable.php on line 237

The exact nature of the error and line numbers will vary. The point is, your frilly new theme is broken or there’s a plugin conflict with it. Here’s a funny thing that happened with my situation and I suspect others may benefit from this tip. If you’re receiving these errors, and you’re still logged into your WordPress admin panel, activate a different theme you know works. The real problem begins if you log out.

If you are unable to access any portion of your site, or most importantly, the log in page, you’re going to need to get your hands dirty.

FTP into your WordPress themes folder, then to the folder for the offending theme (i.e. wp-content/themes/broken-theme).
Copy everything within that theme’s folder to another folder on the server, or to your hard drive (or just delete if you plan on installing fresh).
Copy the files from a known-good theme (like the included “classic” or “default”) into the folder you just emptied.
You should now be able to access your log in page. (www.yourdomain.com/wp-admin/)

You could just leave it as is and set out to fix or replace your bunk theme, however, I recommend “officially” activating the theme you wish to revert back to, then deleting the duplicate you created in step 3.

Shared Discovery, troubleshooting, wordpress

Apr 30, 2009

Justin Marty

No Comments

WordPress Stats Showing “Dummy” Image

Something went wrong...

Upon viewing your blog stats generated by the WordPress Stats plugin you see an image that looks like a bar graph with data back to 2003 with two colors, one representing “Region A” and the other, “Region B,” you’re looking at a dummy image that WordPress Stats inserts when something goes awry. (Personally, I think it would be better if something more descriptive was there, like an image that says “i is BROKDED!”) I wish I would had the foresight to take a screen shot of the image before I fixed the problem, but at any rate, the problem is resolved.

My solution (thank God, the easy one): Deactive the plugin, delete all related files, upload a fresh copy, and reactivate. You will have to re-enter your WordPress.com API key, and to keep your stats, choose to “Replace” the blog (the plugin will guide you through these steps) with the same URL that you’re reactivating.

If that doesn’t take care of the issue, there are other solutions in this thread.

Good luck!

Shared Discovery, Software

Sep 17, 2008

Justin Marty

2 Comments

Frustration with Upgrading My Zune Software [Solved]

I haven’t been able to upgrade my Zune software installation over the last couple of updates because I kept getting the “Setup must stop because the required package ‘Zune’ failed to install,” Error code: 0×80070643.

Most solutions included downloading and installing the full Zune package which includes all of the other components required. I tried that, and nada. I tried a utility provided by Microsoft called “Windows Install Cleanup” which allows you remove a program’s Windows Installer configuration information so there’s no trace, or anything saved, from previous installs.

So, when the big Zune 3.0 update came around, I really wanted to upgrade. I decided I’d do the one suggestion I kept avoidng: a complete removal and reinstall. I avoided this because I’d lose all settings and *gasp* play counts. (I like them, okay?)

I completely removed the Zune software using a program called “Unzoone.” I also cleaned up the registry to make sure all traces were removed with “CCleaner.” Finally,

Okay. This HAS to work, right?!

Restart.

Start Install…..

ERROR!!!!! GAHHHHHHHHH!!!!!!!!

So, I began yet another quest of Googling for answers. Finally, I happened upon this Locker Gnome blog, Digged (?), where it was suggested that the Windows Firewall must be turned on (mine’s always off) for the installation to complete. Sceptical, I tried it. Sure enough! That was the ticket. Now why in HELL would the Windows Firewall need to be enabled for this reason!?

Discoveries, Stuff from the Interwebs

Jun 26, 2008

Justin Marty

2 Comments