[ckpepper02]

GOT IT!!!

Turns out the default forum user role was set to participant upon activation. This was blocking my access to the Forum Admin button. To get around this, I had to create a new WP user account, set it as an administrator, and the change the Forum role of my original username to Moderator. When I logged back in, I can see the Forum button.

Hope this helps someone else!

[ckpepper02]

GOT IT!!!

Turns out the default forum user role was set to participant upon activation. This was blocking my access to the Forum Admin button. To get around this, I had to create a new WP user account, set it as an administrator, and the change the Forum role of my original username to Moderator. When I logged back in, I can see the Forum button.

Hope this helps someone else!

[John James Jacoby]

My short answer is to turn off bbPress’s built in per-topic notifications, and build your own.

Since it’s a blanket on/off for each user, save a usermeta option whether or not they’ve opted in; save this when they create their account. There are plenty of actions and filters in the default profile templates that will allow you to intercept the input/output process, so adding an additional field is not too difficult, though not exactly easy either (lots of touch points.)

In all, this could be built as a completely self-contained plugin, and released to the community. I’d be surprised if someone isn’t already trying to build the same thing.

[Erlend]

Defaulting to plain-text, like bbpress.org now does, seems like a perfectly good compromise to me.

[verlaine76]

I know this was a while ago, but in case anyone else stumbles across this topic, here’s how I did it.

In your wordpress install find the folder `/wp-content/plugins/bbpress/templates/default/css`

Open the file `bbpress.css` in a text editor
Within the bbpress.css file, search for the text `#bbpress-forums .status-closed`

When you find this text, below is the entry `color: #ccc;` This is the colour for your text in closed topics. Change it to #000 for black.

[moebis]

Not sure if this is a bbpress or buddypress issue (BTW can’t post on buddypress support forums, when I log in to bbpress.org, but that’s a separate issue, I also see the admin menu on buddypress.org)…

Ok, so I’ve been playing around with both bbpress and buddypress for the last 2 weeks. I have checked out of svn both of the latest trunk versions. I’ve gotten pretty adept at setting everything up from scratch during my testing. When creating a group, let’s say “group1” in buddypress, I allow bbpress to create the corresponding forum during group setup. Now, when I go into the bbpress admin backend and create a forum from there, let’s say “subforum1” and make “group1” the parent, it works. Yeah! Just what I wanted, parent groups and sub-forums, however, it doesn’t work the way I expect it to. I can see the subforum in the group now from the front end, and post something in the subforum, but not in the main forum/group “group1”, and every time I click on the group, and then the forum tab, it shows the sub forum(s) and topic posts (only from the last post to the last subforum), and then a create topic form on the bottom, defaulting to the last subforum I created. Meaning I can never post anything in the parent forum “group1” or any other subforums that might have been created under group1. No dropdown to select a different forum to post it to. This is not how would expect it to work. I would expect that you default to the main parent forum (group1) for posting and reading of topics, and the subforums (which do show on the group1 forum page) you can click on and then post within them. It seems this functionality is almost there, and I want to make sure this is either something that is getting fixed, or a mistaken capability that I stumbled upon and it not meant to operate that way.

Thanks for all of you hard work on these 2 projects, you guys are awesome! I can help contribute to the dev as a tester if you want.

[Lynq]

The bbPress theme is inside the plugin and inherits your wordpress themes styling.

If you wish to change that then you need to copy the theme files out of the plugin and into your wordpress theme. The theme files are inside templates/default I believe.

Copy them out into your wordpress theme and then edit those files to get your preferred look, good luck!

[rossagrant]

Just to update on testing too, I have fully tested this now and can recreate it on all of my installs and a brand new install of BP 1.6.3, WP 3.5 and BBPress 2.2.4.

Admin can post @mentions freely, but regular BP members (assigned participant role) can’t without that error in the log appearing.

The @mention still works as it should but I can’t for the life of me see why it’s throwing that error.

I’ve tried it and get the same result on 3 separate servers now too. I have tried it with BP-Default and NO plugins except for BP and BBPress.

If you guys need me to test anything else at all, please shout up.

Should I create a ticket in TRAC?

[singitlow]

Hi, I encounter the very same problem with my 3.5 installation. When logged in, the forum is not found anymore.
I already tried to “Remap existing users to default forum roles”, since it works when the role of a user is set to Keymaster, but that brought no solution. I also checked different browser. The same problem.
Well, I´d be happy for a hint. Thank you in advance,
singitlow

[Erlend]

When you you think images uploading problem will be fixed? I mean that default users can’t upload images now using TyniMCE editor.

I think that’s intentional for now. See this:
bbPress dev chat summary Jan 9, 2013

[Michael]

Okay, I think I figured this out on my own, though I don’t quite have the list of usable html matching what the default TinyMCE editor offers.  I’ll have to play with that separately.

