[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.

[Roy]

I’ve got a nasy little bug(ger). I’ve got a 3.5 WP installation with a forum using the BBpress plugin. Everything was running perfectly until I noticed that in my WP menus I could no longer drag and drop. I deactivated all plugins (which helped), reactivated them. So far so good. Then I noticed that my forums went funky.

The forum index works. I’ve got four forums, two public, two private. One of the forums works (one of the public ones), the other three give 404’s. The strange thing is that a newly created forum also gives a 404, but al subjects (or threads) work, also the threads in the malfunctioning forums.

So I thought: permalinks. Changed to default and back, no go. Edited the permalink of the forums manually to something ‘test’ (edit specific forum), no go. Edit the permalink for forums in the BBpress settings, no go.
Of course I also tried deactivating plugins again, use default theme, searched around a bit on the www and noticed people with htaccess problems. I’m sure it’s something there, but I can’t figure it out, especially not because one forum works and the rest does not.
Website monas.nl, see tab forums.

Thanks in advance for your suggestions.

[carmelneta]

Here is the solution:

All forums pages on non-default WordPress template.php

[jezza101]

I looked into this in the past and having read a number of existing threads on the topic it looks like there is no way to change this.

For aesthetic reasons I chose to change from the default as “/forum/forums/” doesn’t look great so you can change it to “/bb/forums” or “/forum/discuss/” or whatever. Not ideal but trying to hack this to work could leave you in a whole world of pain (prob tricky to get right, and may break with future releases).

[joe.davola]

Hi,

How do I change the editor style from “Visual” to “Text”. My theme is messing up the text area so that it is hardly visible to users. Using the “Text” version is a lot better.

Which file do I need to edit to change this default?

[shrewdies]

OK, here are the redirects, but first some background.

Your move takes some planning, and the redirects are specific to your old Simple:Press Forum structure and your new bbPress settings (Admin-Settings-Forums). I describe how I approached my conversion, but you may need a different approach. If you need specific help with a different set of objectives, then please just ask. I did not use tagging in Simple:Press, as it was more trouble to implement than the benefit it gave. None of this refers to tagging, and I notice that the r4638 version of SimplePress5.php has them commented out.

If your forum has little search and external referral traffic, then save yourself the bother of all this, and just get on with building your new forum.

Before I explain the permalinks, you need to be aware that I took this opportunity of simplifying my forum structure. I used to believe in different forums for different subject areas, but I’ve come to realize that most forum users do not understand my theme, so they cannot decide which forum to post in. I noticed the same thing here when I looked around for the best place to post. I decided to simplify my forums to two main choices, with the rest as child forums. I did this by manually editing the Forums parents in bbPress after the conversion. That explains my choice of Topic slug in bbPress settings, but redirects should handle any choice.

In Simple:Press, topics get permalinks in a hierarchy under their forum, and all forums lie within the WordPress forums page in the Simple:Press settings. Thus, a topic will be referenced domain/wp-forums-page/sp-forum-title-slug/sp-post-title
In bbPress, permalinks are built from your WordPress root, with prefixes set in the bbPress settings under slugs. Thus a topic will be referenced domain/bb-forums-base/bb-topic-slug/bb-post-title

The post titles are the same in bbPress and Simple:Press, so redirects have to account for the changed forum slug structure.

The first bbPress setting, Forums base, is the equivalent of your Simple:Press WP page, so I used exactly that. If you made bad choices when setting up your Simple:Press forum, I guess you could change it with the redirects, by specifying different destination URLs. I kept it the same, and simply renamed my old Simple:Press page (be aware this auto changes in WP menus, so you may need to manually delete old forum menu pages and add new custom menu links)

In bbPress settings Single Slugs, the Forum Prefix should be left switched on.

Forum slug has no Simple:Press equivalent, so I opted for something theme related. The default is probably OK, but I’m slug-fixated as a result of a bad SEO upbringing. I have not redirected these pages, but I will assess the impact over the next few days, and come back with these if I see they are necessary.

I set topic slug to my most popular forum, which is very general, as per my introduction. Redirects will handle whatever you put here.

The rest of the bbPress settings do not affect conversion.

At last, @netweb here are the requested redirects. Are you glad you didn’t ask for my life story? 😉

The general construct is:
Old
^ begin with
/wp-forums-page
/sp-forum-title-slug
(.*) store the rest

New
//domain
/bb-forums-base
/bb-topic-slug
/$1 whatever * stored

RedirectMatch 301 ^/gout-pal-forum/gout-symptoms(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/gout-cures(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/gout-diet(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/colchicine-campaign(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/united-states-colchicine-sources(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/gout-related(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/uric-acid(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/your-gout(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/tech-stuff(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/wish-list(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1
RedirectMatch 301 ^/gout-pal-forum/gouties-water-trough(.*) http://www.gout-pal.com/gout-pal-forum/please-help-my-gout/$1

One potential complication lies with multi-page topics. I’m still assessing if it is worth bothering with these, as traffic rarely hits anything after the first page. Google WebMaster Tools is currently complaining, but experience tells me it will soon re-index unless there are other sites that link to specific pages.

Disclaimer: Before you try this at home, you might like to wait a month or so. I’ll be back to tell you if I killed my forum traffic or not. 😮

[Stephen Edgar]

So close… Indeed you use bbp_has_replies to reverse order the replies

function custom_bbp_has_replies() {
  $args['order'] = 'DESC'; // 'ASC' (Ascending, Default), 'DESC' (Descending)
  
  return $args;
}
 
add_filter('bbp_before_has_replies_parse_args', 'custom_bbp_has_replies' );

And use bbp_show_lead_topic to always show the ‘lead topic’ (More details here.

function custom_bbp_show_lead_topic( $show_lead ) {
  $show_lead[] = 'true';
  return $show_lead;
}
 
add_filter('bbp_show_lead_topic', 'custom_bbp_show_lead_topic' );

[satochan]

I set the permalink rule for Forum as below.
http://xxxxxxx.jp/forum/%post_id%/

However,when log in as Subscriber/Contributor, the permalink rule isn’t reflected
but default setting(/%postname%/) is reflected…

On the other hand, when log in as Admin, the permalink rule is reflected normally.

Could you tell me why this happens?

[Stephen Edgar]

There is this comment via @JJJ

Try bumping the converter start (_bbp_converter_start) up 1 or 2, and see if it continues on.

I am trying to wrap my head around this and this may or may not help 😉

Once the import stops at that magic ~31000 number open up your WordPress `wp_options` table in phpMyAdmin and find the following three entries (or values similar):

• `_bbp_converter_step | 6`
• `_bbp_converter_start | 31100`
• `_bbp_converter_query | SELECT convert(topics.topic_id USING “utf8…`

These translate to ‘step’ is the step the conversion was up to (Importing forums, forum hierarchy, topics etc), ‘start’ is the last set of rows the converter was importing when it stopped from the current ‘step’ and ‘query’ was the last SQL query executed.

I think from some calculated guesswork yours will be around step=6 & start=31000

What you can now try is to change this ‘start’ value directly in the `wp_options` table and increase the value to hopefully allow the importer to skip the problem and finish importing the remaining topics and onto importing the replies.

The default setting for the importer is to import 100 rows at a time as defined by ‘Rows Limit’ on the import options main import tool. Thus the importer could be failing on any of those 100 rows so if it was row 31000 that it stops on changing this to 31001 would continue on and finish the import. The reality is though that it could be any number from 31000 to 31099.

I would suggest on the forum import settings change ‘Rows Limit’ to ‘1’ and in `wp_options` change `_bbp_converter_start` to 31001 and click start. This will resume the last import starting at the same ‘step’ it left off with and starting at row 31001 and then proceed 1 row at a time.

If the import stops again you can look up the values in `wp_options` and increase by 1 again and resume the import again.

Now with that said the import will continue to only import 1 row at a time for the remainder of the import process which with 30,000+ topics I expect you will have quite a few tens or hundreds of thousands of replies to also import and this will be much slower than importing 100 rows at a time.

[beervanger]

Hi everyone,
I need your help. I wanna migrate from phpbb to bbpress.
I use bbConverter. I got this error :

[…again and again…]

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

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 ” at line 1]
SELECT * FROM wp_posts WHERE id =

Convert forums (0 – 99)-
Not clearing default passwords-

Not Converting users Selected-

Not Cleaning Data-

Conversion Complete-

Starting Conversion…

Could you help me?
Thank you.

[revkev]

Unable to post in new forums (all forums are new on this site). Can see ‘everything, except for a ‘submit’ button after entering the topic.

Have verified this occurs with TwentyTwelve, BP Default and BP Columns ver. 1.5.3

I am using WP 3.5 and Buddypress 2.2.3

Have reinstalled forums
Have Deactivated and Activated the plugin.
Have reset permalinks (as suggested in another forum)
Have made a new post to WP and confirmed I am able to post comments to it.

At a loss, any suggestions and solutions greatly appreciated!

http://www.lcag.info/

The forums are listed in a widget on the left side of the page (don’t have them working on the discussion page (yet), that is another post???

Your time and energy is greatly appreciated.

RevKev

[Stephen Edgar]

It appears that bbPress Sweedish translations are a bit all over the place:

bbPress Dev – 87% Complete https://translate.wordpress.org/projects/bbpress/dev/sv/default
bbPress 2.2x – 0% Complete https://translate.wordpress.org/projects/bbpress/2.2.x/sv/default

Also WP Sweeden had previously operated there own translations here
bbPress 2.1 http://wpsv.se/oversattning/projects/bbpress/21
bbPress 2.0 http://wpsv.se/oversattning/projects/bbpress/20

I think the best idea would be to contact WP Sweeden and ask about bbPress translations

http://wpsv.se/kontakta-oss/

[Geezerjim]

Are you using Jetpack-Sharing? If so, just go to the configuration page and check the boxes for forums, topics, replies, or whatever you want. They are not checked by default, and will not be checked if you added bbPress after you activated Jetpack.

[distjoyo1]

actually no, i’m runnin the v1.3 of the theme, and please what are the steps to update any theme cos i noticed that the update link only shows for wordpress default themes, thanks so much for your time

[Ben]

Have you found a solution to this problem?

I’m having the same issue. I used the [bbp-topic-form] shortcode in my `bbpress.php` template file. If I enter with my super-admin account I can see the form and create topics. But if I enter under the default “Participant” role, it gives me the message “You cannot create new topics.” However, if I go to a specific forum, the topic form is displayed underneath, so it must be a shortcode problem.

Right now I’m using `echo do_shortcode(“[bbp-topic-form]“);` to include the form in my template file. Is there a better way to do this?

[Ben Hansen]

Not sure if this is related to anything else i’ve seen here but pretty sure this is about the new dynamic roles. Prior to the new forum roles i had created custom roles to combine capabilities of forum and wp default roles (such as Moderator + Editor) using user role editor. Things were all out of whack and i noticed this week that everyone was able to see our private forums, so i decided to try to clean things up by deleting all of my custom roles and start over. Unfortunately it seems that the new powers have stuck and i can no longer edit the capabilities of the participant role (has everything but keep gate and manage capabilities) the other roles seem to be editable (although they all default to this level of power as well) Anyone know what to do here?

Thanks advanced!

[Mantzer]

Hey
I have an author page that is different to the default bbpress user page.
However I’d like to show the last forum topic a user started as well as their latest reply on that particular page. Is there a way to do this?
Thanks a lot.

[Hansaplastique]

I was looking for a way to make sure forum posts are always edited in the WYSIWYG mode of the fancy editor, and found an easy solution to hide raw text (both tabs actually disappear with this) – in case someone is looking for this as well;

In the template files (only copy the files you need from wp-content/plugins/bbpress/templates/default/bbpress to your theme folder, into a folder called bbpress, for example wp-content/themes/mytheme/bbpress) you’ll find numerous calls to:

bbp_the_content( array( ‘context’ => ‘reply’ ) );

In your template files replace a call like this with (ie. add: ‘quicktags’ => false);

bbp_the_content( array( ‘context’ => ‘reply’, ‘quicktags’ => false ) );

The calls can be found in all form-xyz.php files.

[Lynq]

The only thing I can think of is that there is some template files that are overriding the default bbPress theme and they are erroring because of some custom function or have no actual code in them.

Have you had a look in your theme folder to see if there is a bbpress folder, is there any files inside that folder?

[Lynq]

Have you tried switching to a default theme to see if the theme is causing this issue? It looks it is going to be a plugin or theme issue.

When I have any issues I try and replicate my forum on a local test, then I disable plugins one by one to see if that fixes it, then I try switching to a default theme. Usually that gets me a lot closer to finding out what is causing the issue.

Good luck!

[baldwin]

Dear all,

I have post this at plugin site, however, i want to post it here too since this was an issues and i want to increase the popular of this post so that the master or “sifu” can see and help… thanks
I am fresh to wordpress. I have install bbPress into my wordpress, and i face some serious issues.
By default, after I comment on a topic, it should be refresh the page and show me my comment with “Awaiting Moderation”. However, it’s some time do not refresh and stay in same page, it will link me to the main topic pages.
After I set the topic and reply under “Per Page” section to 1000 per page, this issue do not occur anymore. But problem is reader do not like so many topic or comment in 1 page. It’s seems that bbPress by default do not have a solution in the code to link correctly between the topic pages?
For example, if I set under “Per Page” section, 10 post per reply. When this topic have more than 10 reply, the 11 reply will go to page 2, here the issue will start. anyone post after page 11 will be link to wired page/link or the page will display “Oh bother! No replies were found here!” or “page 404, not found”.
Anyone have a solution on this? Any help is appreciate…
Thanks