[Atsutane]

To center it u need to play with css .. try look into default bbpress style.css and see which code u can use to suit your theme

[Atsutane]

Well u can try this. Donno if it gonna work or not .. right now 12:54am so i dont have the time to test it Try at ur own risk. Got problem dont blame me . Well if this was wrong feel free to fix it.

function get_post_author_avatar() {

global $bbdb;

$id = get_post_author_id();

$user = bb_get_user( $id );

$usermail = $user->user_email;

$default = “http://www.somewhere.com/homestar.jpg”; // Put your default avatar link

$size = 40;

$grav_url = “http://www.gravatar.com/avatar.php?gravatar_id=”.md5($email).”&default=”.urlencode($default).”&size=”.$size;

echo “<img src=”$grav_url” alt=”Gravatar” />”;

}

[ear1grey]

The topic-tags.php template is being explicitly included through the topic_tags() method of template-functions(), so replacing it in my-templates has no effect.

This makes me wonder if, generally, a bb_include and bb_require method could be used for all includes which would check the template system before resorting to a default folder.

this could possibly replace the oft repeated:

if (file_exists( BBPATH . 'my-templates/whatever.php' ))

require( BBPATH . 'my-templates/whatever.php' );

else require( BBPATH . 'bb-templates/whatever.php' );

I thought it worth mentioning because theme developers might find it useful from the outset.

[mokona]

I’m trying to install bbPress but I got this error

“Fatal error: Call to undefined function: load_default_textdomain() in /home/.nevermore/wererabbit/demon.wererabbit.net/bbpress/bb-settings.php on line 132”

What I’m supposed to do?

[meeciteewurkor]

what about the encode_bad function in the same formatting-functions.php file?

It has the same list of default allowed html tags. I don’t know enough php yet to understand what it does, though?

Maybe the img tag needs to be placed here as well?

