Using IXWebhosting as service provider. Uploaded all files from htdocs by FTP to site root folder. Moved _data & _lib out of site root up one level. Made sure all necessary folders & files writable.

Step 4 in installation gives:
"No XOOPS installation could be found in the specified folder."
/hsphere/local/home/<accountname>/<sitename>.org

Strangely, it finds the other two folders just fine:
/hsphere/local/home/<accountname>/xoops_data
/hsphere/local/home/<accountname>/xoops_lib

I made a file 'rootpath.php' in root site folder. dirname(__FILE__) replies:
/hsphere/local/home/<accountname>/<sitename>.org

mainfile.php is writable. all checks to that point are ok. Capital letters in folder names not an issue (there are none). I even tried moving the data & lib folders back under site root with no progress. Installation DID find the two folders both times correctly. Doesn't make sense that it could find the other two folders and not the root physical path.

No joy googling any answers or searching the forums here. Any suggestions appreciated.

--update--
Successful install into a sub-web. Scraping original directory and trying again...

--update2--
Complete reinstall into a blank directory gave same results. Installed and configured sub-domain successfully. Weird. Copied mainfile.php over to root web, changed XOOPS_ROOT_PATH & XOOPS_URL, seems to work fine. Not an answer to the malfunction but, a workaround. Haven't tried doing anything but, it's up into admin without error.

Did anyone find a real sollution?

I have the same problem with a clean installation of XOOPS 2.3.1 : it finds xoops_lib and xoops_data without any problem, but it cannot detect the httpdocs directory...

I even tried to put all files in a subdirectory, without success...

-UPDATE-
A clean 2.3.0 installation is working without any problems... so for the time being, I will install 2.3.0 and upgrade to 2.3.1

Quote:
Shouldn't that be:
/hsphere/local/home/<accountname>/public_html
or
/hsphere/local/home/<accountname>/ht_docs

?

SailJapan,

That is not the problem...
The directory IS working with the 2.3.0 installation, but is NOT working with the 2.3.1. installation...

So there is "some" difference between 2.3.0 and 2.3.1. ...

I have the same issue, but even 2.3.0 won't work. Is there an answer for this issue?

Quote:It seems to me that some Apache or php.ini configuration settings are not set correctly. You may contact your hoster for it.

Check your /mainfile.php for all path and url definitions.
The XOOPS_URL should align with what you type in your browser to surf to your XOOPS site (without trailing / ).
The XOOPS_ROOT_PATH should correspond to the path you see in your websites filemanger in your website admin panel (eg cPanel)(also without trailing / ). If Apache is correctly setup, then it corresponds also with the value shown in document_root in the Apache table from php info.
The other paths and url's are derived from those two.

The problem is that the function checks for mainfile.php *and* whether XOOPS_VERSION is defined. Unfortunately, XOOPS_VERSION is not defined for the install routine. add to install/include/common.inc.php and re-run the install.