A solution to a big problem.
Posted: Fri May 03, 2002 5:41 am
I'm in the process of creating a program with about 16 different pages that need to connect to a MySQL DB. In each page, I include a config.php file that has all the information I need on it. Now here's the problem:
To include the page, I have to have the exact path to it. Since I'm going to distribute this program, that path is going to differ per each user. I don't want users to have to go through 4 pages (there would be 4 config files if I placed one in each folder that I'm using in the program) to edit the paths. Rather, I'd like to have them edit one file to use on all the pages.
Any ideas on how this might work? I've been thinking about this very hard and can't come up with anything.
Then again, I'm a n00b
Also, how do I keep certain actions from happening until I submit a form? (The form and code are on the same page).
Thanks!
To include the page, I have to have the exact path to it. Since I'm going to distribute this program, that path is going to differ per each user. I don't want users to have to go through 4 pages (there would be 4 config files if I placed one in each folder that I'm using in the program) to edit the paths. Rather, I'd like to have them edit one file to use on all the pages.
Any ideas on how this might work? I've been thinking about this very hard and can't come up with anything.
Then again, I'm a n00b
Also, how do I keep certain actions from happening until I submit a form? (The form and code are on the same page).
Thanks!