The styling must be in the a file somewhere yeah? So why not have some sort of file map or layout so people could get in and play with it a little at their own peril?

I'm answering myself :)

I followed your clue and found this link: http://codex.wordpress.org/Taxonomies which explains very well what to do for creating a 'forum_categories' taxonomy.

Then I think I can just call bb_has_topics from my template with this parameter:

array('forum_categories' =>
array('searched_category1', 'searched_category2, ....)
)

I will try and let you know.

Thanks a lot !!

This question is not about bbPress but about this site. I have edited my profile but I don't see how can I change my picture (avatar). I tried on Internet Explorer and also on FireFox, but it looks like there isn't a field for doing this.

Thanks.

I agree, I think I will use forums (and forums categories) for canonical place, and I will try the WordPress categories taxonomy to do what I need. However, I have two questions:

1. Should I modify the core of bbPress for archieving this ? If I should, I don't really like it because if a new version of bbPress is published then I won't be able to upgrade easyly.

2. Does it already exist a plugin or something similar where this (using WordPress categories) is already implemented ?

Many thanks.

What you want to do *could* be possible, but I think you'll have more success creating your own taxonomy structure to group topics together with, and using the core Forum/Category structure as the canonical place where that topic ultimately lives.

Research creating custom WordPress taxonomies. It should help you achieve what you're trying to do pretty easily.

I wonder if a topic can be assigned not just to a single forum, but to a multiple forum, just like WordPress posts can be assigned to multiple categories.

Imagine I have a question related to computers and medecine. Can I create a single topic under both forum categories computers and medecine ?

Thank you.

And about standalone package idea, I disagree with it since as part the wp plugin is the best reason I going to use it.

if ( !is_user_logged_in() || ( is_multisite() && !current_user_can( 'manage_network_users' ) && bbp_is_user_home() && !apply_filters( 'enable_edit_any_user_configuration', true ) ) || !current_user_can( 'edit_user', bbp_get_displayed_user_id() ) ) {

The key portion of that being:
( is_multisite() && !current_user_can( 'manage_network_users' ) && bbp_is_user_home() && !apply_filters( 'enable_edit_any_user_configuration', true ) )

This appears to be written intending to disable the ability for site admins on a network to edit users. However the code here does not seam to do any tests for what the user id is and who's currently logged in.
This has the unwanted effect of removing the ability for a normal non-superadmin user to edit their own profile because this code activates when multisite is enabled and doesn't take the fact they are trying to edit their own profile into account.

But I have to second the standalone package idea. That sounds like it would open up very interesting possibilities.

Angela

Fatal error: Call to undefined method stdClass::have_posts() in wp-content/plugins/bbpress/bbp-includes/bbp-topic-template.php on line 308

Line 308 of bbp-topic-template.php looks like..

function bbp_topics() {
	global $bbp;

	// Put into variable to check against next
	$have_posts = $bbp->topic_query->have_posts();

	// Reset the post data when finished
	if ( empty( $have_posts ) )
		wp_reset_postdata();

	return $have_posts;
}

Not sure what the problem is here...

I can do some simple PHP, mostly without the classes/objects stuff (I'm currently in the process of learning PHP, so would really like some practical experience other than tweaking plugins).

I'm better with MySQL. I can devote perhaps 2 to 3 hours a day.

I'm located at the UTC+8 timezone (although I probably can't get up at 5 AM to attend the dev meeting).

Angela

https://core.trac.wordpress.org/ticket/19961

https://core.trac.wordpress.org/ticket/19958

http://bbpress.trac.wordpress.org/ticket/1737

http://bbpress.trac.wordpress.org/ticket/1738

http://bbpress.trac.wordpress.org/ticket/1739

http://bbpress.trac.wordpress.org/ticket/1740

http://bbpress.trac.wordpress.org/ticket/1741

http://bbpress.trac.wordpress.org/ticket/1742

http://bbpress.trac.wordpress.org/ticket/1743

http://bbpress.trac.wordpress.org/ticket/1744

http://bbpress.trac.wordpress.org/ticket/1745

http://bbpress.trac.wordpress.org/ticket/1746

http://bbpress.trac.wordpress.org/ticket/1747

http://bbpress.trac.wordpress.org/ticket/1748

http://bbpress.trac.wordpress.org/ticket/1749

http://bbpress.trac.wordpress.org/ticket/1750

http://bbpress.trac.wordpress.org/ticket/1751

Standalone bbPress

I appreciate the reason why you sought to create a standalone version of bbPress.

The plugin makes sense because it provides access to a large captive base of WordPress users. But on the other hand it ties bbpress down to WordPress, making it usable *only* with sites that use WordPress.

What if someone who doesn't use WordPress wants a forum software?

Well, I have a suggestion. bbPress should ONLY be developed as a WordPress plugin (as I believe it is now).

However, a standalone package should be available at bbpress.org. This would basically be a bundle of WordPress and bbpress, where bbpress is active by default.

Additionally, by default, the forum root would be selected as the static page that appears as home. You will need some help from your colleagues at WordPress for this...at the moment only pages (and not custom post types) are allowed to be selected as home. (update: https://core.trac.wordpress.org/ticket/19958 )

To sum up, it will still be WordPress with a bbPress plugin, but would be *sold* as forum software. The distinction being target market. bbPress plugin is targeted and marketed to people who use WordPress and are LOOKING for a forum software that integrates with it. The standalone package is targeted and marketed to people who are looking for forum software.

You might think this is a zany idea, and it probably is. It just might work, though.

However, bbPress is already a very good script. Some of my suggestions e.g. #1 #2 and #5 are almost completely non-technical and basically require some manual labor, which I am happy to provide.

I beg to differ with you on documentation. You are right that technical documentation, esp. for plugin developers etc would require an understanding of the codebase. However, I am talking about end-user documentation...in moving to bbPress, that is one of the hurdles I faced. I have also noted a pattern of big concerns of prospective and new users, both here and on WordPress.org

I think if the non-technical parts are dealt with, along with ONE technical part (migration), that would make an immense difference to the adoption of the software. And, of course, a significant number of users will generate interest among developers.