[_ck_]

Yes you can, easily.

I have a mini-plugin for this somewhere around here…

Here you go:

<?php

/*

Plugin Name: Delete Own Post

*/

function delete_own_post($retvalue,$capability,$args) {return ($capability=='delete_post') ? bb_current_user_can('edit_post',$args[1]) : $retvalue;}

add_filter('bb_current_user_can','delete_own_post',10,3);

?>

Note that they can only delete for as long as they can edit.

Meaning after the 1 hour default, no more delete.

But you can change the timeout in the admin settings.

[Ashish Kumar (Ashfame)]

What’s all missing in terms of features in 0.9 when we compare it to bbPress 1.0+ ?

• XMLRPC – but do we use it right now? I haven’t heard of anything using bbPress XMLRPC
• WordPress matching backend

What else? I never used 0.9 much. BTW, I think most of the functionality a forum owner would need are covered by _ck_’s plugins

I would like to hear from you guys.

[mdolon]

Thanks zaerl!

In terms of integration, I connected the databases between WP and bbPress during installation and made sure that the cookie information matched in both configuration files (bb-config and wp-config). Those two steps made it so when a user registered and logged in at my forum, they were logged in at my blog too.

I didn’t really need any of the WordPress functions in bbPress so I skipped the deep integration part (calling wp-load). The only bit of dynamic code in my header is checking to see if a user is logged in, and on WordPress you can do that with:

<?php if(is_user_logged_in()){?>

Do something

<?php } ?>

I use caching to load the sidebar and footer. When someone visits my main site, http://devgrow.com/, it creates a cache of the sidebar and footer if there is no existing cache or if it’s older than 6 hours. The cache is just a text file that contains the output of the dynamic bits in my sidebar in HTML format, which I just include in my bbPress sidebar and footer.

I also wrote some custom code to pull the recent and popular (most replies) topics and display them with their topic icons.

Hope that makes sense, let me know if you have any other questions.

[pagal]

paste it before </head>

<meta http-equiv="content-type" content="text/html; charset=iso-8859-1"><br />

<title>Unique Title Here</title><br />

<meta name="description" content="Description of your page" /><br />

<meta name="keywords" content="keyword1, keyword2, keyword 3" /><br />

<meta name="robots" content="index,follow" /><br />

<meta name="distribution" content="uk, united kingdom, london, global"><br />

<meta name="document-classification" content="another,keywords, here"><br />

<meta name="rating" content="General"><br />

<meta name="MSSmartTagsPreventParsing" content="TRUE"><br />

<meta name="Copyright" content="website titlet"><br />

<meta name="developer" content="http://www.developer-name.com"><br />

<meta name="Author" content="Author Name"><br />

<meta http-equiv="pragma" content="no-cache" /><br />

[_ck_]

Note that filter is only available in bbPress 1.0 and 1.1, if you are trying to do it in 0.9 it will not work.

In 0.9 unfortunately you’d have to edit the end of registration-functions.php

[_ck_]

Here is what (the highly respected) Mark Jaquith has to say about the very similar problem over on the WordPress side:

Why WordPress Themes are Derivative of WordPress

And I guess the way I stated this whole thing was wrong to begin with, what I meant instead was that if you sell premium themes to remember they also have to be GPL – IF you start with another theme that is GPL.

You can’t make a premium theme that uses GPL code from another theme or bbPress/WordPress itself and sell it without making it GPL.

(now I think I finally said it correctly)

I guess the sad conclusion to all this is how bbPress standalone now has some really nice premium themes but is ending standalone development.

[mdolon]

Check it out: http://devgrow.com/discuss

It took about a week to get everything the way I wanted. At first I wanted to do a deep integration but it was too much of a pain, so I just ended up writing some custom code to cache most of my sidebar, header and footer elements from my blog and display the cached content in bbPress.

Plugins I’m using:

• Allow Images
• Auto Add to Favorites
• BBcode Lite
• Google Sitemap Generator
• Post Count Plus
• Post Count Plus for WordPress
• Subscribe to Topic
• Topic Icons
• Custom Plugin for Recent/Popular Topics

And some more custom code throughout the templates. Would love to answer questions or hear feedback!

[AaronIsaac]

Okay, first thing’s first… if this is the forum on the bbPress site itself, it really needs to be a bit more of a better example. As it is, when I get to the forum I’m first faced with a giant tagcloud, then I have to scroll all the way down past a huge list of posts to get to the actual individual forums such as this one. Of course, I could hit the button to start a new topic at the top of the top of the page but not only is that counterintuitive, it’s a really bad idea in general that will get people just Pcoming in and posting without looking at other posts first. I’d hoped the layout would have been changed by now at least.

