Problem with new modules

New Member Joined: May 26, 2007 Posts: 9

Hello.

Iam having trouble with new modules not appering in the module list at the administration page.

The installation is not a fresh one but an upgrade from 2.02.02.

The current installed version is 2.10.01.

Ill take it from the start. I were having trouble with not being able to move the blocks. When i choose left or right, the settings didnt work. No changes and everything went back like before the changes. By searching your forum i found a fix for this.

ALTER TABLE `nuke_blocks` ADD `groups` TEXT NOT NULL AFTER `view`;
ALTER TABLE `nuke_message` ADD `groups` TEXT NOT NULL AFTER `view`;
ALTER TABLE `nuke_modules` ADD `groups` TEXT NOT NULL AFTER `view`;

I have been searching for a simular solution for the modules but i havent found anyone. So the remaining trouble is that the new installed modules doesnt appear in the list. If i take an old one which is in the list and change its foldername, it disapears and the new one dont show itself either.

Here's my table structure for modules

CREATE TABLE `nuke_modules` (
`mid` int(10) NOT NULL auto_increment,
`title` varchar(255) NOT NULL default '',
`custom_title` varchar(255) NOT NULL default '',
`active` int(1) NOT NULL default '0',
`view` int(1) NOT NULL default '0',
`groups` text NOT NULL,
`inmenu` tinyint(1) NOT NULL default '1',
`mod_group` int(10) default '0',
`admins` varchar(255) NOT NULL default '',
`mcid` int(11) NOT NULL default '1',
`url` varchar(255) default '',
PRIMARY KEY (`mid`),
KEY `mid` (`mid`),
KEY `title` (`title`),
KEY `custom_title` (`custom_title`)

Hopefully, this is just a nooberror that i have caused Embarassed

Any suggestions?

registered · Posted: Mon Feb 04, 2008 5:04 pm

RavenNuke doesn't seem to use 'mcid' or 'url' anywhere I can find

Posted: Mon Feb 04, 2008 6:34 pm

Problem solved.

I got rid of the mcid and url tables. While i was doing that i saw an error message in phpmyadmin where it sayd that column mid cannot be both an index and o primary key. So i removed the index key and now it works perfect.

I hope i havent done anything i should't

Thanks for the hint evaders Smile

Posted: Mon Feb 04, 2008 6:41 pm

Maybe i did something that i should't have done.

I took a look in the blocks table and same here, the same warning.

PRIMARY KEY (`bid`),
KEY `bid` (`bid`),
KEY `title` (`title`)

???

My admin says this:
PRIMARY and INDEX keys should not both be set for column `bid

Posted: Tue Feb 05, 2008 12:19 am

That "PRIMARY and INDEX" error is a result of the database created by phpNuke's .sql file. It is a warning from phpMyAdmin... it does not create any problems with running the site. Best to remove the index key when you can, but it isn't critical.