What I did was add a function in my functions.php file that changed the allowed markup for all bbPress (and blog) posts to include what I think is a reasonable list AND is still safe. I’ve added the IMG tag as well — for my Forum that’s a useful feature, and I’ll just have to monitor what people post in terms of image links.

Here’s the code I added to my functions.php file:

add_action('init', 'my_html_tags_code', 10);
function my_html_tags_code() {
        define('CUSTOM_TAGS', true);
        global $allowedposttags, $allowedtags;
        $allowedposttags = array(
                'p' => array(
                        'style' => array()),
                'strong' => array(),
                'em' => array(),
                'i' => array(),
                'del' => array(),
                'h1' => array(),
                'h2' => array(),
                'h3' => array(),
                'h4' => array(),
                'h5' => array(),
                'hr' => array(),
                'blockquote' => array(),
                'q' => array(),
                'pre' => array(),
                'span' => array(
                        'style' => array()),
                'div' => array(
                        'style' => array()),
                'ul' => array (),
                'ol' => array (
                        'start' => array()),
                'li' => array (),
                'a' => array(
                        'href' => array (),
                        'title' => array (),
                        'rel' => array()),
                'img' => array (
                        'src' => array(),
                        'width' => array(),
                        'height' => array(),
                        'alt' => array())
        );
        $allowedtags = array(
                'p' => array(
                        'style' => array()),
                'strong' => array(),
                'em' => array(),
                'i' => array(),
                'del' => array(),
                'h1' => array(),
                'h2' => array(),
                'h3' => array(),
                'h4' => array(),
                'h5' => array(),
                'hr' => array(),
                'blockquote' => array(),
                'q' => array(),
                'pre' => array(),
                'span' => array(
                        'style' => array()),
                'div' => array(
                        'style' => array()),
                'ul' => array (),
                'ol' => array (
                        'start' => array()),
                'li' => array (),
                'a' => array(
                        'href' => array (),
                        'title' => array (),
                        'rel' => array()),
                'img' => array (
                        'src' => array(),
                        'width' => array(),
                        'height' => array(),
                        'alt' => array())

        );
}

[choibc]

I am pleased to release this clean theme for non-tech people.
It is basically bootstrap child theme and bbpress styling of default bbpress template.
I have hard time to figure out new bbpress plugin and theme. Now I have some clue…with lots of googling. One thing I couldn’t do is “Previous/Next Topic” navigation while seeing single topic.

Please refer here to download theme.
WordPress Bootstrap + bbPress

Any suggestion welcome.

[Stephen Edgar]

The docs are now up also,

@brokentwig Key changes from your great work getting this started

• Topic tags are now included
• Once bbPress core converter is updated we can filter the users imported
• Added Topic Closed Status
• Inline docs consistent with other importers
• Whitespace and code formatting improved
• Uses parser.php to convert HTML & Smilies
• Reply status not needed, defaults are built into converter.php
• Reply Order removed, this is calculated during the import

The to do list:

• Remove the `callback_savepass` & `authenticate_pass` as you rightly point out they are not needed and Vanilla uses the same hash as WordPress for passwords so this is too easy.

If you see any bugs with the converter `Vanilla.php` please post these to the trac ticket here.

If there is anything else that needs doing before or after the import that I have not already listed in the codex docs if you could add/update these that would be great.

https://codex.bbpress.org/import-forums/vanilla
(Use the same bbpress.org username and password to login)

[mintertweed]

Okay, so I physically replaced bbpress.css located in bbpress/templates/default/css/ with the newly named style-forums.css and the styles are working fine. But I immediately replaced it with the original bbpress.css because my forums are still not appearing properly. So…first problem solved! Yay. Now, how do I make my forums appear once again? Thank you for your help thus far!

[PavelS]

@netweb When you you think images uploading problem will be fixed? I mean that default users can’t upload images now using TyniMCE editor.

[jeffacubed]

@wdfee Wow – I am SOO glad I stumbled across this y’day – as I was having the EXACT same issue related to the inability to post/create new (forum) topics within buddypress groups after I migrated all the group forums to bbpress 2.2.3.

My config is WP 3.5 multisite, bbPress 2.2.3, BuddyPress 1.6.3, using bp-default theme &/or Genesis Agency w/ Genesis Connect.

It was driving me bonkers trying to comprehend what could be wrong. Regardless, I de-activated bbpress on the root site (site 1), & re-activated bbpress ‘sitewide’ and now I can post new topics w/ buddypress group forums. Like you, I could always create new topics for group forums via the back-end & from the front-end via the sitewide forums, but the front-end was a no-go (w/in the actual group-forum) until I activated bbpress sitewide. As a test, I created a multisite ‘from scratch’ installation (WP 3.5 multisite, bbPress 2.2.3, BuddyPress 1.6.3, using bp-default theme) & activated both buddypress & bbpress from site 1 (root) and everything works 100% as expected from the start. I still don’t 100% understand the nature of this sol’n, but I’ll take it for now!

Anyways, THANKS for posting this, as this forum thread was the tipping point to get a major [buddypress x bbpress] open-innovation project launched ‘only x1 month late’ √

