[Ryan Hellyer]

Why do the powers that be not see reason in what _CK_ says above?

Justin Tadlock’s forum plugin avoids these problems. Why can’t the new Automattic created one too?

http://justintadlock.com/archives/2010/07/16/a-wordpress-forum-plugin-using-custom-post-types

[_ck_]

Holy cow, there is some serious kool-aid drinking going on.

You can’t just up-end a community and then ask everyone to be positive about it.

Zero consultation was done with the community/contributors, exactly the same amount that was done with backPress. Let’s be CRYSTAL CLEAR about that right from the start.

For the people showing up out of the blue and jumping into the bbpress project suddenly this year, having NEVER contributed in the past few years, and in effect telling us to “shut up and go along with it” – I am seriously not going to take that nonsense, even if you say “please”.

You don’t just take a project and completely re-write it into something else and take it’s name. It’s not yours, it belongs to the community who adopted the existing program and worked many hours to install it, figure out bugs and improve it. It’s not yours to show up late and completely re-invent after that.

You don’t wash away the years of forum questions and answers by intermingling them with a different, incompatible version.

You don’t just call it 1.2 when it will have nearly zero code/layout/theme/compatibility with 0.9/1.0/1.1 – I mean sheesh, even calling it 2.0 would have been a minimal effort to note it’s something different but no, 1.2 is to confuse as many as possible either on purpose or out of apathy.

You don’t insist it has nothing to with Automattic when the SVN/TRAC slots were decided and made by Automattic people on Automattic servers at Matt’s directive as a plugin for another Automattic managed product.

The main developer of bbPress 0.8/0.9 was an Automattic employee (Michael) under Matt’s directive, the main developer of 1.0 was an Automattic employee (Sam) under Matt’s directive. It’s an Automattic product, always will be. Matt has been trying to figure out how to monetize it for years which is why it keeps getting messed with, so he can make a wordpress.com equivalent for forums.

Even JJJ admitted a YEAR AGO, that it’s a good thing bbPress is separate from WordPress because of how blogs and forums are different even though they share similar data structures. But now it’s a 180 turn in the opposite direction because of Matt’s whim.

If you want me and the other people who have a problem with this to shut up, it is SUPER SIMPLE to end this problem:

1. don’t call it bbPress
2. start another Automattic site to build your forum plugin

   (or attach it to a wordpress.org subdomain which probably would have been more appropriate)

3. finish what was started: it’s too late for 0.9 to be properly finished as it should have been into 1.0 before the 180 with backPress but it’s not too late for 1.1 to be released and then matured into 1.2

Don’t just march into an existing community, take it over and change it’s course into another 180 turn for the second time in three years and expect anyone to just smile and go along with it.

What you aren’t seeing are the 10,000+ sites that don’t post here and have successfully adopted it, even with virtually no advertising or support from the WordPress community.

Ironically I would have far more easily accepted another forum project being started by Matt and unfortunately letting bbPress slowly die over what is being done now.

[_ck_]

There actually is a section on TRAC for “bbpress.org website” to report bugs, so I am going to suggest we start posting there and fill trac with trackable bug reports that can be fulfilled and commented on individually?

https://trac.bbpress.org/newticket

go to “component” and select “bbpress.org website”

feel free to still post them here but on TRAC is even better too

[xarzu]

I have moved my wordpress blog from a subdirectoy down to the root and it seems to be working fine now.

When I installed the wordpress and the bbpress, I gave settings to ensure that they were tied together.

Now that I have moved the wordpress to the root directory, what do I have to change in the wordpress and the bbpress to make sure that when you post to the blog it appears in the forum etc.?

[chrishajer]

If your WordPress site is at http://www.example.com, and that corresponds to “wordpress-instance”, then you want the folder “bbpress-instance” accessible at http://www.example.com/bbpress-instance.

It’s hard to tell the hierarchy of your folders from your post, but basically, you want a folder (with bbPress files in it) at the same level as wp-config.php. The name of the folder matters, since it will be visible in the URL (bbpress-instance in the above example.)

You should end up with this folder setup when you are done.

wordpress-instance/

