| Re: New 2.5.9 install path problem |
| by Mamba on 2017/10/15 4:54:28 Good to hear that everything is working now! |
| Re: New 2.5.9 install path problem |
| by Dante7237 on 2017/10/14 12:07:52 Thanks for the help guys. I just replaced the mainfile with an empty stock one and the installer still fails at step 4. There is no prompt for input, and it continues to look in cms root for the lib and data folders. Shux. I just noticed the fields on step 4 are editable. It isn't exactly easy to tell.. Gimme a second. Yup, that was it.... hahaha Thanks again. |
| Re: New 2.5.9 install path problem |
| by geekwright on 2017/10/13 16:21:15 Quote:
Right! There is no mainfile.php before the installer runs. Enter the correct paths when prompted, and it will verify them. After that, the installer will create the new mainfile.php once all the needed information has been gathered. Here is the relevant documentation on GitBook. |
| Re: New 2.5.9 install path problem |
| by Dante7237 on 2017/10/13 10:20:14 As long as I've used xoops the mainfile needed to be edited to reflect paths "before" the installer runs. So you're telling me that the installer will prompt me for input rather than expecting paths to be present in mainfile? |
| Re: New 2.5.9 install path problem |
| by Mamba on 2017/10/13 9:06:37 1) the install process creates the "mainfile.php" for you. If you don't have it, i.e. that the installation was NOT successful. You do NOT use/modify the "mainfile.dist.php" - that's only for XOOPS. 2) During installation, you specify where the lib and data paths are, so the system can check if they exist. If they are not, the process will not continue. So making changes after the installation manually is risky, unless you know what you're doing. My recommendation: install again, with the correct paths provided to XOOPS during installation. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|