Skip to:
Content
Pages
Categories
Search
Top
Bottom

DB Posts Table Not Installing

  • @super-artsy

    Member

    Alright, so after running the install. I get these errors:

    Your installation completed with some minor errors. See the error log below for more specific information.

    SQL ERROR!

    >>> Database: wp_blog (localhost)

    >>>>>> CREATE TABLE IF NOT EXISTS bbs_posts (

    post_id bigint(20) NOT NULL auto_increment,

    forum_id int(10) NOT NULL default 1,

    topic_id bigint(20) NOT NULL default 1,

    poster_id int(10) NOT NULL default 0,

    post_text text NOT NULL,

    post_time datetime NOT NULL default ‘0000-00-00 00:00:00’,

    poster_ip varchar(15) NOT NULL default ”,

    post_status tinyint(1) NOT NULL default 0,

    post_position bigint(20) NOT NULL default 0,

    PRIMARY KEY (post_id),

    KEY topic_time (topic_id, post_time),

    KEY poster_time (poster_id, post_time),

    KEY post_time (post_time),

    FULLTEXT KEY post_text (post_text)

    ) TYPE = MYISAM DEFAULT CHARACTER SET ‘utf8’;

    >>>>>> You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘TYPE = MYISAM DEFAULT CHARACTER SET ‘utf8” at line 16

    Key master email not sent!

    I have tried dropping all the bbPress tables and reinstalling it, but the problem still persists. I get this error message everytime after running the install script. I am running PHP 5.3.5 and MySQL 5.5.8 on a WAMP localhost server. Also, I am trying to integrate bbPress with my current WordPress blog…

    Thanks in advance,

    -Deuce

Viewing 6 replies - 1 through 6 (of 6 total)
  • @super-artsy

    Member

    Alright, well I find a solution to my problem with a bit of SQL language tweaking. Apparently the issue deals with my MySQL version, but all I had to do was make a simple edit changing ‘TYPE’ to ‘ENGINE’.

    So the line:

    ) TYPE = MYISAM DEFAULT CHARACTER SET 'utf8';

    becomes:

    ) ENGINE = MYISAM DEFAULT CHARACTER SET 'utf8';

    I hope this helps those who encounter the same problem.

    Cheers.

    @super-artsy

    Member

    Alright, well I find a solution to my problem with a bit of SQL language tweaking. Apparently the issue deals with my MySQL version, but all I had to do was make a simple edit changing ‘TYPE’ to ‘ENGINE’.

    So the line:

    ) TYPE = MYISAM DEFAULT CHARACTER SET 'utf8';

    becomes:

    ) ENGINE = MYISAM DEFAULT CHARACTER SET 'utf8';

    I hope this helps those who encounter the same problem.

    Cheers.

    @yunglion

    Member

    what file exactly do i change that in?

    @yunglion

    Member

    what file exactly do i change that in?

    @yunglion

    Member

    thank you a lot man it worked for me.

    @yunglion

    Member

    thank you a lot man it worked for me.

Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.
Skip to toolbar