phpNuke, Google and includes/sessions

Posted: Sat Mar 27, 2004 3:45 am

This is just a post which I thought might be of interest.

I did a search on Google on one of my sites and was excited to see I got 180 odd hits. However when I started looking at them most of them were for includes/sessions errors on line 250. If I looked at the cached page on Google for these entries it they showed errors like this:

Quote:

Warning: Cannot modify header information - headers already sent by (output started at /web/htdocs/www.abcxyz123.net/home/includes/my_header.php:64) in /web/htdocs/www. abcxyz123.net/home/includes/sessions.php on line 249

Warning: Cannot modify header information - headers already sent by (output started at /web/htdocs/www.abcxyz123.net/home/includes/my_header.php:64) in /web/htdocs/www.abcxyz123.net/home/includes/sessions.php on line 250

So being in detective mode, I entered includes/sessions in Google and got 222,000 hits. I couldn't look at all of them but those that I did all had the above error messages.

It seems that Google and phpnuke's includes/sessions don't like each other for some reason or another.

As I said this might be of interest (yes, I know I should get a life but it's Saturday night Down Under, it's raining, it's cold and I've had three bowls of ice cream and can hardly move ........ Wink

)

Ron.....

PS Has anyone noticed that Google indexes nuke's homepages, blocks etc but apparently not the forums?

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

My forums are indexed. I don't think you're interpreting those results correctly Smile

. Those header messages would appear to be valid for a point in time. At one time that would have been the errors that visitors were receiving until you fixed it. Is that possible?

Posted: Mon Apr 05, 2004 12:28 am

I have watching my Google entries since starting this topic and now think that everytime Google tries to index phpnuke forums it creates a cached page with:

Quote:

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/australianopinion.com/httpdocs/header.php:33) in /home/httpd/vhosts/australianopinion.com/httpdocs/includes/sessions.php on line 249

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/australianopinion.com/httpdocs/header.php:33) in /home/httpd/vhosts/australianopinion.com/httpdocs/includes/sessions.php on line 250
Australian Opinion: Forums

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/australianopinion.com/httpdocs/header.php:33) in /home/httpd/vhosts/australianopinion.com/httpdocs/includes/page_header.php on line 525

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/australianopinion.com/httpdocs/header.php:33) in /home/httpd/vhosts/australianopinion.com/httpdocs/includes/page_header.php on line 531

Warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/australianopinion.com/httpdocs/header.php:33) in /home/httpd/vhosts/australianopinion.com/httpdocs/includes/page_header.php on line 532

Now there are a two hundred or so Google entries like this for my site and the cached pages all have different dates, some only a day or two ago.

Now this doesn't just apply to my site but to hundreds of other phpnuke sites (just input 'httpdocs/includes/sessions.php' into Google). If I could get to the bottom of this it might mean better indexing on Google.

Ron...

Worker Joined: Feb 16, 2004 Posts: 164

that sounds familiar...........its a common error - the header.php:33, try changing the

Code:




include("header.php");

into

Code:




require_once("header.php);

or

Code:




include_once("header.php");

where ever the duplicate call is from ie page_header.php.

Richard[/quote]

Posted: Mon Apr 05, 2004 12:43 am

Thanks, Richard, I will give that a try and come back here in a week or three and let you know the results.

Ron...

Posted: Mon Apr 05, 2004 12:53 am

Code:

require_once

Try that one first.........thats how i fixed the same problem.

Richard