Second problem, and this is one I’ve had on the wordpress forums as well but never bothered to ask about it. At the bottom of the post box it lists allowed tags (shortly after mentioning “Enter a few words (called tags)” with a link to the tagcloud rather than a definition of tags), but what gets me is “Put code in between backticks.” I’ve been running forums since before ISPs could offer residential Internet connections and yet I have absolutely no clue what that means. Unless this software is only meant for WordPress users (which I’m one of, btw), it would be best to get a bit more accessible to ordinary people in terms of language/jargon.

My other large beef is that the forums read like blog comments rather than forum discussions. Threading would be my number one request if I intended to use it. I guess my number two request would be integrating said threaded comments into the comments section of blog entries for those using it with a WP blog, though that’s a lot more complicated. I’d want to start off with the other way around by having the blog able to automatically display posts from certain sections such as Announcements and such. I’m not sure if that functionality exists yet, so apologies if it does. If not, I suppose a workaround could be reading the rss feed from that section into the blog section, but aggregating your own feeds is a fairly silly notion.

That’s it for initial feedback right now. I may come take another look when the software has matured a bit… by that I mean the core, it shouldn’t have to depend on plugins and themes to have very basic funcionality on its own.

[_ck_]

It’s hand coded, probably into the template system.

It’s parsing the readme.txt file.

Far too custom that you’d ever find a plugin for it.

It’s probably using in part some of the code from Mark Jaquith who designed the readme.txt format for Matt/Automattic and implemented by mdawaffe (Michael)

http://wordpress-plugin-readme-parser.googlecode.com/

[hpguru]

I think bbPress standalone is dead in 2010.

Matt Mullenweg: Non-plugin bbPress development is going to continue until we have a perfect importer so people will be able to bring their content out of the legacy codebase.

bbPress 1.1 may be here.

[Greg]

I guess one could also use the check on BBP_VERSION (or equivalent) to print an error message when the plugin refuses to activate.

But a user would still need to install the plugin or look in the code (or read the README if the plugin author was good enough to mention the dependency).

[Ashish Kumar (Ashfame)]

@_ck_

Thanks a lot

I am gonna ditch v1.0+ and start using 0.9 from now on. Will downgrade my other installations too.

[_ck_]

Oh sorry, I lost track, too many things going on everywhere.

Save it into a plugin (ie. custom-registraton-email.php) put it into your my-plugins/ directory and activate.

[Gautam Gupta]

One can easily do a check on activation if BBP_VERSION is defined and optionally a version_compare check too, and if it doesn’t satisfy the condition, then the plugin should deactivate itself.

[willcrain]

I am using the bbpress integration plugin to sync my wp and bbpress site up for users to login/logout.

I am having some issues getting my front-page login to work the way that i want it to. Currently (complete code and file setup at bottom) when i try to login initially i have the fields:

Community Login or [link – Register] – [link -Lost Password?]

[field – username] [field – password] [btn – login]

when i input the username and password and hit login it shoots me to the login page where i need to do this again in doer to login.

currently i have this code attributed to my login button:

<input type="image" src="<?php bb_option('uri'); ?>my-templates/discussion_center/images/top_login_btn.png" width="67" height="23" alt="Submit Form" value="<?php _e('Login');?>" />

i am guessing thats where the issue lies with that. i would like it to NOT go to another page and to just log in right there.

Next, after i am logged in the set up is like this:

Welcome back, username!

[link – View your profile] [link – logout]

the logout link seems to work, logging me out of my bbpress install, but it doesnt log me out of my wp install… any fix for that?

i added the cookies line to the wp-config.php for the plugin, am i supposed to add it to the bb-config.php too?

Thanks for the help in advance!!!

<b>In my header.php ::</b>

---

<?php login_form(); ?>

<?php if ( is_bb_profile() ) profile_menu(); ?>

<b>In my logged-in.php ::</b>

---

<div id="loginreg" class="clear">

<span id="welclogout"><?php printf(__('Welcome back, %1$s!'), bb_get_current_user_info( 'name' ));?>

<p>

Use the links below to manage your account.

<?php echo bb_get_profile_link('View your profile'); ?>

<?php bb_admin_link( 'before= | ' );?>

<?php bb_logout_link(); ?>

</p>

</span>

</div>

<b>in my login-form.php ::</b>

---

<div id="loginreg">



<p>Community Login or <?php printf(__('Register'), bb_get_option('uri').'register.php')?> - Lost Password?</p>



