error:

Duplicate key name ‘user_nicename’

>>> User tables will already exist when performing a database integrated installation.

Forum could not be created!

and

Step 1 – Creating database tables

>>> Create table bb_forums

>>> Create table bb_posts

>>> Create table bb_topics

>>> Create table bb_topicmeta

>>> Create table bb_tags

>>> Create table bb_tagged

>>> Added index wp_users UNIQUE KEY user_nicename (user_nicename)

>>>

>>>>>> Duplicate key name ‘user_nicename’

How can I fix this?

[@mdawaffe Member 16 years, 8 months ago]

What version of bbPress are you installing?

If you go to your bbPress site, does it work (even though the installer said it failed)?

I think there may be a bug in the bbPress installer such that if you want to integrate the user database, you must also check the cookie integration checkbox.

[@bryan868 Member 16 years, 7 months ago]

I’m having this same problem. Fresh installation using version 0.9.0.2.

Referrer is OK, beginning installation…

>>> Setting up custom user table constants



Step 1 - Creating database tables

>>> Create table bb_forums

>>> Create table bb_posts

>>> Create table bb_topics

>>> Create table bb_topicmeta

>>> Create table bb_tags

>>> Create table bb_tagged

>>> Added index wp_users UNIQUE KEY user_nicename (user_nicename)

>>>

>>>>>> Duplicate key name 'user_nicename'



Step 2 - WordPress integration (optional)

>>> WordPress address (URL): MYURL

>>> Blog address (URL): MYURL

>>> WordPress cookie secret key set.

>>> WordPress database secret set.

>>> User database table prefix: wp_



Step 3 - Site settings

>>> Site name: MYSITENAME

>>> Site address (URL): MYURL

>>> From email address: MYEMAIL

>>> Key master role assigned to existing user

>>>>>> Username: admin

>>>>>> Email address: MYEMAIL

>>>>>> Password: Your existing password

>>> Description: Just another bbPress community

>>> Forum could not be created!

>>> Key master email sent



There were some errors encountered during installation!

I should note that I assigned the key master as my admin user in WordPress. When I go to my forum I receive the following error….

Parse error: syntax error, unexpected T_STRING in /MYPATH/bb-config.php on line 22

[@jakemc Member 16 years, 6 months ago]

Check your BB_SECRET_KEY value. Mine (taken from the WP SECRET_KEY value ended with a backslash, which effectively escaped the end quote. Changing it to \ escaped the escape (if you see what I mean). I then went back and installed okay.

[@timjamz Member 16 years, 4 months ago]

This seems to be a problem with the install files. I have tried four different installations now, and integration causes the error with “user_nicename” in the wp_user table regardless of the correctness of all the other information (secret key, et al).

First run will produce the user_nicename error as well as the ‘Forum could not be created’ error. Second run will still produce the user_nicename error, but not ‘Forum could not be created’ – after the second run, the forum is installed and accessible… but cross-platform (wp -> bbp -> wp) cookie-based login is broken. Logging into the forum kicks the user off of the blog and vice versa.

I’m beating my head against a wall with this one. Anyone have any ideas?

Thanks for any help you can offer.

[@timjamz Member 16 years, 4 months ago]

I guess it’s a problem with the install wizard. I was able to get cookie-based cross-platform login going by performing a clean install without running the integration during install.

1. Perform a clean, standalone install and log in with the provided admin login.

2. Go to Settings . WordPress Integration – Input the blog URL twice, enter the blog ‘secret’ from [blog_url]/wp-admin/options.php, and enter the blog prefix.

3. Update the blog wp-config.php with the two lines suggested by WordPress Integration Settings page, and you should be in business.

Hope this helps someone else out there.

Used WP 2.5 & 2.5.1 – bbPress 0.9.0.2

[@estrahon Member 16 years, 4 months ago]

Thanks timjamz, that definitely worked as I was also having the same issues. I was stuck on this issue for weeks.