The setup of my blog (wordpress 206) needs an useroline plugin (- WP-UserOnline -) that runs 100% under my localhost.
However, while installing this plugin under host-server (on air), I received this message:
WordPress database error: [You have a sintaxe error on your SQL ...... near to 'ENGINE=MyISAM DEFAULT CHARSET=latin1' line 1]
CREATE TABLE ra_useronline ( timestamp int(15) NOT NULL default '0', userid int(10) NOT NULL default '0', username varchar(150) NOT NULL default '', displayname varchar(255) NOT NULL default '', useragent varchar(255) NOT NULL default '', ip varchar(40) NOT NULL default '', location varchar(255) NOT NULL default '', url varchar(255) NOT NULL default '', type enum('member','guest','bot') NOT NULL default 'guest', UNIQUE KEY useronline_id (timestamp,username,ip,useragent)) ENGINE=MyISAM DEFAULT CHARSET=latin1;
Warning: Cannot modify header information - headers already sent by (output started at /home/users/rxxxxx/wp-includes/wp-db.php:104) in /home/users/rxxxxx/wp-includes/pluggable-functions.php on line 270"
1) first of all, that my localhost (in my test environment) is OK and
2) second, that there are an error on external server (something relevant on MySQL configuration or database created for my personal use on my blog in the external server):
a) This is the same problem that I have when I try to configure wordpress to accept registered users (in System Admin, Options, users);
b) And, more than this, the same error I have when I try to install wordpress (for the first time, in the second step - "now, we are going do create tables").
--> I solved the problem on item (a) closing users registration form - this is not the right way, but this is a procedure to avoid problems while I 'm trying to understand what is going on.
--> I solved the problem on item (b) forcing the first password (the password of ADMIN manually and - after that crippled instalation changing the password).
All problems are around that MySQL error a--> You have an error... 1064...
How can I solve this problem on MySQL - this is not a specific WordPress problem, I think, but, can someone help me?