Hi Kristina,
Sorry for the delayed reply and Happy New Year!
I am afraid that adding the module to the config does not automatically add the table to the database. That needs to be done manually.
The SQL for a cxt module is:
CREATE TABLE IF NOT EXISTS `cxt_tbl_cxt` (
`cxt_cd` varchar(30) COLLATE utf8_unicode_ci NOT NULL DEFAULT '',
`cxt_no` int(10) NOT NULL DEFAULT '0',
`ste_cd` varchar(10) COLLATE utf8_unicode_ci NOT NULL DEFAULT '0',
`cxttype` int(3) NOT NULL DEFAULT '0',
`cre_by` int(4) NOT NULL DEFAULT '0',
`cre_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`cxt_cd`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;
CREATE TABLE IF NOT EXISTS `cxt_lut_cxttype` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`cxttype` varchar(255) NOT NULL DEFAULT '',
`cre_by` int(11) NOT NULL DEFAULT '0',
`cre_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
PRIMARY KEY (`id`)
) ENGINE=MyISAM AUTO_INCREMENT=10 DEFAULT CHARSET=utf8
INSERT INTO `cor_tbl_module` VALUES (10,'cxt_cd','mod_cxt','cxt','A core module for adding markup and aliases',1,NOW());
/*!40000 ALTER TABLE `cor_tbl_module` ENABLE KEYS */;
INSERT INTO `cor_tbl_alias` (alias, aliastype, language,itemkey,itemvalue,cre_by,cre_on) VALUES ('Context',1,'en','cor_tbl_module','10',1, NOW());
For other modules replace ‘cxt’ and the module number (in this case cxt is module 10).
We do provide pre-configured a pre configured ARK for single context, and we are working on producing more for future releases.
Thanks,
Mike