reclassified.

I do not see this error -- it may have been fixed.  Please re-open if it's still there and give a more details explanation of where it is, etc...

Still there.  I just go to www.php.net and at the very top of the page, before anything is printed I get that error.  It only happens on the front page.  If I go to any other sub-page I do not get the error.  It doesnt appear to effect any functionality of the site, its just a little annoying and its been happening for several weeks.

I still can't see this.  I even went so far as viewing the source and searching for 'error'.  Nothing.  Try shift+refreshing your browser and clearing your browser cache.   

Also, are you sure you're on the main php.net website and not a mirror?

This was fixed fairly quickly upon being introduced, several changes are being made on the php.net site, we apologize for temporary errors which occur during this process.

This isn't a temporary error.  Its been happening for over 2 weeks.  I took a snapshot of the error 5 minutes ago.  You can see it here:

http://offsky.com/transfer/example.jpg

The error doesnt bother me, I just thought I'd be a good samaritan.

I *do* appreciate your desire to help out but there is definately some critical piece of information missing here.

#1) That snap is *not* 5 minutes old.  That much is obvious from the missing news item.

#2) Noone else is seeing that error message since it was last fixed.

My *theory*, is that your corporate firewall is caching the page.  This would explain the lack of the most recent news item (which was added two days ago) and the presense of the error message despite the script having been fixed.

I'd like you to try something to circumvent possible caching by your firewall.

Browse to: http://www.php.net/?a=12345

This *should* tell any caching proxy to forcibly reload the page (using the GET parameter).  This may or may not work, but it's the simplest approach.

Baring that, try the following script from behind your firewall:

<?php
  $fp = fopen('http://www.php.net', 'r');
  var_dump($http_response_header);  
?>

If the page is being cached, the caching proxy should tell you in the response header when it was originally rendered.

Thanks in advance for taking the time to explore this.

This must come from cache. This error was fixed days before... We also have an Activestate awards news item since yesterday, so I am sure you are not seeing a fresh copy of the page.

It was the cache! Dang proxy!

I'm sorry for leading you on a wild goose chase. Thanks for your responses.  Its good to see an active and responsive bug resolving crew.

-Jake

Should be bogus, as no bug existed to correct...