[vizcano]

Yes @netweb that is the correct post.
i just made it sticky again.

the thing is that normal and super sticky work fine.

i dont understand anything about the codes thats why i cant find the problem by myself 🙁

Thanks.

[Stephen Edgar]

Not so much what I need, it is what you need to help work out what the issue is 😉

At a quick glance it looks like the bootstrap.css is overwriting the bbPress CSS styles.

Can you make the topic a “sticky” again please:

This is the forum correct? EDIT: Removed URL

[Robin W]

@netweb Thanks for the update

Having followed the links, then code is here

https://meta.trac.wordpress.org/browser/sites/trunk/buddypress.org/public_html/wp-content/themes

[deepthyxavier]

Thank you for your response.
Solved the problem by changing the code in plugins/bbpress/includes/common/widgets.php
made a small change around the line no: 586

[Stephen Edgar]

The theme used here on bbpress.org is called bbpress-org, the theme used on buddypress.org is called buddypress-org, I see a pattern emerging, the theme used on codex.bbpress.org is called codex-bbpress-org, the theme used on codex.buddypress.org is called codex-buddypress-org, there is a pattern here :shakes fist: ;P

Along with the above, each of those themes is a WordPress child theme, the parent theme is named bb-base, as you can see below per the announcement blog posts all the above parent and child themes and plugins used on all the sites were “open sourced” back in March 2014

Open Sourcing bbPress.org

Open Sourcing BuddyPress.org

The above posts also link to the source repos, there is also a new child theme that is now used on the bbPress 2.x powered https://wordpress.org/support/ forums and an even newer evolution of this theme is being worked on for the updated redesign of the WordPress forums, you can even sneak a peak at the new design by visiting this URL: https://wordpress.org/support/?new-theme=1

The updates to all of the above and the migration of the WordPress Support Forums to bbPress 2.x, rather 2.6-alpha is one of the reasons bbPress 2.6 isn’t out yet, it’s because we’re making sure bbPress 2.6 will be the best it possibly can be, and by deploying it on wordpress.org and the ensued battle testing of it that has been taking place we’ve got a few things to do before we can say bbPress 2.6 is ready to be released.

[Stephen Edgar]

@mikehaceman, thanks for testing this, I’ll update the and test the patch in a few hours

And FWIW an import should also work albeit slower without the wp_bbp_converter_translator table, some hosts don’t allow users to create new tables, so I’ll see if I can figure out why this isn’t working either for you 🙂

[mikehaceman]

Ok it was hanging for too long so here what i found out:

on the patch page (https://bbpress.trac.wordpress.org/attachment/ticket/3026/3026.patch) you made few mistakes:

1. Line 663 KEY meta_join (meta_key, meta_value) ) {$charset_collate};”;
should finish with ” , ” not ” ;”; ” otherwise it will crash error

2. Line 660 PRIMARY KEY (meta_id),
is duplicated so i guess 660 or 661 can be removed

3. when running import after those changes in wordpress, converter is giving error message:

