365 Discoveries » wordpress

Error: Headers already sent, /wp-includes/pluggable.php [WordPress]

Justin Marty — Thu, 20 Aug 2009 13:48:46 +0000

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.

Similar Posts:

Error: Headers already sent, /wp-includes/pluggable.php [WordPress] originally appeared on 365 Discoveries on August 20, 2009.

Too Easy

Justin Marty — Fri, 12 Jun 2009 21:12:16 +0000

Upgrading WordPress is ridiculously easy. Between the new “one-click” automated upgrade and the automated SQL database backup plugin I use, it’s just too easy! Those darned kids nowadays will never have to go through the old methods of manually upgrading plugins and the core program. They won’t appreciate it!! They won’t!

Similar Posts:

None Found

Too Easy originally appeared on 365 Discoveries on June 12, 2009.

WordPress Stats Showing “Dummy” Image

Justin Marty — Thu, 30 Apr 2009 11:20:13 +0000

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!

Similar Posts:

WordPress Stats Showing “Dummy” Image originally appeared on 365 Discoveries on April 30, 2009.

Something I Probably Should Have Thought About [Gmail Pictures]

Justin Marty — Sat, 14 Mar 2009 10:21:19 +0000

This is actually pretty stupid of me to do this, but I have to laugh at it. At the end of January, I was forwarded some information I was expected to post on a web site I administer. After sitting on it for awhile, I simply copied the information from the email, and pasted it into the WordPress visual editor. The email contained a photo which, to my surprise, appeared in the post perfectly formatted. Apparently, I thought nothing of this.

Today, I went back to edit the page because I noticed a typo. Often, when you go to edit a page or post in WordPress, the HTML of the content will appear briefly before the TinyMCE visual editor has a chance to load. So, during that half-second, something in the code caught my eye; something about the image. I checked it out, and it seemed that all this time, the photo was being called from mail.google.com. I thought that couldn’t be right; Google isn’t going to play photo host through their Gmail system. But, the picture was there in the editor and the live page. But, wait a minute… I loaded the page in Internet Explorer (I had been using Firefox), and the image was broken. The problem? Whenever I edited or visited the page, I was also logged into Gmail with the same account that the image came from, so the image loaded because Firefox was authenticated while Internet Explorer wouldn’t be.

I should have known better. When you copy and paste stuff on the web (like web-based email), your browser is actually copying the code behind the content you’ve selected. If the image had already come from another web site like Flickr or Picasa, it wouldn’t have been a problem. But, anyway… another day, another lesson learned.

Similar Posts:

Something I Probably Should Have Thought About [Gmail Pictures] originally appeared on 365 Discoveries on March 14, 2009.

WordPress 2.5.1 is Available, and the Reminders are PERSISTENT

Justin Marty — Sat, 26 Apr 2008 12:03:35 +0000

I’m subscribed to the official WordPress blog so I know when new updates are released, however, it seems with the 2.5 landmark release, notification of the update appears on every page of the admin interface. There’s no way you can miss it now. Now, we just gotta get automatic upgrades without having to upload and overwriting files manually.

Anywho, 2.5.1 is out and it addresses a bunch of problems people have been having with the coveted 2.5 release. It looks like a 2.5 “redo” release. After browsing through the WordPress forums, version 2.5 has frustrated many a WordPress user, even veterans. I’ve been lucky, I guess, I have yet to come across anything buggy.

Similar Posts:

WordPress 2.5.1 is Available, and the Reminders are PERSISTENT originally appeared on 365 Discoveries on April 26, 2008.

SPAM Clogs the Tubes [Akismet Stats]

Justin Marty — Tue, 15 Apr 2008 13:00:19 +0000

There’s a lot of controversy going on all over the Internet and the real world over the massive use of peer-to-peer technology (P2P), and it’s legitimate and illegitimate implications. Namely, the massive amount of bandwidth P2P communications consume. Frankly, I believe the ISPs are blaming P2P users for using the available bandwidth on the network (regardless of the fact that those users have paid for a certain level of service) and threatening to charge for overages on ridiculously low monthly bandwidth caps instead of upgrading their networks as they should be doing just as any other company would have to who needs to keep up with demand in order to remain a viable competitor!

I’m sorry, I digress. That discussion is a whole ‘nother week of blog postings dedicated to the topic.

However, my topic today is related. Akismet (a WordPress bloggers best friend against SPAM) keeps detailed stats on the comments it filters. Every comment that is submitted to a blog with Akismet installed gets passed through Akismet and is checked to see if it looks like SPAM. If it passes the test, the comment is allowed to post on the blog. If for some reason a comment is caught that isn’t SPAM or a comment it let through that is SPAM, I can mark it manually, and Akismet will “learn” from its mistake.

Anyway, back to the stats. Listed here, you can see a basic graph outlining the number of HAM comments (legitimate comments) in blue, and the number of SPAM comments in orange. That is a outrageous HAM to SPAM ratio! And that’s only on blogs that Akismet tracks!

My point is… there’s A LOT OF SPAM. I’m sure the bandwidth it takes to transmit all that crap is fairly substantial. There have been studies that try to pinpoint the number, but they all differ. They do, however, agree that it is certainly more taxing than legitimate communications.

The solution? These ISPs should spend more of their resources locking down something that NOBODY likes (SPAM) and less time alienating their customers over crap like DNS-based behavioral tracking and bandwidth caps.

P.S. Akismet is the reason you don’t have sign-up or enter in some CAPTCHA or other human-verification code in order to comment here! So yeah! Give it up for Akismet!

Similar Posts:

SPAM Clogs the Tubes [Akismet Stats] originally appeared on 365 Discoveries on April 15, 2008.

WordPress Fixed Pinging for Future Posts

Justin Marty — Wed, 02 Apr 2008 13:00:42 +0000

It took me some amount of time to find this answer, but it seems that WordPress will process a “ping” for your blog when a post goes live. Previously, WordPress would send a ping as soon as any post was published, regardless if a post was scheduled to go live at a later date. After version 2.3 (I believe), the ping will be sent after the new post is public.

One thing to keep in mind, though, is that when your blog pings whatever services you have set up, it’s not telling the service what’s new, only that there is something new at your blog and the service should send a spider/robot/crawler/killer coding ninja monkey at your blog to discover the new content.

Either way, it’s a pretty important feature… But, so are killer coding ninja monkeys… and they don’t have that integrated into WordPress yet, damnit.

(Yes, this post was scheduled for a future time… heheh.)

Similar Posts:

WordPress Fixed Pinging for Future Posts originally appeared on 365 Discoveries on April 2, 2008.