2006.02.03

Problem with Geo Plugin

So WordPress released version 2.0.1 a few days ago and being a good little boy I upgraded. So far so good.

I created a page to place a Google Map showing places I’ve written about. It is a combination of two plugins and one of them is the Geo plugin. Unfortunately since upgrading I can’t post anything if the plugin is active. I get this error:


48

Warning: Cannot modify header information - headers already sent by (output started at /home/dnerad/public_html/douglas/journal/wp-content/plugins/geo.php:344) in /home/dnerad/public_html/douglas/journal/wp-admin/post.php on line 122

Damn. That sucks! So if I want the map I can’t post. What’s strange to me is the line mention is just this:


<th width="33%" scope="row">' . __('Geographic Tracking Features', 'Geo') . ':</th>

Looks innocuous to me. I think it just puts the words on the posting page.

Oddly after showing the error above the article I am posting shows up as a draft. What’s up with that? Does anyone in the WordPress Dev World know what’s going on? Maybe I’m an idiot, but it looks remarkably difficult to submit a ticket…

4 Comments Categorized: grrr  site

You can follow responses with a RSS 2.0 feed or via email using the checkbox below. Both comments and pings are currently closed.

 

4 Responses to “Problem with Geo Plugin”

  1. Jason Clark says  (February 4th, 2006 at 08:32:30 )

    Don’t know for certain the issue, but I can offer a few tips. First of all, the line number is probably useless. If PHP uses any kind of file-inclusion, it can throw off the number. That line 122 should refer to whatever line of code calls/loads the geo plugin.

    The actual error means what it sounds like… Some code in geo.php is trying to add an HTTP header to the output, but the HTTP headers have already been sent to the browser, and part of the page content has been sent as well. I’ve seen a similar issue years ago developing a web site using MS IIS and Active Server Pages. If you needed to add/modify headers after some of the page content had been generated, you had to enable buffering, so that the page content would be buffered until the entire page was done, and only then would it go to the browser. Of course, this makes the page appear to take longer to load.

    I don’t know if PHP (or the wordpress code) has a similar feature or not. Hopefully this will give something to go on.

  2. douglas says  (February 4th, 2006 at 11:36:06 )

    Yeah, that makes sense. The problem is that I know squat about PHP and am having a hard time figuring this stuff out. I’d worked enough with Blosxom to guess what much of the Perl code did; this is still all too new.

    Hopefully some of these pingbacks will produce the effect of someone more knowledgable than I in the art of PHP hacking in WordPress to resolve the issue…

  3. douglas says  (February 24th, 2006 at 23:20:00 )

    They’ve fixed the problem I was having with the release of v1.9.1. Thank you “ringmaster”!

  4. Quinn says  (December 12th, 2006 at 12:36:37 )

    What I want to do on my blog, is every few hours take the oldest post and move it to the
    front of the queue, all automatically. Anyone know if there is a plugin that can do this or
    a simple way to set up another plugin to do this (use my own feed perhaps)?
    Thanks.