function encode_bad( $text ) {

$text = wp_specialchars($text);

$text = preg_replace('|<(/?strong)>|', '<$1>', $text);

$text = preg_replace('|<(/?em)>|', '<$1>', $text);

$text = preg_replace('|<(/?a.*?)>|', '<$1>', $text);

$text = preg_replace('|<(/?ol)>|', '<$1>', $text);

$text = preg_replace('|<(/?p)>|', '<$1>', $text);

$text = preg_replace('|
|', '
', $text);

$text = preg_replace('|<(/?ul)>|', '<$1>', $text);

$text = preg_replace('|<(/?li)>|', '<$1>', $text);

$text = preg_replace('|<(/?blockquote.*?)>|', '<$1>', $text);

$text = preg_replace('|<(/?code)>|', '<$1>', $text);

$text = preg_replace(“|(.*?)|se”, “‘' . encodeit('$1') . '‘”, $text);

return $text;

[meeciteewurkor]

thanks nolageek. I’ve actually had that part correct. After messing around, now only one topic is like that. The other is fine.

In fact the default topic that was made called “Your first topic” portrays the correct “freshness”. All new topics give the -1 year weirdness. I’ll keep tinkering.

http://meeciteewurkor.com/bbpress/

[Michael Adams (mdawaffe)]

If bb_ really is your bbPress table prefix, and that is what is entered int the integration plugin page, users registering through bbPress should be given WordPress’ default role upon logging into WP for the first time.

So I’m not sure what’s wrong exactly, but it may be caused by the stuff you’re doing manually (as you expect).

[hasund]

I am setting up a web site that has two main groups of users: The (WP) blog editors, and the readers, who are supposed to be able to make contributions through comments or in the forums. The registered WP users can use the bbPress forum seamlessly, however, there’s a bit of a problem on the other end, with the users who first register themselves in bbPress. It seems that when someone registers as a bbPress user, they are also automatically a WP user. This would be fine and dandy, if only their user level was set low enough to keep them out of the WP backend. But it doesn’t work like that. I’ve set the default user role for new users to “Subscriber”, but something in the communication between bbP and WP goes wrong, and they are granted some mutation of the administrator role instead: They aren’t able to publish, or edit posts from users with a higher level, but they can edit each others drafts, and they can change both their own and others user levels and passwords. Or edit the templates.

So what I want is a way for registered WP-users to flow freely into bbPress, but not vice versa. I don’t want the forums users in the WP dashboard area at all. I’ve tried the bbpress-integration.php-plugin, but it doesn’t seem to make any difference, its only option is to set the bbPress prefix to bb_ (the bbP-tables already has this).

[devils_advocate]

ok – I found the ultimate guide and it got me 95% through…

I’m still having a problem (that is likely in my WordPress set up) and a problem seeing the (default stylesheet)….

ideas?

[matiasquaglia]

Hi, i’m just steppin’ in in Bbpress, and i’m very impressed.

I’ve used WP in the past, and I like it a lot.

BBPress has same carisma.

I’m just wondering about changing the default language.

In Wp that’s done throug a compiled file, and with BBP?

[gnawph]

Some of these additions are either done with a simple plugin or template modifications…

Personally I’d like to see bbPress continue on with it’s development without spending resources to integrate the two programs together. Rather bbPress should stand alone as a forum system and not just a glorified WordPress plugin. It is my opinion that current forum systems offer way too many features and confuse themselves with content managment systems and social networking sites. Huge avatars and signatures take away from actual content and private message systems have been around for ages disguised as email.

The community around bbPress should develope plugins for all of these specific features. Remember that 90% of your users will just read and post on your forum and all those other goodies are just taking up resources that aren’t contributing to the overall “digital discussion” philosophy of a forum. Usenet is still pretty popular and that hasn’t changed much in years.

I’d like to see improvements on security, speed, and ease of use in the next releases rather than glittering goodies and features.

I am working on another ghetto plugin to highlight threads that have been started since your last visit. It’s been painful and frustrating to work on this since it’s been so long since I’ve worked with php but man is it fun. Another thing I’d like to see in the next release is a list or plan of what is going to happen next so I don’t waste time creating a plugin that is going to be in the next release.

Although it is fun.

P.S.

I’m biased on this issue as I’ve been in web stuffs for a number of years now so I can easily integrate a theme. It should be very simple as most of your design should be located inside your wp css file. The only thing you really have to change is some <div> placement. I threw away the default bbpress css theme and just flung bbPress into my WordPress site’s containers and it worked pretty well.

[abidsultan]

hi,

can anyone help me out for the following…why it dosent move after 2nd step…

“Second Step

Now we’re going to create the database tables and fill them with some default data.”

[Michael Adams (mdawaffe)]

Copy bb-templates/topic.php to my-templates/

Find and remove

<li id="resolution-flipper"><?php _e('This topic is') ?> <?php topic_resolved(); ?></li>

This will likely be removed by default in future versions of bbPress.

[kingb]

You have to edit ‘template-functions.php’ which is located in the bb-includes folder. The function is at line 890, called tag_heat_map. You will see that it takes 4 variables as parameters the first one is the smallest size possible for the tags, the second one is the largest size possible for the tags, the third is wether it the font size is measured in points(pt), pixels(px), or ems(em). The default is pt. The last parameter is the maximum numbers of tags that are displayed.

Hope this helps!

[ear1grey]

/me thinks aloud

Just the one set. A basic plugin-management-plugin should be auto-activated when no other plugin-management-plugin is available.

This would need an extra entry in the plugin remarks such as “Plugin-Type: Plugin Manger” so that at least one such plugin is always enabled.

That way the default behaviour could be replaced (as requested earlier), keeping UI clutter down.

Perhaps “Plugin-Type” should read “Plugin-Tags” and thus categories could be achieved.

[mozey]

i am under the impression that there is a default theme with bbpress, mine is not loading, everything else is working. (Well, its installed and ic an add forums etc), but it looks like its not finding a .css file of anysort. any ideas?

[bryanveloso]

Also when bbPress has a true template system, I’ll be making the default skin sort of like Andy’s Sandbox theme, so you won’t have to try to get around my CSS if you don’t want to.

[gnawph]

Oops, removed my site specific urls.

Well, the point of the entire plugin is to integrated with WordPress. I wouldn’t want to have my smiley images stored in two different locations and I’m not entirely sure were to edit my default WP smiley locations.

[gnawph]

I wanted that functionality as well so I ripped some WP code, played around, and finally got something I could use. This is a highly sloppy work as I am out of practice and not really a great PHP programmer anyway. The plugin is mostly a rip of the WordPress code with a filter. It is not elegant or tested completely but so far it has been getting the job done.

Note: This plugin will not work without a default install of WordPress.

You have to create a directory called /my-plugins/, copy this code into a file called whatever-you-want.php, upload and enjoy!

Feedback appreciated! Maybe I can improve on this and increase my PHP/*press skills.

<?php

/*

Plugin Name: WordPress Smiley Integrator .0002

Plugin URI: none

Description: Gives WordPress Smiley Functionality to bbPress

Author: John Farrell

Version: 1.0

Author URI: none

*/

function convert_smilies($text) {

$wpsmiliestrans = array(

':mrgreen:' => 'icon_mrgreen.gif',

':neutral:' => 'icon_neutral.gif',

':twisted:' => 'icon_twisted.gif',

':arrow:' => 'icon_arrow.gif',

':shock:' => 'icon_eek.gif',

':smile:' => 'icon_smile.gif',

' ??:' => 'icon_confused.gif',

':cool:' => 'icon_cool.gif',

':evil:' => 'icon_evil.gif',

':grin:' => 'icon_biggrin.gif',

':idea:' => 'icon_idea.gif',

':oops:' => 'icon_redface.gif',

':razz:' => 'icon_razz.gif',

':roll:' => 'icon_rolleyes.gif',

':wink:' => 'icon_wink.gif',

':cry:' => 'icon_cry.gif',

':eek:' => 'icon_surprised.gif',

':lol:' => 'icon_lol.gif',

':mad:' => 'icon_mad.gif',

':sad:' => 'icon_sad.gif',

'' => 'icon_cool.gif',

'8-O' => 'icon_eek.gif',

'' => 'icon_sad.gif',

'' => 'icon_smile.gif',

'' => 'icon_confused.gif',

'' => 'icon_biggrin.gif',

'' => 'icon_razz.gif',

':-o' => 'icon_surprised.gif',

':-x' => 'icon_mad.gif',

'' => 'icon_neutral.gif',

'' => 'icon_wink.gif',

'' => 'icon_cool.gif',

'8O' => 'icon_eek.gif',

'' => 'icon_sad.gif',

'' => 'icon_smile.gif',

'' => 'icon_confused.gif',

'' => 'icon_biggrin.gif',

'' => 'icon_razz.gif',

':o' => 'icon_surprised.gif',

':x' => 'icon_mad.gif',

'' => 'icon_neutral.gif',

'' => 'icon_wink.gif',

':!:' => 'icon_exclaim.gif',

':' => 'icon_question.gif',

);

// generates smilies' search & replace arrays

foreach($wpsmiliestrans as $smiley => $img) {

$wp_smiliessearch[] = $smiley;

$smiley_masked = htmlspecialchars( trim($smiley) , ENT_QUOTES);

$wp_smiliesreplace[] = " <img src='/wp-includes/images/smilies/$img' alt='$smiley_masked' class='wp-smiley' /> ";

}

$output = '';

// HTML loop taken from texturize function, could possible be consolidated

$textarr = preg_split("/(<.*>)/U", $text, -1, PREG_SPLIT_DELIM_CAPTURE); // capture the tags as well as in between

$stop = count($textarr);// loop stuff

for ($i = 0; $i < $stop; $i++) {

$content = $textarr[$i];

if ((strlen($content) > 0) && ('<' != $content{0})) { // If it's not a tag

$content = str_replace($wp_smiliessearch, $wp_smiliesreplace, $content);

}

$output .= $content;

}

return $output;

}

//add the filter

add_filter('post_text', 'convert_smilies');

?>

[Elad Salomons]

aka: yes, it works! The only thing I did change it to plave the call:

load_default_textdomain();

just after line 75.

[plasticdreams]

Hi.

A few japanese users and I are trying to localize.

They say:

1. put your-lang.mo into bb-inclues/languages/;
2. add define (‘WPLANG’, ‘your-lang’); in config.php( line 56 is fine);
3. add load_default_textdomain(); in bb-settings.php(line 135 is fine);
4. replace ABSPATH to BBPATH in bb-inclues/i18n.php.

…and these fixes are work well.

You can see here: http://hiromasa.zone.ne.jp/files/wordpress/bbPress01.png

[Elad Salomons]

I think that the following call in bb-settings.php is missing:

// Load the default text localization domain.

load_default_textdomain();

[Matt Mullenweg]

bbPress uses the exact same translation framework, gettext.

Large parts of it have already been translated as part of WordPress.com, but we don’t want to localize the default templates until we have proper themes. (Like in WP.)