WordPress database error: [Key column ‘meta_id’ doesn’t exist in table]
CREATE TABLE wp_bbp_converter_translator ( value_id bigint(20) unsigned not null default ‘0’, meta_key varchar(255) null, meta_value varchar(255) null, PRIMARY KEY (meta_id), KEY value_id (value_id), KEY meta_join (meta_key, meta_value) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

Btw… im not a coder. No clue about php im just applying some logic to what i see 😉

[mikehaceman]

Hi @johnjamesjacoby

Thanks for the update. I have downloaded again the alpha and installed it fresh on my website. Unfortunately still the same error message:

Repair any missing information: Continue
WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE wp_bbp_converter_translator ( meta_id mediumint(8) unsigned not null auto_increment, value_type varchar(25) null, value_id bigint(20) unsigned not null default ‘0’, meta_key varchar(255) null, meta_value varchar(255) null, PRIMARY KEY (meta_id), KEY value_id (value_id), KEY meta_join (meta_key, meta_value) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci
No data to cleanStarting Conversion

[John James Jacoby]

Hey @mikehaceman, sorry you are having trouble.

This isn’t usually necessary, but something between your two installations isn’t cooperating, and in these rare cases it unfortunately requires a bit of scrutiny.

WordPress installations since 4.4 and beyond will try to use utf8mb4 for their character set, and utf8mb4_unicode_ci for their collation. Traditionally these are InnoDB tables, but you’re usually free to decide this for yourself.

utf8mb4 tables have reduced maximum key lengths due to the additional bytes required for each character, so the safe maximum length is reduced to 191. It’s possible we haven’t updated our special converter table to handle this, so I’ll check, and update it if that’s the case.

If you wanted, it may be worth going through all databases, all tables, and all columns, and ensure that your encoding & collations are what you expect them to be. (This means in your old forums, and your new ones.)

[Edit: Updated this post to reflect what we’ve updated in bbPress’s converter]

[mikehaceman]

Thank you for the reply. I have downloaded and installed alpha.
When running import im getting error:

Repair any missing information: Continue
WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE wp_bbp_converter_translator ( meta_id mediumint(8) unsigned not null auto_increment, value_type varchar(25) null, value_id bigint(20) unsigned not null default ‘0’, meta_key varchar(255) null, meta_value varchar(255) null, PRIMARY KEY (meta_id), KEY value_id (value_id), KEY meta_join (meta_key, meta_value) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

I tried to find this error and potential solution. I found someone recommending bbpress toolkit. I have installed it and system info is as follow:

WP version 4.6.1
Theme Twenty Sixteen 1.3
PHP version 5.4.19
bbPress version 2.6-alpha-6091
Active Plugins Name and Version
– p1 bbP Toolkit 1.0.6
– p2 bbPress 2.6-alpha

Any idea ?

[rajwantsingh27]

Turns out that the shortcode has dodgy apostrophes. Once I edited those the shortcode worked:

[bbp-single-view id='popular']

That was a good find. And yes it works now.

Thanks

[Chad R. Schulz]

Yeah, the role of moderator would allow this user to edit topics/replies. Check out the prebuilt roles/caps here.

Also, by giving them the role of author they’d gain access to the back-end of your site for other content (create posts, etc.), as well.

These are two separate roles that do two different things.

[xmatter]

After I renamed the standard “forums root” under Settings > Forums to “forums-old” and added the shortcode to the Forums page, I was able to accomplish a non-sidebar style page.

[xmatter]

Today I changed theme to GeneratePress. Under the “Forums” Page, I changed Content No Sidebar & Full Width Content. Still the Forums page will NOT remove the sidebar. When originally installing bbPress, I created a Forums page with the slug “forums” and that is how its communicating. From there as a diagnostic step, I created another page named Forums2 and added the shortcode to display the forums index. That page would NOT displat it full width (no sidebar) no matter what I tried. Any help would be awesome.

[Chad R. Schulz]

To avoid this problem you can simply replace <?php if ( bbp_allow_topic_tags() ) : ?> with <?php if ( bbp_allow_topic_tags() && current_user_can( 'moderate' ) ) : ?> in your child-theme’s form-reply.php file.

This would prevent any non-moderator from gaining access to the topic-tags designation of the parent topic while adding/editing replies.

Still feels kinda hacky. But, whatever works.

[u_Oi]

Try this code. Put it on the function.php

/* Hide SideBar in bbPress Profiles and Topics*/
function disable_all_widgets( $sidebars_widgets ) {       
    if ( function_exists('is_bbpress') ) {
        if (is_bbpress()) {
            $sidebars_widgets = array(false);
            remove_all_actions('bp_register_widgets');
            unregister_sidebar( 'bp_core_widgets' );
        }
    }
    return $sidebars_widgets;
}

add_filter('sidebars_widgets', 'disable_all_widgets', 1, 1);

You don’t say if You want the full-width to all pages or only to topics, forums, or profiles.

Regards,

[Robin W]

It could be done with css or by altering template or code.

In any case it would require some custom coding in quite a lot of places.

Beyond any free help I can offer – sorry !

[Robin W]

this code will change it

li.bbp-forum-freshness, li.bbp-topic-freshness {
   text-align: left;
 }

[fullenchilada]

Thx Robin. Just added some lines of code to the theme’s css file. Working perfectly now.

[Robin W]

Line 471 of your theme’s style.ccs has

http://www.revelation-online.de/wp-content/themes/mh-magazine/style.css

img {
  height: auto;
  max-width: 100%;
  vertical-align: bottom;
}

Thevertical-align: bottom; is causing the issue

[senatorman]

one best way.ive done with my forum. All other ways are not working

-Update phpbb to the latest version
-use the BBpress Alpha 2.6
-import the data from phpbb
-do the fixes down under in separatly ( run sql in 5 steps, begin with the first)

/* Get all posts with wrong author and correspondent right author from translator table */

create table TMP_ORPHANS as
select
wp_posts.ID,
wp_posts.post_author,
wp_bbp_converter_translator.value_id real_author,
IFNULL(wp_posts.post_date, NULL) post_date,
IFNULL(wp_posts.post_date_gmt, NULL) post_date_gmt,
wp_posts.post_content,
CASE
WHEN wp_posts.post_type = 'reply'
THEN (SELECT tmposts.post_title from wp_posts as tmposts where tmposts.id = wp_posts.post_parent)
ELSE wp_posts.post_title
END post_title,
wp_posts.post_excerpt,
wp_posts.post_status,
wp_posts.comment_status,
wp_posts.ping_status,
wp_posts.post_password,
wp_posts.post_name,
wp_posts.to_ping,
wp_posts.pinged,
IFNULL(wp_posts.post_modified, NULL) post_modified,
IFNULL(wp_posts.post_modified_gmt, NULL) post_modified_gmt,
wp_posts.post_content_filtered,
wp_posts.post_parent,
wp_posts.guid,
wp_posts.menu_order,
wp_posts.post_type,
wp_posts.post_mime_type,
wp_posts.comment_count,
(	select wp_postmeta.meta_value
from wp_postmeta
where
wp_postmeta.meta_key = '_bbp_author_ip' and
wp_postmeta.post_id = wp_posts.id
) user_ip
from wp_posts
left join wp_users on wp_posts.post_author = wp_users.id
left join wp_bbp_converter_translator on wp_posts.post_author = wp_bbp_converter_translator.meta_value
where
wp_posts.post_type in ('forum', 'reply', 'topic') and
(wp_users.id is null or
wp_users.id = 1) and
wp_bbp_converter_translator.value_type = 'user' and
wp_bbp_converter_translator.meta_key = '_bbp_old_user_id';

/* Do this to be able to create indexes later – some may not work */
ALTER TABLE TMP_ORPHANS modify column post_date datetime default NULL;
ALTER TABLE TMP_ORPHANS modify column post_date_gmt datetime default NULL;
ALTER TABLE TMP_ORPHANS modify column post_modified datetime default NULL;
ALTER TABLE TMP_ORPHANS modify column post_modified_gmt datetime default NULL;
ALTER TABLE TMP_ORPHANS modify column user_ip varchar(40);
ALTER TABLE TMP_ORPHANS modify column post_title varchar(255);

/* we create indexes to speed up the update process */
ALTER TABLE TMP_ORPHANS ADD INDEX(post_date);
ALTER TABLE TMP_ORPHANS ADD INDEX(post_author);
ALTER TABLE TMP_ORPHANS ADD INDEX(real_author);
ALTER TABLE TMP_ORPHANS ADD INDEX(user_ip);
ALTER TABLE TMP_ORPHANS ADD INDEX(post_title);

/* Revert bad authors to good authors */
UPDATE
wp_posts INNER JOIN TMP_ORPHANS
ON wp_posts.id = TMP_ORPHANS.id
set wp_posts.post_author = TMP_ORPHANS.real_author
where wp_posts.post_type in ('reply', 'topic') ;

/* Drop TMP table */
DROP TABLE TMP_ORPHANS;

The result is a compleet database with the good relation between post and author

[Stephen Edgar]

Also, I just learnt that if your themes header.php contains lang="en" that will cause issues, see https://bbpress.org/forums/topic/unable-to-change-language/#post-179361

[ngp130895]

I found out that because in the header.php in my theme, the <html> tag has an attribute of lang="en" that overrode WordPress language options. I removed this and it works. Thanks for your reply anyway!

[Stephen Edgar]

When you downloaded those files what options did you select?

You need to select All current to get the “current strings”

p.s. I’ve also just made a request to have bbPress “stable” language packs generated, once this is complete you should be able to download the translations directly from the WordPress updates dashboard, just as you get the translations for WordPress itself.

Keep an eye out for Finnish to show up in the API here

[ngp130895]

Hi,
I am using bbPress to create a forum for a customer. I use WordPress 4.6.1 and bbPress 2.5.11.
I downloaded the .mo and .po files in my language (Finnish) from this link, changed the file names into:
bbpress-fi_FI.mo and bbpress-fi_FI.po, and moved them to wp-content/languages/bbpress
Eventhough my wordpress site language is Finnish and I have those mo and po file in the folder, the bbpress forum is still in English.