----bbpress-instance/

bb-config.php

bb-templates/

----wp-config.php

----wp-content/

plugins/

themes/

Make sense?

[willcrain]

After the first time that I logged into my bbpress account after the install with wordpress I was no longer able to access the wordpress wp-admin page. no login option or anything. whenever i try to login i dont get anything… i can however log into the bbpress admin account

My set-up is as followed:

wordpress-instance

>files with wp instance (ie wp-config.php, index.php, etc)

>[folder] wp-admin

>[folder] wp-content

>[folder] plugins

>[folder] themes

>[folder] myCustomTheme

>[folder] uploads

>[folder] index.php

>[folder] wp-includes

>[folder] bbpress instance

Is this where i would want to put the bbpress instance for installation?

Any help would be very appreciated. Thanks.

[John James Jacoby]

Too much to address, but I’ll pick some points.

WordPress + BuddyPress + W3 Total Cache = less than 10 queries on a complete social network. If optimization is your cup of tea, there’s lots of ways you can achieve that. Core issues with WP should be directed over to those folks.

If you have a method to make it better, submit a patch. Then you can work your way up to being one of ‘those people’ that are making the decisions that you don’t agree with.

Pete’s status, isn’t any different than the way you all feel about things. If you can vent your frustrations, so can he.

Help me understand why we’re upset again.

1. bbPress 1.1 (standalone) – Still in active development

2. bbPress 1.2 (plugin) – Months before anyone should consider it stable, but you’re welcome to jump on the bandwagon early and help make it exactly the way you want it, side by side with Pete and myself, and anyone else that’s along for the ride.

Regarding # 1, what MORE do you want your lightweight standalone software to do? If you want it to be more efficient, spend some time walking through queries and making it that way. If you want something in the UI changed, do it; patch it; make it go, and I will review it, and commit it.

Regarding # 2, our goal is to have this usable ASAP as part of the 3.org initiatives, but I wouldn’t want anyone outside of that initiative using it for production until it’s released. I know we all like to live on the bleeding edge (I’ve always been that guy too) so now’s your time to start helping us weld things in from the very get-go. If you think the way we’ve doing it now is completely wrong, let us know and provide us a better way; I am happy to listen and make it right, because I want what you want; the best bbPress possible.

I think all this talk about Matt, and Automattic, should be redirected back towards Automattic the company, and not bbPress the open source software. I understand the two are perceived to be tightly integrated because mixing money and open source is mixing business with pleasure, and it’s always hard to explain or understand the difference.

I think the general negativism has taken its toll already, and it’s time to try to look at this glass as half full going forward. Please? Kindly?

Not trying to be a jerk here, but man… there is no end in sight here, and it just isn’t productive or helpful anymore. We need to tighten this ship up before it sinks itself. I say this, not from a “looking down” perspective, but from a “‘we’re in this together so let’s make the best of it” perspective.

[Andrew Nacin]

Comparing bbPress frontend queries to Twenty Ten queries is like comparing apples with orange traffic cones.

[zaerl]

In bbPress if you put something between backtick it shows up in fixed-width, not-transformed style.

And, for that matter, why isn’t this site using it?

bbpress.org and bbPress in general uses the backtick notation. It’s hard to remove it. I have answered to a topic some times ago showing a little hack to erase it.

So, is there a way to turn it on?

<?php

/*

Plugin Name: I love strike-through

Plugin URI: http://www.bbpress.org

Description: <s> tag

Author: zeal

Author URI: http://www.zaerl.com

Version: trunk

*/



function strike_it($tags)

{

$tags['s'] = array();

return $tags;

}



add_filter('bb_allowed_tags', 'strike_it');



?>

[namelesshorseman]

I’m having a similar problem. I’ve turned off all rewriting that I could find to no avail. This happens to me as well the very first time I log in after setting things up, no changes to admin or anything.

My install is two folders down /tomek/forums.

Interestingly, I tried in another browser, going to /bb-admin/index.php manually. This redirected me to the login page as expected. I logged in, and bbPress forwards me to /tomek/forums/tomek/forums/bb-admin/index.php. This, obviously doesn’t exist, and would seem to indicate a trailing or starting slash is missing somewhere, but it can’t be a redirect problem — I’ve turned all those off.

