stream does not support seeking?

uNF

Hi,

I've just reorganised my website to make it easier to navigate (for me, I've given it directory structure, instead of dumping everything in /)

Anyway, Now, I'm getting this problem whenever something gets included:

Warning: main(): stream does not support seeking in /home/camkb/public_html/m3rlin/index.php on line 117

115     } elseif ($action == 'login') {
116      if (!$_GET['done']) {
117               include('http://m3rlin.ws/html/login_form.html');
118         } else {

I've got a feeling it's having "http", I used that, because I didn't want to have a heap of ../../ stuff to get back diretories.. do I have to make it https or something (it has some code which checks sessions.. could that be affected by having http?)

Thanks for any insight..

🙂

dalecosp

Originally posted by uNF
Hi,

Warning: main(): stream does not support seeking in /home/camkb/public_html/m3rlin/index.php on line 117

Thanks for any insight..

🙂

You may be on the right track, but don't forget to check whether or not include is allowed to access 'remote' files in php.ini

You could perhaps code with the $DOC_ROOT var.....

ivogomes

I'm having the same problem. I solved it by replacing the includes like this:

before:
include ('http://www.website.com/contents/page.php');

after:
include ('/home/public_html/contents/page.php');

It works this way without any problems...

My real problem is when I want to include someting like this:

include ('http://www.website.com/contents/page.php?action=something');

Since my host updated PHP to version 4.3.2. the includes started showing the error:

Warning: main(): stream does not support seeking

I need some help on how to include this files. Please help me!!

ivogomes

Hey!! I figured it out!!!

I must put an @ before the include, like this:

@include ('http://www.website.com/contents/page.php?action=something');

All pages work fine now.

goal

That will supress the warning message, however it doesn't actually resolve the fact that it's generating the warning. If you're going to do some condition testing on the result of the include() then you're a bit screwed.

mellymell

Hello all... So, now that we know that using "@" to supress the error message is a quick-fix, how do we actually fix the message. My problem is that I use subdomains and so for a subdomain, I have to access the include file with the full URL rather than a relative path (unless you know something I don't 😃 )

So, has PHP issued a fix to this issue or a way to resolve it on our end?

Okay, I just found out-silly me.... Even if I'm using a subdomain and therefore can't take a relative path, I can still use the FULL path: /home/username/public_html/doc.inc

I'm sure you all knew that... What makes it so bad is that I've included other files on the SAME pages with the full path... WHY OH WHY did I use a URL for the others?

dalecosp

Originally posted by mellymell
My problem is that I use subdomains and so for a subdomain, I have to access the include file with the full URL rather than a relative path (unless you know something I don't 😃 )

My subdomains are all on the same filesystem, therefore, I still don't have to include remote files.

So, has PHP issued a fix to this issue or a way to resolve it on our end?

Well, one of them is called CURL... also, it wouldn't hurt most of us to RTFM on include() ... 😉

milomedia

you know, the @ may not get to the root of the problem, but since the software works perfectly, there must be no problem. This is obviously a problem with the newer php... I had a wonderful little system running error free until my host upgraded. I say use the @... including a footer and or header will still work, and the end user won't see an ugly message.
-e

daynah

Yea, it's definitely the newer php. I've been getting this error a lot lately. The best way to remedy the problem is to use:

<? include('/absolute/file/path/header.php'); ?>

If you use the absolute path, you don't need the ../../

The path usually looks like this:

<? include('/home/username/directory/header.php'); ?>

My real problem is when I want to include someting like this:
include ('http://www.website.com/contents/page.php?action=something');
Since my host updated PHP to version 4.3.2. the includes started showing the error:
Warning: main(): stream does not support seeking

I need some help on how to include this files. Please help me!!

Before the include, try setting the action variable.

For example,

<?
	if($something)
	{
		$action = 'something';
		include('/home/public_html/contents/page.php');
	}
?>

I believe this should work. 🙂 As long as the files are not called remotely.

I believe putting the @ in front of the function only surpresses the error from that function...

SVTBlackLight01

And how do we solve this problem if the files are called remotely?

dalecosp

[man]include/man

hismightiness

I may be simply missing it, but it does not seem to me that an actual solution was posted. Here is what I have:

global $ad_filename;
$include_path="http://".$_SERVER["HTTP_HOST"]."/ads/";
@include ($include_path.'ad_rotator.php?file=ad_banner01.txt');

I also get this error message using PHP version 4.3.2 on a Red Hat Linux server running Apache 1.3.28 (Unix).

I was just looking through the online documentation, and noticed the function "realpath()". Would this be useful in resolving the error issue?

dalecosp

Hmm...

http://bugs.php.net/bug.php?id=24053

Appears that there might be a few developers aware of the issue.

brownafroduck

Ugh I am experiencing the same problem, but just as of today... This is ridiculous if you ask me. That something this big wouldn't work.

hismightiness

Oh well, as a native ASP 3.0 developer, I am used to findings ways to work around obstacles in front of what I am trying to do. 😃 One of the reliefs behind using PHP nowadays, is the built-in functions which ASP does not have and requires you to write yourself.

Thanks for the update, dalecosp! That is a very useful link too...

Apparently, the only recommended way around this problem is to use a @ prior to the include() until an updated version of PHP corrects the problem.

acidbreeze

Seeing as how the problem still occurs on PHP 4.3.4 for a few setups, I'm thinking that this problem should receive more attention.

dark2k1

I had a problem passing variables to included files so I came up with this solution.

$file_name = "whatever.php?somevar=heysup";

$file_name = explode("?", $file_name);

$queries = explode("&", $file_name['1']);
for($x = 0; $x < count($queries); $x++) {
$query = explode("=", $queries[$x]);
$_GET[$query['0']] = $query['1'];
}

extract($_GET);

include($file_name['0']);