3
Hello rrettich -
As Herko mentioned above...(just noticed...my apologies for being redunant)
Would you/Could you send some additional detail regarding your installation environment such as OS, etc, etc..?
It could be an access problem..i.e. execution permissions, not permitted to view the files at all, .htaccess file, etc, etc (who knows sometimes?)... if you install it locally (via files, instead of HTTP)via root on a Unix system and are testing via an external browser as an non-privileged user...sometimes that can trip you up.
As you can see, I altered my signature to reflect my XOOPS server environment. (I was asking a lot of questions at the time, it saved a lot of typing)
In my past, I tried to place XOOPS immediately into my web taxonomy, i.e. no applications under
, etc, etc... no dice & some frustration (understatment)
To get my insanity to return, I moved my XOOPS directory to be immediately under the Apache/htdocs...bingo..with sanity restored, I moved it around to where I wanted the XOOPS directory to reside. Of course, I did have to make some adjustments to the Apache httpd.conf file, but who doesn't look forward to doing that. (despite being a server geek, I just wanted to see XOOPS work first before I got all nerdy on server infrastructure issues)