With Metadot Version 4.6.1 and higher, it is possible, for a virtual server configuration, to select on a per-virtual-server basis the gizmos that you want to make available for each server. This can be useful if you are using a specialized gizmo that you want to make available, e.g., to only one of your virtual server sites.
To enable this feature, create the table vserv_modules, as it
is defined in <metadot>/metadot/sampledata.sql. (If you have loaded the
sampledata file, then it will already be defined). Create this table in each
virtual server database for which you want to restrict the set of gizmos.
Then, for each table (in each virtual server database), insert a row into the vserv_modules table. Set the 'name' field to be the name of the server config block for the given virtual server, in your metadot.conf file. Set the 'modules' field to be a list the names of the gizmos that you want to include for the server, comma-separated, with no white space between the items in the list. For example, the following might be a typical entry, where "<vserv block>" is replaced by the actual name of the server config block in metadot.conf:
insert into vserv_modules values('<vserv block>',
'Item,ImageItem,Category,Poll,Discussion,Newsitem,Table,GizmoShortcut,NewsPaperView,Faq,CMSDocument,Calendar');
If such an entry exists in the virtual server's vserv_modules table, corresponding to its server block name in metadot.conf, then it will make only the listed modules available through the site's "Add.." menu via which gizmos are added as page content.
If the system can't find an entry in the vserv_modules table matching the site's server block name, or if the table does not exist, then no restriction of module availability will occur.
© Copyright Metadot Corporation 2002. All rights reserved.