[johnhiler]

Yury – I totally agree that we as a community need more control over things like docs, etc.! But I can’t see Matt giving FTP and database rights to us… maybe instead, we can download copies of the various releases and plugins and upload them to a backup server somewhere? And start some docs on another server, as you have.

Honestly – I would be shocked if Automattic shut down bbpress.org without warning. It would be a real black mark on Automattic’s reputation in the open source community, which is something Matt and his team are really proud of (and rightfully so). But if that’s something that a bunch of us are worried about, we can maybe create another thread to discuss how to prepare for that contingency.

Gautam – I’m not too worried about this next release, because Matt pretty clearly defined it before he disappeared:

https://bbpress.org/forums/topic/whats-happening-with-bbpress/page/5#post-64400

The next version though, we’ll definitely need to establish a clear direction – with or without Matt (but hopefully with him, or someone from Automattic!). But I’m not too worried about informing anyone… we’re posting on a public server, so it’s not like we’re hiding what we’re up to!

[johnhiler]

“And main question: Who is admin of this site with full access if Matt left project?”

Is that the part you’re referring to? I guess I’m not understanding what contingency we’re preparing for. Matt has already de facto left the project, and Chris has been doing a wonderful job of making steady progress towards the next release.

Is the concern that if bbpress.org is suddenly shut down, we won’t have a backup of the data? Sorry – just trying to get my head around your concern!

[jurasiks]

we’ve got 1 open ticket till 1.0.3 on trac?

sent another message to Matt, spam his Facebook page…

is he ignoring us?

[psycheangels]

fix post position

function fix_post_position() {

global $bbdb;

$get_topics = $bbdb->get_results("SELECT * FROM $bbdb->topics ORDER BY topic_start_time ASC");

foreach( $get_topics as $get_topic ) {

$get_posttopic = $get_topic->topic_id;

$postorder = 1;

$get_posts = $bbdb->get_results("SELECT * FROM $bbdb->posts WHERE topic_id = '$get_posttopic' AND post_position = '1' ORDER BY post_time ASC");

foreach( $get_posts as $get_post ) {

echo "UPDATE bb_posts SET post_position = ";

echo $postorder++;

echo " WHERE topic_id = ";

echo $get_post->topic_id;

echo " AND post_id = ";

echo $get_post->post_id;

echo " ;";

echo '<br/>';

}

} }

echo fix_post_position in your template file and copy the sql query to your database

[robalan]

zaerl,

Apparently I need the second pair of eyes for when I post things here. ;o) I copied/pasted the redacted code, but didn’t add the BB_.

On the actual config file, they are:

define(‘BB_AUTH_KEY’, ‘same as wordpress’);

define(‘BB_SECURE_AUTH_KEY’, ‘same as wordpress’);

define(‘BB_LOGGED_IN_KEY’, ‘same as wordpress’);

define(‘BB_NONCE_KEY’, ‘same as wordpress’);

[Anonymous User]

Hi Rabbitdk,

with manual coding it should be possible to display complete posts in wordpress.

I use the examples from https://bbpress.org/forums/topic/heres-how-to-show-bbpress-info-inside-wordpress-without-full-integration to display an complete list of my forums and a short list of the newest topics.

http://www.mysteria3000.de/wp/

But I think – to make an original WordPress Post out of it – is not as easy as pure displaying.

hmmm….