Any idea where to start looking?

Thanks,

Tomek

[Joe Gibson]

Z –

“It doesn’t understand strikethrough cause that tag (the obsolete ‘s’) isn’t enabled by default on bbPress.”

So, is there a way to turn it on?

And I understood that the ‘Code’ button was for generating backticks, but what are backticks used for since the buttons cover pretty much everything?

And, for that matter, why isn’t this site using it?

Thanks,

Joe

[chrishajer]

The function itself adds the dashes and removes the blacklisted characters (or maybe allows only whitelisted characters).

http://phpxref.ftwr.co.uk/bbpress/nav.html?bb-includes/functions.bb-formatting.php.source.html#239

[Aaron Jorbin]

JJJ and Pete: Congrats and best of luck on the project. I’ll lend any support and help I am able to. I am excited and looking forward to this plugin.

_CK_ I’d really like to know why you think this is an auttomatic decision? Neither Pete nor JJJ work for Automattic. As far as WordPress goes, multiple lead developers/committers are non Automattic employees. WordPress is a Meritocracy. The more you contribute, the more you demonstrate an understanding of the philosophy, the more responsibility and influence that you have. If you find your opinions are being ignored, I suggest trying to influence those that have contributed diplomatically or contributing patches.

[doobadabba]

I’m excited to hear that bbPress as a WordPress plugin is getting spirited attention and development!

I can also feel for all the contributors to current and past iterations of bbPress, who may have felt left in the dark, or unappreciated. Well, I appreciate you!

I’ve got a little niche community site right now. The site has a blog, and a classifieds section, and a bbPress forum. I’ve got integrated login working, but would love to have even more integration between bbPress and WordPress (especially shared header and footer, and it would be good to have just a single “profile” associated with members of my site).

As digging into code is not my most favorite thing, I’m hoping that bbPress-as-WP-plugin can simplify all of my WordPress projects.

I’m aware that some people may want to keep a standalone bbPress project going, even if only the maintenance of current and former iterations of bbPress.

And I can see that using the same name “bbPress” for both the upcoming bbPress-as-WP-plugin, and the current-and-former-standalone-bbPress-iterations that may be continually maintained, is potentially a source of confusion.

But, I don’t think it has to be confusing.

If a central location, such as this website, clearly presents and describes the differences between using the upcoming bbPress-as-WP-plugin and current-and-former-standalone-bbPress-iterations, then I think people will be able to decide what is best for them.

If I understand correctly, Matt was the original coder (and I’m guessing namer) of bbPress. And it seems that he is the top caller of shots for how bbPress goes forward. As such, I don’t think he should need to rename bbPress-as-WP-plugin to anything other than bbPress, even tho so many other people have been making bbPress what it is today.

But if he did rename it to something like pbPress (plugin-board-press), it might simplify things. How about ccPress (community-creation-press)?

That’s my though-gasm in this moment anyway. Thanks to all of you who have gotten bbPress to where it is today, and to all of you who are moving bbPress forward, and also to all who are mindful of moving forward in a fashion that is not unduly regressive

[chrishajer]

If you can install via subversion, you can have it now. If you cannot install via subversion and are waiting for a packaged version, you will have to talk to those in charge.

Recent discussion here:

https://bbpress.org/forums/topic/bbpress-plugin-is-born

Look for replies by John James Jacoby about releasing 1.0.3 or 1.1

[chrishajer]

Thanks for posting that Josh

[Josh Stauffer]

I found several posts about converting SMF to bbPress. Since I just got done with the conversion and it is still fresh on my mind, I figured I would share my notes on the process.

To convert SMF to bbPress, I had to:

-Convert SMF 1.1.11 to phpBB3 (3.0.7)

-Convert phpBB3 (3.0.7) to bbPress 1.0.2

I had SMF setup on a subdomain: forums.mysite.com

