To register for an Internet.com membership to receive newsletters and white papers, use the Register button ABOVE.
To participate in the message forums BELOW, click here
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?)
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.
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?
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.
Quote:
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() ...
__________________
dalecosp ---------------- "God doesn't play dice." --- Albert Einstein
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
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.
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.