Sep 19th, 2011, 10:04 AM
Hi Dogen,
Huh! Yes, it look like you've configured it properly.
I've run into things like this before, where the "physical" address doesn't actually map to the path supplied on the command line. I believe this can occur when there are symbolic links in the path, or something along those lines - most times I never got to the bottom of it. It may not be the issue, but it would be good to check.
Try this: upload a PHP file to the Form Tools root folder (same folder as process.php) ith the following content.
Then load it in your browser. That will output a bunch of variables with the paths that the running PHP process *thinks* they have.
One or more of them will contain the path to the current running script. Check the path - does that look exactly like /var/www/html/apps/forms - or does it maybe just start with /html/apps or something like that?
- Ben
Huh! Yes, it look like you've configured it properly.
I've run into things like this before, where the "physical" address doesn't actually map to the path supplied on the command line. I believe this can occur when there are symbolic links in the path, or something along those lines - most times I never got to the bottom of it. It may not be the issue, but it would be good to check.
Try this: upload a PHP file to the Form Tools root folder (same folder as process.php) ith the following content.
PHP Code:
<?php print_r($_SERVER); ?>Then load it in your browser. That will output a bunch of variables with the paths that the running PHP process *thinks* they have.
One or more of them will contain the path to the current running script. Check the path - does that look exactly like /var/www/html/apps/forms - or does it maybe just start with /html/apps or something like that?
- Ben