We are in the process of migrating this forum. A new space will be available soon. We are sorry for the inconvenience.

Blad podczas instalacji


dzwonal
27-01-2006, 13:28
Zarowno przy mambo jak i Joomli:

na drugim kroku instalacyjnym:

SQL=Specified key was too long; max key length is 1000 bytes SQL=# Table structure for table `jos_core_acl_aro`\n\nCREATE TABLE `jos_core_acl_aro` (\n `aro_id` int(11) NOT NULL auto_increment,\n `section_value` varchar(240) NOT NULL default \'0\',\n `value` varchar(240) NOT NULL default \'\',\n `order_value` int(11) NOT NULL default \'0\',\n `name` varchar(255) NOT NULL default \'\',\n `hidden` int(11) NOT NULL default \'0\',\n PRIMARY KEY (`aro_id`),\n UNIQUE KEY `section_value_value_aro` (`section_value`,`value`),\n UNIQUE KEY `jos_gacl_section_value_value_aro` (`section_value`,`value`),\n KEY `hidden_aro` (`hidden`),\n KEY `jos_gacl_hidden_aro` (`hidden`)\n) TYPE=MyISAM:
- - - - - - - - - -
# Table structure for table `#__core_acl_aro`

CREATE TABLE `#__core_acl_aro` (
`aro_id` int(11) NOT NULL auto_increment,
`section_value` varchar(240) NOT NULL default '0',
`value` varchar(240) NOT NULL default '',
`order_value` int(11) NOT NULL default '0',
`name` varchar(255) NOT NULL default '',
`hidden` int(11) NOT NULL default '0',
PRIMARY KEY (`aro_id`),
UNIQUE KEY `section_value_value_aro` (`section_value`,`value`),
UNIQUE KEY `#__gacl_section_value_value_aro` (`section_value`,`value`),
KEY `hidden_aro` (`hidden`),
KEY `#__gacl_hidden_aro` (`hidden`)
) TYPE=MyISAM
= = = = = = = = = =