bradgrafelman wrote:If all you're trying to do is include some static HTML file on another server, then readfile() or file_get_contents() would be more applicable; include()/require() should only be used for loading PHP scripts for parsing; this obviously can't be done across an HTTP connection as the PHP code will already be processed and all you're getting is the output.
Also note that you don't need to know the full local path, just a relative path. Also, if you know the file you want is in a directory called "includes" in the root of the website, you could do:
include($_SERVER['DOCUMENT_ROOT'] . '/includes/myfile.php');
OK, I really do appreciate you trying to help.
But it's irritating and frustrating when someone says that what is currently working cannot be done!
Please understand. This works! At least to date. It works everywhere except on my home box.
The mnu.php file I'm trying to include generates a menu. That menu is dynamic in that it changes, sometimes from one day to the next, sometimes from one hour to the next.
The output that I want to see is the processed output of that file.
It works on the hosting server.
It works on WinXP
It worked on Ubuntu 7.10.
It doesn't work on Ubuntu 8.04.
Maybe more background is in order.
I ran an upgrade process to bring Ubuntu up from 7.10 to 8.04.
Everything looked good until I rebooted. Ubuntu could not load.
I loaded the ISO of 8.04 onto a different partition. Then I had to reload all the LAMP stuff, as well as most everything else. The install 'upgraded' my Firefox to v3 beta 5, wiping out most of the utility that I had with Firefox 2.x because the extensions I had loaded mostly don't work with v3.
I was able to recover a great deal from the 7.10 partition - I could see it, I just couldn't run it. What I could not recover, I downloaded from my hosting servers. The scripts I'm talking about now are running on of those servers.
Somewhere in this reinstall process, some component was changed such that what worked before in LAMP does not work the same.
What I'm trying to discover is what changed. If I don't understand that, I have no idea what might or might not work in the future.
If it's a procedural change, then I'll adapt.
But if it's a config change, I need to understand what that change might be.
I'm trying to find an answer, not an alternative - I have alternatives, they're just unattractive and somewhat less efficient.
Again, I don't mean to offend, but I'm looking for an answer to the problem, not alternatives.