<form method="post" name="loginform" id="loginform" action="<?php bb_option('uri'); ?>bb-login.php">



<div class="left">

Username

<input type="text" name="log" id="user_login" class="text input" value="<?php if (!is_bool($user_login)) echo $user_login;?>" size="20" tabindex="10" />

</div>



<div class="center">

Password

<input type="password" name="pwd" id="user_pass" class="text input" value="" size="20" tabindex="20" />

</div>



<div class="right">

<input name="remember" type="hidden" id="remember" value="forever" tabindex="90" />

<input name="re" type="hidden" value="<?php echo $re; ?>" />

<?php wp_referer_field(); ?>

<input type="image" src="<?php bb_option('uri'); ?>my-templates/discussion_center/images/top_login_btn.png" width="67" height="23" alt="Submit Form" value="<?php _e('Login');?>" />

</div>

</form>

</div>

[Greg]

Hmmm. Seems that even the mod is hijacking threads on bbpress.org these days…

Feel free to start a different thread to talk about the specific performance aspects of bbPlugin versus bbStandalone.

One more attempt to focus this thread on the original question: I am interested in a discussion on the relative merits of evolving bbStandalone and bbPlugin independently versus in a coordinated fashion, NOT the relative merits of bbStandalone versus bbPlugin.

Repeating the advantages of both, with one additional pro that I thought of for the coupled roadmap.

Advantages of a coupled roadmap:

– Higher quality for standalone (benefitting from the larger installed base of the plugin)

– Better performance for the plugin (benefitting from the big standalone sites)

– More tight WP integration is likely for standalone

– Easier “cross-grades” between plugin and standalone version

Advantages of independent evolution of the plugin and standalone versions

– More flexibility in release roadmap for both versions

– No compromises for either version

[willcrain]

I am using the bbpress integration plugin to sync my wp and bbpress site up for users to login/logout.

I am having some issues getting my front-page login to work the way that i want it to. Currently (complete code and file setup at bottom) when i try to login initially i have the fields:

Community Login or [link – Register] – [link -Lost Password?]

[field – username] [field – password] [btn – login]

when i input the username and password and hit login it shoots me to the login page where i need to do this again in doer to login.

currently i have this code attributed to my login button:

<input type=”image” src=”<?php bb_option(‘uri’); ?>my-templates/discussion_center/images/top_login_btn.png” width=”67″ height=”23″ alt=”Submit Form” value=”<?php _e(‘Login’);?>” />

i am guessing thats where the issue lies with that. i would like it to NOT go to another page and to just log in right there.

Next, after i am logged in the set up is like this:

Welcome back, username!

[link – View your profile] [link – logout]

the logout link seems to work, logging me out of my bbpress install, but it doesnt log me out of my wp install… any fix for that?

i added the cookies line to the wp-config.php for the plugin, am i supposed to add it to the bb-config.php too?

Thanks for the help in advance!!!

<b>In my header.php ::</b>

---

,

<?php login_form(); ?>

<?php if ( is_bb_profile() ) profile_menu(); ?>

‘

<b>In my logged-in.php ::</b>

---

,

<div id=”loginreg” class=”clear”>

<span id=”welclogout”><?php printf(__(‘Welcome back, %1$s!’), bb_get_current_user_info( ‘name’ ));?>

<p>

Use the links below to manage your account.

<?php echo bb_get_profile_link(‘View your profile’); ?>

<?php bb_admin_link( ‘before= | ‘ );?>

<?php bb_logout_link(); ?>

</p>

</span>

</div>

,

<b>in my login-form.php ::</b>

---

,

<div id=”loginreg”>

<p>Community Login or <?php printf(__(‘Register‘), bb_get_option(‘uri’).’register.php’)?> – Lost Password?</p>

<form method=”post” name=”loginform” id=”loginform” action=”<?php bb_option(‘uri’); ?>bb-login.php”>

<div class=”left”>

Username

<input type=”text” name=”log” id=”user_login” class=”text input” value=”<?php if (!is_bool($user_login)) echo $user_login;?>” size=”20″ tabindex=”10″ />

</div>

<div class=”center”>

Password

<input type=”password” name=”pwd” id=”user_pass” class=”text input” value=”” size=”20″ tabindex=”20″ />

</div>

<div class=”right”>

<input name=”remember” type=”hidden” id=”remember” value=”forever” tabindex=”90″ />

<input name=”re” type=”hidden” value=”<?php echo $re; ?>” />

<?php wp_referer_field(); ?>

