#1

Re: Instruction 1.07 RC1 for XOOPS 2.5.9 and PHP 7.1 Released for Testing

Yesterday 20:03 Module for creating structured pages with a tree-like menu. In the examples, everything is visible.

#2

Re: Instruction 1.07 RC1 for XOOPS 2.5.9 and PHP 7.1 Released for Testing

Yesterday 19:27 hi aerograf

thank you for sharing. Is somewhere a description what this module is doing and for what it can be used?

#3

Re: Xoops Partners 2.0 Beta 1 ready for testing

Yesterday 16:16 The blocks are showing the inactive partners, I've modified the blocks/partners.php file to omit these records, already sended a pull request to git.

on line 71 change:



to

#4

Re: New 2.5.9 install path problem

10/15 4:54 Good to hear that everything is working now!

#5

Re: New 2.5.9 install path problem

10/14 12:07 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.

#6

Re: New 2.5.9 install path problem

10/13 16:21 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.

#7

Re: New 2.5.9 install path problem

10/13 10:20 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?

#8

Re: New 2.5.9 install path problem

10/13 9:06 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.

#9

Re: New 2.5.9 install path problem

10/12 11:46 So I looked at my last cms install and noticed a difference in mainfile names.
The previous installed cms had the file named "mainfile.php".

The 2.5.9 install has the file named as "mainfile.dist.php".
Renaming the file to "mainfile.php" throws a server error on access....

I recall some subtle thing about this, just not exactly what.

(I will mention here that the installer guide has 0 info about editing this file before install. Which makes those instructions useless to newcomers.)

#10

Re: New 2.5.9 install path problem

10/12 11:14 Yeah, I have.
The installer keeps looking in cms root instead of what I declared in mainfile.