I have extensively used the multisite module by Mr. Jan
Pederson for about 21 subsites. Through this I saw that
it could be really very very difficult to configure all
of them. Ofcourse this was just a module that did a
However, I think that if some of the fundamental
factors in the new development is layed, it would be
Giving thoughts to this wish, I came to the following
idea and wish that it could be implemented:
There are 3 tables that are really controlling
everything within xoops database. If there was one more
field $sitegroup in the exististing database, that
would really solve the entire problem.
By doing so, the existing tables of xoops_config,
xoops_category and xoops_configoptions an extra
dimension to work with that through this the entire
database could be used and multiplied. Hence the field
$sitegroup would be the main multi-plicator of the
Therefore, it would be necessary to have the first
PRIMARY TABLE as the MASTER TABLE known as
xoops_sitegroups!!! This table would then be
responsible to install one or more sites.
This is the table that would then be responsible during
the BOOT SEQUENCE by the kernel of xoops. In this
table, some basic information would be stored, like
paths and other informations.
During the installation, the installer will only
install the primary site and make the access possible.
Thereafter it would be possible to get in the
Hence, this follows a theory, that all the other tables
that are required should also get the variable fields
like xoops_modules, xoops_blocks, xoops_groups, etc.
Also, here in the PRIMARY TABLE as the MASTER TABLE,
there could be possibily a field $lang that tells the
code of the language givin a multi-language feature.
The only thing which in each and every table that
should be refected is the $sitegroup variable! That
shall bring a multisite and multi-language feature to
the entire database!!!
Does this idea of mine make sense?
Log in to post a comment.