Forum post type 'post_type=forum' in admin section can't be opened due to large forum count (30+ forums)

[Sadr]

Our BuddyPress site has 37 group forums with 20k threads and 150k posts that we want to convert into bbPress 2 forums. The import is successful, but I can't access 'wp-admin/edit.php?post_type=forum', nor view any topic or forum in the front-end. I can still access topics & replies in the back-end.

On a side-note, I don't understand why the importer insists on having only one forum in root, while making every other forum a child by default.

The current workaround for this is to create a new forum, make that a child of the one parent forum (haven't tried childing it to another child forum) and the forum section is now available again via the back-end, and the single parent forum with all its children will display in the front-end. Permanently deleting the single parent forum (ideally it has no topics of its own) will un-child all the other forums, putting them in root.

[johnjamesjacoby]

Replying to Sadr:

Our BuddyPress site has 37 group forums with 20k threads and 150k posts that we want to convert into bbPress 2 forums. The import is successful, but I can't access 'wp-admin/edit.php?post_type=forum', nor view any topic or forum in the front-end. I can still access topics & replies in the back-end.

Have you recounted everything?

On a side-note, I don't understand why the importer insists on having only one forum in root, while making every other forum a child by default.

Because this is the way group forums are setup in BuddyPress with bbPress 1.x.

The current workaround for this is to create a new forum, make that a child of the one parent forum (haven't tried childing it to another child forum) and the forum section is now available again via the back-end, and the single parent forum with all its children will display in the front-end. Permanently deleting the single parent forum (ideally it has no topics of its own) will un-child all the other forums, putting them in root.

Might be a quirk of the migration, but I wouldn't suggest putting all of your group forums in the root quite yet. As they'll get commingled in with any site-wide forums you might have.

Moving to 2.2 to investigate further then.

[Sadr]

Yep, I recounted everything.

Regarding the root placement, will it still be a mess if we're using a different slug (e.g. bbforum) for bbPress 2? That being said, I'm pretty sure we're going to retire our legacy forum entirely anyhow.

Let me know if there's any further testing I could do, if you'd be interested in our database/site backup or if you'd like access to our test site.

[netweb]

Let me know the test site URL (here or via email) and I'll have a look.

[Sadr]

The test site url is test.jmonkeyengine.org. We usually run it under maintenance mode but I'll leave that off for now. I don't think you'll be able to find much unless you're admin and the forum has been freshly converted without the workaround being done already, so shoot me an e-mail at e.soghe@… and I can run the conversion and give you admin access.

[johnjamesjacoby]

Once you have the group forums and site-wide forums both using bbPress 2.x, the only thing that currently keeps group forums out of site-wide view is the Group Root forum, which is usually hidden from site-wide view.

I haven't put any thought into a work-around, but one possible one would be a custom post_status, which would leave the forum visibility up to the group. This would probably bork search and things though.

[johnjamesjacoby]

The other way to do this, is to have groups use a custom topic taxonomy. The caveat with that approach is groups lose the ability to have their own stickies, and it basically works like WordPress.org does.

[johnjamesjacoby]

(In [4259]) Dropdowns:

• Revert back to text inputs for topic and forum ID's in metaboxes.
• Fixes memory issues when loading thousands of posts.
• Fixes #1878.
• See #1901.