<input type=”image” src=”<?php bb_option(‘uri’); ?>my-templates/discussion_center/images/top_login_btn.png” width=”67″ height=”23″ alt=”Submit Form” value=”<?php _e(‘Login’);?>” />

</div>

</form>

</div>

,

[deadlyhifi]

The plugin is Add bbPress Default Role. It’s three lines of code so you may be better just writing it into your functions.php file.

[_ck_]

<cite>ashfame</cite>

I guess all your plugins are tagged https://bbpress.org/plugins/tags/_ck_

right?

And I believe even your updated plugins support 0.9 ?

Unfortunately the plugin section is still broken and does not import tags so the _ck_ tag is no longer complete there (update: someone appears to have fixed it in the past 24 hours)

For now this is the only way to find them all:

http://bbshowcase.org/forums/topic/_ck_-plugin-catalog-index

Virtually 100% my plugins will support 0.9 (except ones specifically made to “fix” 1.x)

<cite>Mark McWilliams</cite>

Not with WordPres 3.0 anyway, 1 install, multiple sites!

Well, multiple BLOGS, I am not sure if they can get multiple forums going on the first version, we’ll see. But I am sure it’s a goal of Matt’s so they can use it on WordPress.com

[Mark McWilliams]

_ck_: As far as I could guess, you’d have to install multiple copies of WP.

Not with WordPres 3.0 anyway, 1 install, multiple sites!

[Erlend]

@Ryan: I had JS enabled but.., aha, I never noticed the double-click edit upon mouse hover before. Neat

Now, the thing I encountered in both the P2 theme and Justin’s forum plugin is: Neither (seems to be able to-) take advantage of WordPress’ own in-built rich text editor.

I probably did not make this clear enough in my first post. My main point sort of ended up in the second to last paragraph:

What I’d love to see is rich front-end editing based on the native WP editor

What I’m inquiring about is:

How to achieve front-end editing with WordPress’ native rich editor?

The main question is of course ‘how will bbPress go about doing this?’, but clearly this method is still unbeknown to many plugin authors who could greatly benefit from it.

(Disclaimer: My project relies on the bp-wiki plugin, and I am indeed curious as to the possibility of a a more conventional approach to rich front end edits in the future.)

One ‘almost’ example I found is this one:

https://wordpress.org/extend/plugins/tinymce-excerpt/

It grabs the native editor and displays it somewhere new. However I suspect it can only do so because it’s still within the confines of the admin backend. Posting and editing content from front-end can clearly be achieved, but apparently with severe limitations. It’s getting functions that are normally limited to the backend (tinymce editor, file upload, etc) to the front-end that is awkward.

Speaking of which, feasibility image/file uploads would make for an excellent follow-up question, but maybe you’d rather have me start a new thread for it?

[Erlend]

Alright, appreciate the response. I think we’ve exhausted this discussion then

[Matt Mullenweg]

Non-plugin bbPress development is going to continue until we have a perfect importer so people will be able to bring their content out of the legacy codebase.

[Matt Mullenweg]

Greg, I think we agree, just have different ideas about where that line is drawn. I’ve laid out the core philosophy as a framework for discussions above. I have never advocated making every plugin a core feature, and conversely I doubt you’re suggesting making every line of code in bbPress a plugin.

Balancing between the two is how development happens, and is best navigated in the context of a specific anchor (feature) rather than in abstract.

[Greg]

I can see strong arguments for both a wp plugin and a standalone forum.

Also, the reality is that both will exist in the future. The WP team is very passionate about “bbPress as plugin” and at the same time some existing large installations will see to the continuation of standalone version in some format.

So it might be good to frame this decision differently than plugin versus standalone… The real question is: to what extent do we want the plugin and standalone versions of the bbPress code base to evolve independently versus in a coordinated way?

Simplistically, the two options are:

1. coupled roadmap with coordinated releases or periodic rev/fwd integrations

2. independent roadmaps that diverge over time (the current plan of record)

Both options (coupled roadmap and independent roadmap) can work, but it would be better for this decision to be the result of thoughtful discussion.

To kick things off, here are some pros of a coupled roadmap:

– Higher quality for standalone (benefitting from the larger installed base of the plugin)

– Better performance for the plugin (benefitting from the big standalone sites)

– More tight WP integration is likely

And some pros of independent evolution of the plugin and standalone versions

– More flexibility in release roadmap for both versions

– No compromises for either version

Another more subtle effect to consider is the impact on dev resources invested in the code base. For example, I think that there are currently a lot of “silent” but significant resources being invested in standalone bbPress development. It would be great to pull more of that work into the official project, but I fear that opportunity will go away once the move is made to “bbPress as plugin”.