[captjones]

There does not seem to be a step by step manual.

`To customize bbPress:
The directory “wp-content/plugins/bbpress/templates/default/” contains the directories “bbpress”, “css”, “extras”, and “js”, and the file “bbpress-functions.php”.

“bbpress” contains template files; copy any you want to modify into a directory named “bbpress” in your theme’s root. eg. /wp-content/mytheme/bbpress/
“extras” contains optional page templates and things to make life a little easier when customizing; copy any you want to use or modify into the same ‘bbpress’ folder. eg. /wp-content/mytheme/bbpress/
“css” contains style sheets; copy any you want to modify into a directory named “css” in your theme’s root. eg. /wp-content/mytheme/css/
Edit the new files for complete control over bbPress display in your theme.`

^ I did all this and the forum stopped working at all. No other option?
Thanks.

[Erlend]

I prefer the way WPORG deals with per-project forums over the BuddyPress-bbPress way. As in, when I click on a thread from within a group forum, I want that link to be a default forum link, not a custom group forum link. I realize this can potentially cause some confusion for users when they’re taken away from the group. Thing is that I’m running a forum-centric community, not a group-centric one, so for us it’s problematic the other way around:

User discovers new thread via forum index, clicks thread, suddenly the user is in a group! And that’s what we’d like to avoid.

[faeronsayn]

@netweb thank you for that answer it should help debug. But what I don’t understand is that even if the BBpress template is not loading, why are the thread links in the forum being changed to something pretty awkward. Nothing of that sort is defined in the CPT plugin …

The forum tries to point to this link for each thread

http://example.net/forums/topic/forum-category/forum-sub1/%post-name%/

If the bbpress templates are not loading, why are the links being defaulted to that exactly?

[Stephen Edgar]

These are the settings you should use:
Select Platform: Mingle
Database Server: localhost
Database Port: 3306
Database Name: My database name
Database User: My database user name
Database Password: My database password (which I use to login to phpMyAdmin)
Table Prefix: wp_

The changes above are `localhost` for the database server which is the default and is what is needed for most web hosts, the table prefix `wp_` which matches the screenshot you linked to above.

If this does not work confirm with your webhost the correct settings for your database name, user & password.

[brokentwig]

Of course, this is probably the easiest way to clean out deleted and un-confirmed users, but it would be cool to build it into the converter for others to use. Vanilla has no way of cleaning these by default.

`
DELETE GDN_User
FROM GDN_User
LEFT OUTER JOIN GDN_UserRole ON GDN_User.UserID = GDN_UserRole.UserID
WHERE GDN_UserRole.RoleID = 3 OR GDN_User.Deleted = 1
`

[Stephen Edgar]

1) In the yellow status window of the importer if you right click in Firefox/Chrome ‘inspect element’ you can check the SQL queries that the importer ran, have a look at the SQL query for the user import and check if that is what the SQL query should be.

The from/join logic is in converter.phpL#777 and you can use that as a guide to how to translate your query to the fields you are mapping.

2) I would not worry about this option as once you have finished the import and start to run the ‘repair forums’ tools the last option is “Remap existing users to default forum roles” and that will set all users without a bbPress role to ‘participant’

Feel free to throw any questions you have here as I am trying to fix a join for the Invision.php importer as we speak and its being a pain also 😉

[Erlend]

What about the other way around? I’ve run into a lot of problems with the fancy editor when I’m browsing with my mobile phone. Most elegant of all would be to default to text-editing when a mobile device is detected, but a global text-by-default would be a good start.

[Remi]

You can edit the following to your functions.php (for example)

<code>

function no_edit_lock($retval, $cur_time, $lock_time, $post_date_gmt){

return false;

}

add_filter( ‘bbp_past_edit_lock’, ‘no_edit_lock’, 1, 4);

</code>

This will overwrite the default edit_lock behavior.

[Stephen Edgar]

Nice… An extremely good first shot at mapping the MySQL database tables…

I have updated the file with a few things and it should now work…

If your WordPress database uses the out of the box `wp_` table prefix then for the Mingle.php converter we will use `wp_forum_` as the table prefix on the import setting.

• The forum slug is the same process as you did for topics & replies
• A couple of `id` vs `parent_id`
• Dates, WordPress stores four dates for a post in the `wp_posts` table, ‘post_date’, ‘post_date_gmt’, ‘post_modified’ and ‘post_modified_gmt’.
  • Forums – In this case forum creation dates do not exist, this will default to the current date
  • Topics – We map ‘date’ to ‘post_date’ & ‘post_date_gmt’ and ‘last_post’ to ‘post_modified’ & ‘post_modified_gmt’
  • Replies – We map ‘date’ to all four ‘post_date’, ‘post_date_gmt’, ‘post_modified’ & ‘post_modified_gmt’.

So as I said, nice first go at it 🙂

You can view the changes inline I made here and download the full file from here.