| Author | anonymous |
| Date | 2004-12-10 04:14 |
| Posts: |  Hi, well since there's already been a group of people viewing this thread, there must be some interest. So, I'll go ahead and spell out the verdict for you. Hopefully this helps you if you're having similar problems.
In the first form of information, you are prompted to provide a Physical Path to where your install.php resides. This means that even though you are on a hosting service that would ordinarily hide the fully qualified path from you because you don't ordinarily need to know it, you'll need it in this case. If you DON'T know your physical path, here's a way to get to it, thanks to the help of hhombergs. ((Thanks for all your help!)) You'll want to create a little script called something like test.php. Inside the script, all you'll need is the following lines: <?php
Save this script. A good place to put it on your server would be in the same directory as your install.php file since this is the directory whose physical path we are looking for. Execute the script by loading it into your browser. Many of you who have been working with PHP for some time now are already familiar with what this script is doing. But never the less, execute it and you'll see a wealth of information about your system and php configuration. In this wealth of information will be the diamond we are looking for. There will be an entry call "path translated". The path to the right of this is the physical path to your intall.php script. Now you have this. If you are running IIS, make sure to do one of two things when typing this directory into your physical path prompt. 1) change the '' single backslash in the directory path to '' double back slashes OR 2) change the '' single backslash to a '/' single forward slash for each. Otherwise PHP will get confused thinking that this is an escape code. chances are this will take care of your problem if you are experiencing the problems discussed earlier. Happy OPNing |
