Summary
1) Remove requirement to install to site root directory.
2) Change distribution file structure to match server file structure.

Detail:
As I am investigating CMS options, I was very surprised to see that XOOPS dictates website structure. Why is it required to install XOOPS into the root directory? There are many reasons why this may not be appropriate. It is an easy fix for the developers to remove this requirement, so why establish it? The webmaster should determine the appropriate directory for XOOPS, not product developers. Most other CMS products (including Mambo) support this; XOOPS should too.

I was also surprised to see that the file structure used in the XOOPS distribution is not the same as what should be copied to the website. Huh? The files in the html distribution directory aren't copied to the html directory on the server? Then why distribute it this way? I should be able to copy the files 'as-is' to the folder of choice on my site, perhaps edit a config file, run an install program, and have the site working.

You folks are adding a lot of unneeded complexity to your install process for no reason on your side and to the detriment of your potential community.

The biggest gap blocking wider use of open source software is that developers who invest thousands of hours of time to create excellent products ignore the need to spend the extra 5% effort to document them or otherwise make them widely usable. As a result, hundreds of potential users must each manually inspect code to find out how things work or each adapt their environment to some arbitrary restriction. I understand that resources are limited, but I would much rather see 5% less features that are well documented or well thought-out. Instead, hundreds of people have to each spend 5-50 times the amount of one team's missing effort to gain the understanding necessary to use the product.

I don't agree that XOOPS requires itself to be installed in the root directory. I have placed the XOOPS installation scripts in subdirectories in several installations without having to make any changes what-so-ever to the installation routine. Create the directory you want XOOPS installed in, and copy the contents of the html directory to that directory. Pretty simple to me.

I think the documentation recommends that it is placed in the root directory - since that is the way most users will install it.

Your points about the distribution package structure itself have merit, as a frequently asked question is how do I remove the 'html' from my url. Which happens 'cause they copied the entire html directory to their webserver instead of the contents of the directory.

IMO If the structure of the download was modified slightly - both of your complaints are taken care of.

OK, I made the mistake of believing your docs - the installation worked fine to my subdirectory of choice. I still had to copy the files in the /html distribution folder to the XOOPS directory, but it worked.

The first time I read the docs I didn't get the wrong impression. I put it where I wanted it and was done. But that is just me I guess.

As mentioned, you can install XOOPS wherever you desire. You only need to know where you put it so you can install and configure it. Most people want it in the root and indeed install the html directory itself which is then a problem for them. You would copy everything *inside* the html dir to your root or other directory, pretty simple. Or you copy the whole html directory to where you desire. Tip: if you don't like the name "html" then rename it, very easy.

The file structure is straightforward and very common in the Open Source world. HTML files are under an html directory and other things are parallel. You don't normally install the extra folders inside the main application directory. But you can put files anywhere you wish. The only requirement is that you keep the file structure *beneath* html as is (actually you can do tricks with that too but is not basic).

You didn't mention documentation after install which as for most things free, lacking. However, the base application is top notch and the install is painless and easy. The install docs were very clear to me. It helps to have knowledge of basic webserver set-up which is reasonable considering the complexity of what XOOPS is actually doing and that you're putting content on a network. In general, things that are completely bullet proof and dummy proof are very restrictive in their requirements and limited in flexibility. XOOPS is neither of that. So I have to disagree with most of your issues.

Thanks for bringing this issue to out attention. Just to show that we do communicate here, I can now tell you that the matter has been now passed to the documentation writer for update consideration.

Pending changes, the installation document will be updated to clarify the point that XOOPS may indeed be installed in any sub-directory beneath your site root.

Let me add also that several installations of XOOPS my co-exist quite happily in discreet directories and with discreet databases, all under one server.


Richard