Stream does not support seeking?

[Darrin]

hey, on This page (and all of the other pages I have includes on too I guess, this is just the main test page) I'm getting a wierd error message at the top. Does anyone know why? It worked fine a while ago (like a month or 2) and i didn't change anything, but now I get the error, anyone able to help?

[jason]

What does the included file do? Streams generally imply you are either accessing files or network resources.

--Jason

[Darrin]

It is a PHP include (includes a header, displays page info, then includes a footer) and it is including the header and footer fine, but I still get that error message.

[Vin DSL]

I think that's a bug in the new version of PHP they just installed. Try putting a @ symbol in front of include, i.e.:

@include("http://www.xtremefocus.org/webteam/menu/header.html"); 

I think you can also fix it by changing the path from absolute to relative, i.e.:

include("http://www.xtremefocus.org/webteam/menu/header.html"); 

...to this:

include("../webteam/menu/header.html"); 

...or whatever...

[Darrin]

thanks vin! one question though, should I change all the includes on my site to "@include" or just wait (as if it's a bug it should be fixed pretty soon shouldn't it?)

[jason]

An @ in front of any function name in PHP simply surpresses any error messages that function generates, so putting in that @ sign won't hurt anything down the road, even when the bug is fixed, so you can safely use it everywhere if you want.

I just looked in this PHP bug database, and this is an open issue: http://bugs.php.net/bug.php?id=24053. It appears to be an issue related to including remote files (ie using http:// in your include() call). As Vin suggested, if you are including files that are on the same server as the script they are being included into, the proper way to do it is with a local path. This should get rid of the error and may speed up your site a little bit because there is less overhead involved in getting the included file.

Another option would be to change PHP's error reporting to either not display errors at all, or to simply hide non-fatal error messages. Both of these can be done with .htaccess files.

To disable error messages all together, add a line to a file called .htaccess in your public_html directory that looks like this:

php_flag display_errors off

With that, absolutely no error messages will ever be shown by PHP on your site, which can be a pain when you are testing something new, so I'd recommend just hiding the non-fatal stuff:

php_value error_reporting E_ALL & ~E_NOTICE & ~E_WARNING

Good luck...

--Jason

[Darrin]

thanks everyone! I think I'll just leave it for now, as it is working fine (the include that is) and the site is in a testing folder (not live yet) so for the next month or 2 I'll be the only one seeing it

Thanks again!
Darrin

[Vin DSL]

Originally posted by Darrin
thanks vin! one question though, should I change all the includes on my site to "@include" or just wait (as if it's a bug it should be fixed pretty soon shouldn't it?)

Assuming everything is running okay, except for the 'error-errors', I'd just use '@include' on lines that are generating the errors.

LoL! Does that make any sense?