• I created a NEW database separate from the SMF database.
• In the root of forums.mysite.com, I created two directories “bbpress” and “phpbb”.
• I uploaded the uncompressed files of phpBB3 to the “phpbb” directory.
• I uploaded the SMF 1.1.x to phpBB3 converter script. It can be found here: http://www.phpbb.com/customise/db/converter/smf_1.1.x_to_phpbb3/
• When you install phpBB3, I installed it using the NEW database that I created. I followed the “phpBB Convert How To” guide which can be found here: http://www.phpbb.com/community/viewtopic.php?f=65&t=1213555
• At this point, your SMF forum should now be converted to phpBB3.

• Next, I uploaded the uncompressed files of bbPress to the “bbpress” directory and installed bbPress using the same NEW database as phpBB3.
• I used the phpbb3-to-bbpress1-converter which is hosted on Google Code. The script is super easy to install and comes with instructions. It can be found here: http://code.google.com/p/phpbb3-to-bbpress1-converter/
• Optional: I logged into phpMyAdmin and deleted the tables prefixed with phpbb_ in the NEW database.
• Success. It is finished.

Honestly, after reading all the posts out there this whole process seemed rather daunting. Let me assure you that it is easier than it sounds.

Thanks to everyone’s notes that got me on my way and to the awesome folks out there that took the time to write these scripts to make it even possible.

[citizenkeith]

I would just like to say that I am happy that JJJ and Pete have stopped in to keep us informed. This is great news.

That said, I’d like to say that I really, really appreciate Kevin’s posts here. He is speaking for a lot of people, whether he knows it or not. He does a great job of summing up a lot of the feelings us long-time bbPress users are feeling right now.

I am really perplexed by some of the actions and statements by Matt, and now Pete’s Twitter post. Maybe it’s because I’m not a coder and have never been involved with an open source project. But it seems strange that you’d allow a few passionate people with questions annoy you so much. Instead of wanting to give up on it, why not engage with us a little more? Why not ask a moderator to make a Sticky announcement? Why not write a blog post announcing the new bbPress plugin?

I repeat: I think the bbPress plugin is a great idea. I just feel we haven’t been kept in the loop very well.

[_ck_]

If someone wants to start a “positive only” bbPress as WP plugin topic, I promise not to post in there.

People have the right to be blindly optimistic, regardless if there were not one but two different versions of bbPress that were never finished. I mean it should be different by the third time around right?

Seriously: I’d suggest starting with outlining how the Automattic version of the plugin is going to be different/better than the two other existing WP forum plugins, what audience it’s going to address, what it definitely will and definitely won’t do.

I’ve been around since WP 1.5 and when bbPress 0.80 was released, so it’s extremely easy for me to be jaded.

This is an opportunity to get in on the ground floor by watching changes carefully here and reading every line of code submitted since it’s starting from scratch:

https://trac.bbpress.org/browser/branches/plugin

[Josh Stauffer]

I know this topic was started 1 year ago but I thought I’d share my success story.

To start, I just want to note that I have the Permalink type set to Numeric.

First, in the Admin section, I went to Settings > General and changed the bbPress address (URL) from http://www.mysite.com/bbpress/ to http://www.mysite.com/forums/

Next, I renamed the directory /bbpress/ to /forums/ in my hosting account.

Finally, I opened up the .htaccess file in the root of bbPress and did a find a replace. I replaced “bbpress” with “forums” without the quotes. Saved it and reloaded the site.

Worked like a charm (for me)!

[kevinjohngallagher]

Gautam,

You’re words are astute as always.

1.1 is stable, and looking good

I doubt there’s one person involved with bbPress that isn’t looking forward to it’s alpha release so we can get some bug fixes, and then truly thank you and everyone else who added code to it.

Even the people still using 0.9 know and apprecaite how much works goes into it

And about making a living, it can also be done with bbPress as a WP plugin

Yes mate, no doubt.

But we’ve hit this scenario: http://www.dilbert.com/fast/2003-10-12/

The forum topic is this one and the announcement is here (I know no one told any of us about this blog).

You nailed the issue mate.

You and I, and those of us interested in WP development picked up on it. Those who use bbP as standalone, who are those most affected, won’t have. Hence, some of the backlash.