For the last month I use the plugin ‘WordPress-bbPress syncronization’ (http://bobrik.name/code/wordpress/wordpress-bbpress-syncronization). But these plugin does it the other way – make WordPress Post to Topics in bbPress and display answers (post in bbPress) as comments in WordPress. A skilled php developer can use this plugin and change some code to realize your idea.

Unfortunately I’m no developer

[robalan]

Here are my config files, for reference:

wp-config:

<?php

// ** MySQL settings ** //

define(‘COOKIEPATH’, ‘/’);

define(‘DB_NAME’, ‘###’); // The name of the database

define(‘DB_USER’, ‘###’); // Your MySQL username

define(‘DB_PASSWORD’, ‘###’); // …and password

define(‘DB_HOST’, ‘internal-db.###.gridserver.com’); // 99% chance you won’t need to change this value

define(‘DB_CHARSET’, ‘utf8’);

define(‘DB_COLLATE’, ”);

define(‘WP_CACHE’, true);

define(‘SECRET_KEY’, ‘###’);

define(‘AUTH_KEY’, ‘###’);

define(‘SECURE_AUTH_KEY’, ‘###’);

define(‘LOGGED_IN_KEY’, ‘###’);

define(‘NONCE_KEY’, ‘###’);

define(‘AUTH_SALT’, ‘###’);

define(‘SECURE_AUTH_SALT’, ‘###’);

define(‘LOGGED_IN_SALT’, ‘###’);

define(‘NONCE_SALT’, ‘###’);

// You can have multiple installations in one database if you give each a unique prefix

$table_prefix = ”; // Only numbers, letters, and underscores please!

// Change this to localize WordPress. A corresponding MO file for the

// chosen language must be installed to wp-content/languages.

// For example, install de.mo to wp-content/languages and set WPLANG to ‘de’

// to enable German language support.

define (‘WPLANG’, ”);

/* That’s all, stop editing! Happy blogging. */

define(‘ABSPATH’, dirname(__FILE__).’/’);

require_once(ABSPATH.’wp-settings.php’);

?>

bb-config:

<?php

/**

* The base configurations of bbPress.

*

* This file has the following configurations: MySQL settings, Table Prefix,

* Secret Keys and bbPress Language. You can get the MySQL settings from your

* web host.

*

* This file is used by the installer during installation.

*

* @package bbPress

*/

// ** MySQL settings – You can get this info from your web host ** //

/** The name of the database for bbPress */

define( ‘BBDB_NAME’, ‘###’ );

/** MySQL database username */

define( ‘BBDB_USER’, ‘###’ );

/** MySQL database password */

define( ‘BBDB_PASSWORD’, ‘###’ );

/** MySQL hostname */

define( ‘BBDB_HOST’, ‘internal-db.###.gridserver.com’ );

/** Database Charset to use in creating database tables. */

define( ‘BBDB_CHARSET’, ‘utf8’ );

/** The Database Collate type. Don’t change this if in doubt. */

define( ‘BBDB_COLLATE’, ” );

define(‘COOKIEPATH’, ‘/’);

/**#@+

* Authentication Unique Keys.

*

* Change these to different unique phrases!

* You can generate these using the {@link https://api.wordpress.org/secret-key/1.1/bbpress/ WordPress.org secret-key service}

*

* @since 1.0

*/

define(‘AUTH_KEY’, ‘###’);

define(‘SECURE_AUTH_KEY’, ‘###’);

define(‘LOGGED_IN_KEY’, ‘###’);

define(‘NONCE_KEY’, ‘###’);

define(‘AUTH_SALT’, ‘###’);

define(‘SECURE_AUTH_SALT’, ‘###’);

define(‘LOGGED_IN_SALT’, ‘###’);

define(‘NONCE_SALT’, ‘###’);/**#@-*/

/**

* bbPress Database Table prefix.

*

* You can have multiple installations in one database if you give each a unique

* prefix. Only numbers, letters, and underscores please!

*/

$bb_table_prefix = ‘bb_’;

/**

* bbPress Localized Language, defaults to English.

*

* Change this to localize bbPress. A corresponding MO file for the chosen

* language must be installed to a directory called “my-languages” in the root

* directory of bbPress. For example, install de.mo to “my-languages” and set

* BB_LANG to ‘de’ to enable German language support.

*/

define( ‘BB_LANG’, ” );

?>

[robalan]

Also found this in bb-settings.php:

/**

* Should be exactly the same as the default value of the KEYS in bb-config-sample.php

* @since 1.0

*/

$bb_default_secret_key = 'put your unique phrase here';

Do I need to also define the keys here manually??

[Olaf Lederer]

That’s why I asked, I can’t remember that (it was more than two years ago ver. 0.83)

If it works like for wordpress everything is cool.

[rabbitdk]

No, from inside the bbpress forum, I want to send a topic to my WordPress front so it’s published like a ordinary blog post

[rabbitdk]

Not sure that does exactly what I want, btw I am no good with codes, but that is explained pretty detailed so I could probably try it out (however, I just messed up my bbPress install while messing with permalinks )

I want the full forum post to be published as a blog entry, by the click of a button, to promote the posts as you said

[rabbitdk]

Hi there!

I’ve been looking for a while now, I can’t find anything that suits me

I am looking for a plugin that easily lets me (the admin) add a forum post to my WordPress front.

I’ve tried out bbPress-WordPress syncronization, but this only syncs comments, right?

Thanks in advance

[psycheangels]

Fix Topic Slug phpBB Convert bbPress

add this to function.php in your template file

function fix_topicslug() {

global $bbdb;

$get_topics = $bbdb->get_results("SELECT * FROM $bbdb->topics WHERE topic_slug='' ");

foreach( $get_topics as $get_topic ) {

$slug_fix = bb_slug_sanitize( wp_specialchars_decode($get_topic->topic_title));

$topic_id = $get_topic->topic_id;

$bbdb->query("UPDATE $bbdb->topics SET topic_slug= '$slug_fix' WHERE topic_id = '$topic_id' ;");

}

}

and echo fix_topicslug in header. cek your database, and dont forget to remove the above code if you already finish.

my problem now the post_position is broken after convert to bbpress (all post is position 1) any fix ?

[zaerl]

Is it even supposed to show the WordPress users inside bbPress?

Yes it is.

I tell you what I have done. I have bbPress and WordPress on the same database and both have table prefixes. The blog is on my-domain.com/blog. The BBS is in my-domain.com/forum

On forum/bb-admin/options-wordpress.php:

1) the role map is key master, administrator, member, member, member.

2) WordPress URL is my-domain.com/blog, WordPress Blog is my-domain.com/blog.

3) Cookie salt “auth” valid, no Cookie salt “secure auth”, Cookie salt “logged in” valid.

4) AUTH_KEY <=> BB_AUTH_KEY and others set on (bb-config/wp-config).php and the NONCE_KEY <=> BB_NONCE_KEY

5) Table prefix set to the WordPress table prefix. Usually wp_

6) No advanced settings

On /blog/wp-admin/options-general.php?page=bbpress-integration-admin

1) bbPress URL = my-domain.com/forum/. Your plugin URL = nothing. WordPress type = WordPress.

2) Manual Cookie Settings tells me define( ‘COOKIEPATH’, ‘/’ ); which is defined in both config files (on top of those)

My wp-config.php:

<?php



define( 'COOKIEPATH', '/' );



define('DB_NAME', '...');

define('DB_USER', '...');

define('DB_PASSWORD', '...');

define('DB_HOST', '...');

define('DB_CHARSET', 'utf8');

define('DB_COLLATE', '');



define('AUTH_KEY', '...');

define('SECURE_AUTH_KEY', '...');

define('LOGGED_IN_KEY', '...');

define('NONCE_KEY', '...');



$table_prefix  = 'my_wordpress_table_prefix_';



if ( !defined('ABSPATH') )

define('ABSPATH', dirname(__FILE__) . '/');



require_once(ABSPATH . 'wp-settings.php'); ?>

my bb-config.php:

<?php



define( 'COOKIEPATH', '/' );



define('BBDB_NAME', 'same as wordpress');

define('BBDB_USER', 'same as wordpress');

define('BBDB_PASSWORD', 'same as wordpress');

define('BBDB_HOST', 'same as wordpress');

define('BBDB_CHARSET', 'utf8');

define('BBDB_COLLATE', '');



define('BB_AUTH_KEY', 'same as wordpress');

define('BB_SECURE_AUTH_KEY', 'same as wordpress');

define('BB_LOGGED_IN_KEY', 'same as wordpress');

define('BB_NONCE_KEY', 'same as wordpress');



$table_prefix  = 'my_bbpress_table_prefix_';

[zaerl]

I accept your opinion but at least in one case I discovered that the only way to achieve that result is to chmod 777 during the installation/integration/whatever and then switching back to 755 (on a very crap host). So I said what I said cause I tought that it can be a good hint. Apparently it is not (and it seems that my words are even funny) and it’s ok. Maybe it was a combination of factors and the 777 was completely useless.

I’m not a bbPress expert cause I have started to use this software a couple of weeks ago. I’m just trying to learn, help those who encountered my same problems and sharing my code.

Regards.

[zaerl]

I’m trying to find a solution and I can find it only making questions. Are:

define('BB_AUTH_KEY', 'something');

define('BB_SECURE_AUTH_KEY', 'something');

define('BB_LOGGED_IN_KEY', 'something');

define('BB_NONCE_KEY', 'something');

from bb-config.php equal to:

define('AUTH_KEY', 'something');

define('SECURE_AUTH_KEY', 'something');

define('LOGGED_IN_KEY', 'something');

define('NONCE_KEY', 'something');

from wp-config.php? Have you specified define('COOKIEPATH', 'the path'); on _both_ files?

[robalan]

Yes. Installed, copied the “define” code into wp-config… I’ve tried everything you’d find on other forum entries on the topic. I wouldn’t have started my own thread unless I had tried the default “have you…” options and still couldn’t get it to work…

Any other ideas?

[bramruiter1]

The link is sub.salonindien.nl and it’s a dutch forum. I hope you can help me out here. If you need more information, just scream and I’ll get it for you.

[Gautam Gupta]

GlotPress runs on BackPress too. BuddyPress doesn’t need BackPress because much code of it is already there in WordPress. And WordPress will eventually shift to BackPress. Though, that’s really not a matter of argument.

@Yuri

And main question: Who is admin of this site with full access if Matt left project?

As far as I know, matt, sambauers, and mdawaffe are keymasters and trent, chrishajer and _ck_ are moderators.

[kevinjohngallagher]

Back from my holidays and hopefully ramping up some bbPress dev in the next week or so, and this looks like a nice thread to come back to

The thing that I think a few folks have missed out on, is that the biggest changes from bbPress 0.9 to bbPress 1.0 is that alot of the core functions of the backend were unified into BackPress. While this added bloat to be sure, it basically gave us a unified platform on which ‘all’ of the automattic software solutions would be based. Except… none of the others moved to BackPress.

So we don’t have any (to the best of my knowledge) WordPress functions in bbPress, but also with “deep integration” we’re loading multiple classes and functions that effectively do the same thing. With deep integration we duplicate all of the base calls and functions every time we load a page.

BuddyPress got round this by ripping out all of the backpress stuff, and making the bbPress functions call the WordPress functions. BuddyPress’ forum is based on bbPress, its isn’t bbPress. This is where Sam kind of got the short end of the stick. Had WordPress moved to BackPress (instead of porting WP changes into BackPress) then all of the Automattic software solutions would be on the same base platform, and integration between them all would be a doddle. It also would have meant that bbPress could be both a stand alone AND a plugin, as it would effectively be a large “module” on top of BackPress functions.

The realsim is, that without any form of Project Management (and i know that phrase is where people start to hate me) or cohersion between the Automattic projects or developers and contributors, we’re effectively going to go in circles here.

Today marks the 3rd Month with no blog post or communication (other than the infamous “I just want to quit the whole project” statement from Matt). As much as that is disheartening, its not a shock. Matt (the person) and Matt (the developer) and those he works with on these projects have their hands full right now; and from what I’ve seen Chris has continued to steady the ship in a wonderful fashion… but make no mistake we’re drifting aimlessly in the current direction. Lets just keep the ship afloat, try and fix some bugs, and we’ll see what happens when we’re closer to a release.

Hope you’re all having a wonderful afternoon.

[zaerl]

bbPress _must_ not become a WordPress plugin. First of all because a BBS isn’t always associated with a blog and in my case this never happens. bbPress gain the attentions of a lot of people tired of bloatware engine like phpBB or slow engine like vBullettin. I switched to bbPress on all my sites for these reason.

Seconded a lot of people (as far as I know) chose bbPress because they can access to a WordPress style plugin system. If you have ever written a plugin for WordPress you can edit a bbPress one easily in order to accommodate your needs. But if bbPress will be a plugin of WordPress you will download a plugin… of a plugin? This is kind of confusing IMHO. Obviously I’m not talking about PHP programmers or in general skilled people but of regular users.

Third I think that the bbPress project deserve its own space. It is a too well done piece of code and for being a mere WordPress plugin.

[zaerl]

Did you activate Askimet? In my forums it filters away 99.9% of spam. I think that allowing the inclusion of <img> is always a bad idea.

[Kevin Muldoon]

Hey all,

For years I’ve used vBulletin for discussion forums. However, I have recently began to use bbPress for support forums on WordPress powered sites.

There are a lot of good tutorials on bbPress integration however some of the articles don’t go into that much detail in some areas so I decided to write my own tutorial on the matter.

It’s difficult to cover everything, but I have tried to note some of the most common problems which arise when integrating bbPress and WordPress. If you are unsure about anything please let me know

http://www.wpmods.com/integrate-wordpress-bbpress

Thanks,

Kevin

[gerikg]

It hasn’t happened yet (a completed plugin) and with no developers, or developers on other projects, I don’t think it will happen anytime this year. I’ll bet on it. Either way, I read a lot of “let’s do this and let’s do that” but no action. I don’t think any of us can demand anything. We aren’t paying anyone anything. I doubt anyone donates either. We can request it, we can be annoying about it, but the choice is not ours. If you haven’t noticed the more annoying people get, the less developers we have. We can start a movement away from bbP once it’s a plugin but it hasn’t happened. This is premature complaining because it hasn’t happened.

We should focus on four things

1 Getting the current plugins to have admin menus for non-php editors.

2 More Plugins

3 More themes (the reason I picked wordpress over drupal)

4 Documentations. It will be easier for people to code once the basic map is mapped out instead of everyone starting from ground zero. https://bbpress.org/documentation/

[johnhiler]

If you’re serious about keeping bbPress as standalone software, you’re in luck: that’s exactly what bbPress is doing for the next version or two. No need to fork just yet: just get more involved with bbPress.

bbPress will probably start to begin the slow process of becoming a WordPress plugin later this year or maybe next year… at which point, you’ll be better acquainted with the software and in a better position to consider a fork!