6
So you have:
home
|_public_html
| |_index.html
| |_index.php
| |_mainfile.php
| |_install
| |_modules
| |_system
|
|_xoops_trust_path
|_xoops_data
| |_configs
| |_caches
| |_smarty_cache
| |_smarty_compile
| |_xoops_cache
|_xoops_lib
|_modules
|_protector
Commonly you should have the directory structure as above for optimal security. See the move of xoops_data and xoops_lib outside the web root. It function also, but with less security, if they stay in the public_html.
home
|_public_html
|_index.html
|_index.php
|_mainfile.php
|_install
|_modules
| |_system
|_xoops_data
| |_configs
| |_caches
| |_smarty_cache
| |_smarty_compile
| |_xoops_cache
|_xoops_lib
|_modules
|_protector
Verify that at least the files and directories are present in the order shown. (there are a lot more of course).
However when you do not have your index.html in public_html, the web server should pick up automaticly the index.php. Are you sure you can execute php scripts in your webspace?
Can you start the installation process with yoursite.com/index.php ?
Alternative: XOOPS in a subdirectory (eg xoops):
home
|_public_html
| |_index.html
| |_xoops
| |_index.php
| |_mainfile.php
| |_install
| |_modules
| |_system
|
|_xoops_trust_path
|_xoops_data
| |_configs
| |_caches
| |_smarty_cache
| |_smarty_compile
| |_xoops_cache
|_xoops_lib
|_modules
|_protector
In this case index.html contains a link or timed redirect to yoursite.com/xoops/