[RESOLVED] Unexpained Warning Messages

dale282

Hi all,

I'e recently been having some problems with my website (http://www.inmylife.co.uk):

Out of the blue, the site seems unable to process file include requests (usually triggered somewhere in the 'photos' section - try this link and press refresh a few times if all seems to be well first time around: http://www.inmylife.co.uk/photos/summer2006/). Then after that point it starts to not display anything correcly, but when i try to refresh the page, it processes some includes correctly then doesn't process one that were working before.

i just don't understand what's going on with it since i haven't changed anything with the file that starts throwing up the errors

Typically, but not always, it throws up three warning messages for each inclulde file that didn't work:

Warning: main(http://www.inmylife.co.uk/templates/body_top.php): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in /home/inmyli00/public_html/index.php on line 12

Warning: main(http://www.inmylife.co.uk/templates/body_top.php): failed to open stream: HTTP request failed! HTTP/1.1 403 Forbidden in /home/inmyli00/public_html/index.php on line 12

Warning: main(): Failed opening 'http://www.inmylife.co.uk/templates/body_top.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/inmyli00/public_html/index.php on line 12

Does anyone have any ideas as to what's causing this? My guess is that it must be something server-side, but my hosting company are also puzzled at first glance - is there anything I can suggest to them? Some sort of PHP reset perhaps?

Very confused!

Bobulous

It looks like you're trying to call

include 'http://www.inmylife.co.uk/templates/body_top.php'

If so, try this instead

include 'templates/body_top.php'

which is relative to the index.php file in the top (public) directory of your site.

If that's not it, then have you made any changes to .htaccess recently. For instance, have you used .htaccess to forbid hotlinking?

bradgrafelman

Yeah, as Bobulous pointed out, you're trying to include/require/open PHP files across HTTP. You can't do that.

If scripts could get PHP code across HTTP, then you would simply be able to open your browser and see PHP code.

dale282

thanks for those pointers.

i shall try making the include path relative to the file rather than absolute, but i don't think it'll make any difference. The thing is, it was al working perfectly everytime until about a week ago, and that's what i don't understand about it: why it stopped working and why it does work sometimes (eg when pressing refresh, some files are included via the absolute path but others do not work).

very puzzling...

bradgrafelman

"Rather than absolute" ?? You're not using absolute paths. You're using web paths.

An absolute path would look like /home/users/myUsername/public_html/includes/myFile.php. A relative path would look like includes/myFile.php. What you're doing is a web path, so the PHP engine see's the [url]http://,[/url] and goes around to your webserver to request the file. It's like opening up a browser window and typing in that address. You're not loading the PHP file at all - just the output that is sent via the webserver.

dale282

oh, ok, thanks for clearing that up.

i'll try making some of the paths absolute and see if that makes any difference...

dale282

bradgrafelman wrote:
"Rather than absolute" ?? You're not using absolute paths. You're using web paths.

An absolute path would look like /home/users/myUsername/public_html/includes/myFile.php. A relative path would look like includes/myFile.php. What you're doing is a web path, so the PHP engine see's the [url]http://,[/url] and goes around to your webserver to request the file. It's like opening up a browser window and typing in that address. You're not loading the PHP file at all - just the output that is sent via the webserver.

this did in fact solve the problem. thank you very much for your help bradgrafelman!