Just put this in your theme’s functions.php (create one if you don’t have one). Also put this in the beginning of code – <?php and this at the end – ?>
This is a good tutorial (with screenshots) for integration – http://www.wpmods.com/integrate-wordpress-bbpress
And for the time being, there’s no need to create a fork. Just create new tickets, contribute patches and after testing, chrishajer might commit them.
Matt did mention that about 10 people have access to site – I don’t know the names – maybe chrishajer also has the site access (I am not sure).
This tutorial also explains integration for WordPress 3.0 – http://www.wpmods.com/integrate-wordpress-bbpress (WP 3.0 also has cookie salts). Haven’t dug into this yet, maybe will do later.
about style – i saw that topic long time ago, but where is Sam? you said that there are no alive admins…
Sam has left automattic, but he sometimes replies on the trac tickets. (See the bbPress.org 2.0 – sneak peak topic’s last pages). He has also mailed the design files to some other automattic guy.
Why do we need to bother Matt again? We have everything we need to get the next version out the door… the cavalry isn’t coming to save us, but I think that’s ok.
Atleast we must inform the person whose project it was initially – you wouldn’t like if someone had access to your project and kept making changes, releasing new versions etc. in your absense.
Automattic is a company which owns all these projects (WordPress etc) – http://automattic.com/
And Sam had already made a new design for this forum a while ago but has not been implemented yet – https://bbpress.org/forums/topic/sneak-peek-at-bbpressorg-20
@Yuri
Talk practically, as if automattic would give you the passwords. By the way I think this website is owned by matt, as he said in one of the IRC chats or this forum. You can also check here – http://www.pir.org/get/whois?domain=bbpress&Submit=Search while wordpress is owned by automattic – http://www.name.com/whois_result?type=domain&domain_name=wordpress.com&submit=+Submit+
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.
THIS IS IMPORTANT POST, WHICH EVERYONE SHOULD READ:
For the time being, according to the plan laid down by Matt (which was weeks ago), bbPress will continue to be a standalone till some 1.2 version and then change into a plugin.
Now there are 2 things for you to consider:
- Start your own project and if you start, then there will be 2 things:
- Either your project would get more attention if development doesn’t start here
-
- Or your project and hard work would go into vain if the development starts here/or you still don’t get popularity. So you might consider point 2.
- Wait for the development to start (which would only happen when Matt pays attention to it, maybe after WP 3.0?). You might now want to start your own development, then see point 1.
-
I know that you might be confused, but I am also confused as much as you’re, thinking should I keep developing plugins for bbPress or not (nor any donations have come in the recent days). I’ll probably start developing plugins for BuddyPress/WordPress and be active on projects like After the Deadline/GlotPress.
I personally think that Matt is not considered about this project because (I might be wrong):
- See his reply here – https://bbpress.org/forums/topic/whats-happening-with-bbpress/page/5#post-64425 (which was his last post on this forum).
- I mailed him to let me take on the development and he said to be just active on trac, maybe he has some other plans down the line?
Right now, chrishajer is committing patches to the trunk (as he has the svn access) and IMO, trunk is more stable than 1.0.2.
Another thing is that half the people want it to be a plugin and half want it to be a standalone. Thus, I posted this method – https://bbpress.org/forums/topic/bbpress-as-a-wordpress-plugin-thoughts#post-64476, and it is how BuddyPress integrates bbPress forums into WP/BP install. This way it will remain a standalone for those who want it to be simple, light, fast etc. and plugin for those who want deep integration, ease of install etc. The problem that arises here is the plugin and theme repo, anyone has a solution to that? Maybe here’s one – https://bbpress.org/forums/topic/bbpress-as-a-wordpress-plugin-thoughts#post-64737
You really shouldn’t go that way, please.
There’s already a ticket #1233
I have no plan to make this, but I may revisit this idea in the future.
There’s no plugin for the time being, but it can be made by doing this:
1) Create an admin page where the admin puts all the ads and keywords
2) preg_match the post_text for the keywords and display the ad.
BTW, are you the one of pagalguy.com?
This is a fix just to solve your problem:
- Open
/bb-includes/backpress/class.wp-http.php
- At the starting, after
<?php put (on a new line):
if ( !class_exists( 'WP_Http ' ) ) {
- And at the end put:
}
I would probably report this issue on the BackPress trac
Download a fresh copy of bbPress and upload it to your server. This might solve your issue.
Just put the embed video code in the front-page.php template.
You would need:
define( 'BB_FORCE_SSL_ADMIN', true ); //force use of ssl in the admin area
define( 'BB_FORCE_SSL_USER_FORMS', true ); //force use of ssl on user forms like login, registration and profile editing
You can check the source here – http://xref.yoast.com/bbtrunk/nav.html?bb-settings.php.source.html#l458
Topic title length or topic post length?
Or you may use this, if the above doesn’t work for you:
<?php
function unset_arel( $tags ) {
unset( $tags['a']['rel'] );
return $tags;
}
add_filter( 'bb_allowed_tags', 'unset_arel', -1 );
?>
Put this in your theme’s function.php (create one if it is not there):
<?php
function change_dofollow_to_nofollow( $content ) {
return str_replace( array( ' rel="dofollow"', " rel='dofollow'" ), ' rel="nofollow"', $content );
}
add_filter( 'post_text', 'change_dofollow_to_nofollow', -1 );
?>
If the plugin was rejected, you should have got a mail (you also get one when it gets approved).
