http://wordpress.org/support/ WordPress › Support Topic: [Plugin: Profiles] Claims tables already exist... en Tue, 24 Nov 2009 11:49:36 +0000 http://wordpress.org/support/topic/272137#post-1079106 Wed, 20 May 2009 19:49:24 +0000 The Living Legend 1079106@http://wordpress.org/support/ <p>Sweet. Looking forward to it because I just tried the Profiler plugin and it's caused all my plugins to dissappear (this happens more often than I'd like, but a number of plugins don't cause this so hopefully yours won't either). </p> http://wordpress.org/support/topic/272137#post-1078269 Tue, 19 May 2009 21:49:20 +0000 jwriteclub 1078269@http://wordpress.org/support/ <p>2.0 is not at all stable in 2.6+.</p> <p>I'm working on 3.0, should be released within the month.</p> <p>~ Christopher<br /> Profiles Author </p> http://wordpress.org/support/topic/272137#post-1078157 Tue, 19 May 2009 20:03:59 +0000 The Living Legend 1078157@http://wordpress.org/support/ <p>When I activated the plugin, the header (at the very top, above the normal header of the admin area) of the page displayed the following message:</p> <blockquote><p>WordPress database error: [Table 'wp_people' already exists]<br /> CREATE TABLE <code>wp_people</code> ( <code>id</code> int(11) NOT NULL auto_increment, <code>first_name</code> varchar(30) default NULL, <code>last_name</code> varchar(30) default NULL, <code>slug</code> varchar(60) NOT NULL, PRIMARY KEY (<code>id</code>) ) ENGINE=MyISAM </p> <p>WordPress database error: [Table 'wp_bios' already exists]<br /> CREATE TABLE <code>wp_bios</code> ( <code>id</code> int(11) NOT NULL auto_increment, <code>uid</code> int(11) NOT NULL default '0', <code>text</code> longtext NOT NULL, <code>photo</code> blob, PRIMARY KEY (<code>id</code>) ) ENGINE=MyISAM</p></blockquote> <p>I knew those tables didn't exist because I'd just made a backup of the database, so I deleted their entries and the plugin, clicked again on the plugins page and it was returned to normal (note: when this error occurred it cleared my plugins page of all plugins). I checked the database to varify that the tables didn't exist, re-uploaded the plugin and activated it... Same thing happened again.</p> <p>There could be a simple explanation for this, or it could be a bug that needs fixed. </p>