Yes, my tables prefix is "wsnlinks_" but I got an error:
SQL-query :
ALTER TABLE `wsnlinks_comments` CHANGE `time` `time` INT( 11 ) DEFAULT '0' NOT NULL
MySQL said:
#1089 - Incorrect sub part key. The used key part isn't a string, the used length is longer than the key part or the table handler doesn't support unique sub keys
Comments on View Comments Bug
Beginner
Usergroup: Member
Joined: Dec 06, 2004
Total Topics: 2
Total Comments: 4
I just finished upgrading to 3.13 from the basic version 2.56b.
When I click on Comments(n) where "n" is 1 or higher, I get an all white page that says:
"Timestamp is not numeric, it is time. Please report this bug."
When I click on Comments(0), it appropriately takes me to the add a comment screen.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Upgrade issue. Run this query:
ALTER TABLE `wsnlinks_comments` CHANGE `time` `time` INT( 11 ) DEFAULT '0' NOT NULL
(presuming your tables prefix is wsnlinks_)
Beginner
Usergroup: Member
Joined: Dec 06, 2004
Total Topics: 2
Total Comments: 4
Yes, my tables prefix is "wsnlinks_" but I got an error:
SQL-query :
ALTER TABLE `wsnlinks_comments` CHANGE `time` `time` INT( 11 ) DEFAULT '0' NOT NULL
MySQL said:
#1089 - Incorrect sub part key. The used key part isn't a string, the used length is longer than the key part or the table handler doesn't support unique sub keys
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Perhaps you have to run UPDATE TABLE `wsnlinks_comments` SET time='0' WHERE time='time'; first in your case.
Anyhow, for future refernce this is an upgrade issue.