This could all be really positive, in an odd way I think the underlying desire for info is positive JJJ being here is positive Seeing old names and faces pop up is positive I’m confident if 10 of us were in a room right now, this would all be sorted and we’d be coding up a storm It just needs a controlled conversation, some community interfacing and ofcourse, no-one bitching about bbPress on twitter.

[Rich Pedley]

I doubt it is a plugin myself. I suffered from these a long time ago, but hadn’t made any changes to the site for a while at that time.

some of these may be worth a look:

this forum has some interesting comments about it.

What is a core file

WordPress and core dumps

WP tavern

[Gautam Gupta]

Kevin my friend,

For those of us who make a living with bbPress, unilateral decisions made without visibility and with no re-course for questioning nor appeal are scary. really scary.

At least v1.1 is there for the time being, hopefully that would be released soon (after 2 bugs on 1.0.3 and 1.1 are fixed). It’s pretty stable and those who want to run a standalone, can run it and customize it with existing plugins/themes.

And about making a living, it can also be done with bbPress as a WP plugin

I think people are allowed to be a little shell-shocked at this bombshell; especially as it didn’t even warrant its own forum post, sticky or blog post. It just comes across as a footnote and unimportant.

The forum topic is this one and the announcement is here (I know no one told any of us about this blog).

For others – Justin just posted about the WP forum plugin that he has made on his own – http://justintadlock.com/archives/2010/07/16/a-wordpress-forum-plugin-using-custom-post-types

[kevinjohngallagher]

The one change I made to Zaerl Editor was snipping out the part of the code that put that needless “Code” button on the top.

If you’re on a non-US (or i suppose non English/qwerty) keyboard, the backtick key is a total git to hit. there’s quite a large difference between North American keybaords and the rest of the world.

The only disappointment is that it doesn’t seem to understand strikethrough fonts. I tried both “strike” and “del”

bbPress doesn’t process them as standard.

*sorry Zaerl mate, just seen your answer*

[kevinjohngallagher]

Tom,

I totally agree with the premise.

Focussing on the positives is the way forward.

For those of us who make a living with bbPress, unilateral decisions made without visability and with no re-course for questioning nor appeal are scary. really scary.

I for one, am totally and 100% behind the separate forum plugin for WordPress. But I think it’s ok that we ask some questions about it, and while the thread’s not in the most positive tone, I don’t think anyone has asked anything from left field, nor said anything antagonistic or derogatory.

It’s not like we’re asking for info that won’t have already been discussed when making the decision about plugin vs. standalone.

There would have been bench tests, user experiences, requirement gather – y’know numbers and paperwork. I know we’re never going to see the full documentation, but I think it’s ok to ask for an overview. Not to pick holes in it, but to feel positive that the decision is a good one, and one that we can get behind/support/make better

=======================================================================

Andrew, Pete and JJJ and I have had a wee email conversation earlier in the week, before (and during) this thread started. There was some truly great info in that thread. Information that would appease some of the issues brought up here, quell some of the language & tone being used. It confirmed to me that these are the people to take bbPress forward. But that doesn’t mean I am going to put my own and my children’s livelyhood on the line and follow blindly.

everything is going to be A-okay

is alot like

Relax. We’ve done this before.

And man, that didn’t work out too well

I think people are allowed to be a little shellshocked at this bombshell; especially as it didn’t even warrant it’s own forum post, sticky or blog post. It just comes across as a footnote and unimportant. It comes across as “shit, you folks found out? um…” Now of course that ain’t true, but thats the base perception.

Apparently the scrapping of all current bbPress code and new of it’s replacement isn’t even important enough for someone to hit that “sticky” button at the bottom.

Because of this, some emotions will run high, but we’ve both been around the block enough to know that as long as people keep the conversation in house and try to resolve things then we’ll get there

Not everyone will agree with everything, but we’ll get there as long as no-one makes any derogatory comments about the software or community in a KeyNote speech or on an influential Twitter feed we’ll be grand at resolving this, and bringing folks tegether in a positive sense

The dudes who are now running the show just need to give out enough info to get control of the conversation. Once that happens, even more of life will be positive.