Skip to:
Content
Pages
Categories
Search
Top
Bottom

Error when trying to create a group

  • Avatar of Zenseeker
    zenseeker
    Participant

    @zenseeker

    Posted this over at testbp.com, but perhaps should have put it here.

    I just upgraded to trunk-r640 this morning and I’m getting this error making a group: “There was an error saving group details. Please try again.” My bp-groups folder permissions is set to 755 and bp-groups.php is set to 644. Files inside of bp-groups are at 644. Any help or suggestions would be most appreciated. Thanks.

Viewing 18 replies - 51 through 68 (of 68 total)
  • Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    Yes, I’m definitely logging into the admin area as site admin. I’ve tried just about everything, but the only solution has been for me to pre-create the tables “manually”…BP just won’t do it no matter what I try.

    @burtadsit I’m poring through log file now, but I had already posted (earlier in this thread) what appeared to be the relevant portions of the log when invoking BP to create tables, etc. I’ll keep looking, but nothing’s jumped out — first sign of trouble is when it can’t find the tables during operations subsequent to when they’re supposed to have been created.

    Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    Is this creating the problem: “DEFAULT CHARACTER SET utf8″ ??

    From the Apache error log, this is the same syntax error I saw earlier when BP was trying to create tables (see earlier posts):

    [suexec 11180] Chdir to /kunden/homepages/14/d123456789/htdocs/exploreouroceans

    [suexec 11180] Executing PHP4 /usr/lib/cgi-bin/php4 /kunden/homepages/14/d123456789/htdocs/exploreouroceans/index.php

    WordPress database error 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 ‘DEFAULT CHARACTER SET utf8′ at line 14 for query CREATE TABLE wp_user_3_activity (

    id int(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,

    item_id int(11) NOT NULL,

    secondary_item_id int(11),

    user_id int(11) NOT NULL,

    component_name varchar(75) NOT NULL,

    component_action varchar(75) NOT NULL,

    date_recorded datetime NOT NULL,

    is_private tinyint(1) NOT NULL,

    KEY item_id (item_id),

    KEY user_id (user_id),

    KEY is_private (is_private),

    KEY component_name (component_name)

    ) DEFAULT CHARACTER SET utf8; made by dbdelta

    Check the permissions on your mysql user. That might be the only other issue here. It has to have proper rights and access to your database. Something else to check on anyways.

    Trent

    Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    Thanks for your reply. I’ve never had to fiddle with mysql user permissions with other WP databases — where is this done? I tried entering, “DEFAULT CHARACTER SET utf8″ (sans quotes) manually via phpMyAdmin and received the same syntax error message. Is this a clue or a rabbit hole?

    You are not using an older version of hyper-db or the multi-db plugin from wpmudev.org premium are you? Both need to be patched to work with functions and delta-db. Latest trunk of hyper-db works, but multi-db plugin needs to have a few functions added to it until they release a version for 2.7 and/or buddypress integration.

    Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    I’m using wordpress-mu-2.6.5 and bp combo beta. No other plug-ins, etc.

    Avatar of Burt Adsit
    Burt Adsit
    Participant

    @burtadsit

    The big guns have arrived. (whew)

    Do you have phpMyAdmin running? Can you go to it or whatever Database admin program that your host gives you and then run the following command on your database?

    CREATE TABLE wp_user_3_activity (
    id int(11) NOT NULL AUTO_INCREMENT PRIMARY KEY,
    item_id int(11) NOT NULL,
    secondary_item_id int(11),
    user_id int(11) NOT NULL,
    component_name varchar(75) NOT NULL,
    component_action varchar(75) NOT NULL,
    date_recorded datetime NOT NULL,
    is_private tinyint(1) NOT NULL,
    KEY item_id (item_id),
    KEY user_id (user_id),
    KEY is_private (is_private),
    KEY component_name (component_name)
    )

    See if it will actually create the tables manually?

    Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    Ran it in phpMyAdmin. Worked just fine.

    Avatar of Burt Adsit
    Burt Adsit
    Participant

    @burtadsit

    Hey guys what is this ‘made by dbDelta’ stuff?

    It’s in both his err logs near the charset collation spec. That seems to be what mysql is complaining about.

    In code it just appends ‘{$charset_collate};’ where did this come from?

    Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    I do think we’ve zeroed in on the problem. In phpMyAdmin, this (which resembles the syntax that BP is creating) results in the syntax error that follows:

    CREATE TABLE testme (

    field1 int(11) ,

    field2 varchar(100) NOT NULL

    ) DEFAULT CHARACTER SET utf8

    #1064 – 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 ‘DEFAULT CHARACTER SET utf8′ at line 4

    The following works, however (removing the word “DEFAULT” from the last line):

    CREATE TABLE testme (

    field1 int(11) ,

    field2 varchar(100) NOT NULL

    ) CHARACTER SET utf8

    If I type in “DEFAULT CHARACTER SET utf8″ or “DEFAULT CHARACTER SET latin1″ or anything with the word “DEFAULT,” I get the syntax error. I’m running MySQL 5.0.32 and PHP 4.4.9

    As a temporary workaround, what if I simply nuked the word “DEFAULT” from the code for now? Reckless?

    Avatar of Burt Adsit
    Burt Adsit
    Participant

    @burtadsit

    This is an Andy question. Modifying bp core is of course a pain to maintain. You, of course, can do anything you like. But…

    Avatar of Oceandoctor
    oceandoctor
    Member

    @oceandoctor

    I can confirm that globally changing “DEFAULT CHARACTER SET” to “CHARACTER SET” in all bp code prior to installation appears to solve the problem. All databases are created successfully and automatically once I enter the back-end admin area as admin. Everything seems to work based on a quick shakedown. There seems to be hope. But do tell, what does it all mean? And are there any adverse consequences of my desperate code fiddling?

    Avatar of Mike Pratt
    Mike Pratt
    Participant

    @mikepratt

    back to the original part of this topic…was there ever talk of NOT making the 2rd field (recent news) in Group creation a required field? Doesn’t seem so necessary.

    Avatar of Burt Adsit
    Burt Adsit
    Participant

    @burtadsit

    @oceandoctor the real question is why didn’t it work and what are the implications of that?

    @mikepratt I would create a ticket in trac an a future enhancement for that. Might catch on with people as I had trouble creating groups due to that as well. Darn required fields ;)

    Avatar of Andy Peatling
    Andy Peatling
    Keymaster

    @apeatling

    The fix for the original problem: make sure you are running MySQL 4.1 or greater.

    Hi zenseeker,

    You have the following error message on http://www.artistswap.com:

    Problem in wp-config.php – $base is set to BASE when it should be the path like “/” or “/blogs/”! Please fix it!

    In my opinion you are trying to install WordPress Mu manually , by editing wp-config.php file (just like WordPress) and I think that it’s not really a good method.

Viewing 18 replies - 51 through 68 (of 68 total)

You must be logged in to reply to this topic.