[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.

[_ck_]

By the way I want to address this quote:

…it’s not “Automattic” that decides what ends up in the core of WordPress – we have open discussions to set the feature lists for each release and the decisions are driven based on input from a large base of regular contributors.

You are kidding yourself if you think the community is given anything but choices on minor things. Major decisions that change the entire direction of these projects for Automattic are made every year by Matt. Changing bbPress to use backPress is the #-1 example of a single sourced decision done without any input from any contributors. bbPress as a WordPress plugin is another one.

The very first simple question I asked when I heard about backPress is “when will WordPress be changed to also use backPress” (to benefit from all the work needed and the theoretical savings from using a common function set). It’s a very easy problem to predict but was never asked and never answered, ending us up exactly where we are today.

[zaerl]

I have inserted the “code” button for the simple reason that the backtick character is difficult to be typed on a keyboard that isn’t the “standard” U.S. ASCII. This is true for the vast majority of the keyboard layouts worldwide.

The only disappointment is that it doesn’t seem to understand strikethrough fonts.

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

I provide support for standard tags: strong, em, a, img, ul, ol, li, blockquote, code and the non standard img that is widely used.

My plugin do not enable new tags (and implicitly new buttons) in current version 0.3.2 but it does in 0.4 (trunk). I have taken my position regarding the future of bbPress and so I will not upload new plugins and/or updates (https://bbpress.org/plugins/topic/zaerl-editor/page/2/#post-5992). Anyway if you need the new zaerl Editor with custom buttons and other fancy features write me a couple of lines. za AT zaerl.com

[bobbyh]

Look in your plugins for an extra “space” that is sending output (plugins aren’t supposed to send output). This could also be in one of the files you edited or in one of your plugins.

Here is somebody who experienced the same thing: https://bbpress.org/forums/topic/errors-in-installphp-line-10-and-functionsphp-line-1898#post-12300

[Gautam Gupta]

Can we focus on the positives:

bbPress was laying there dormant – it now has a future. This future isn’t going to suit everyone but that’s life.

Exactly.

[pagal]

my recent wp error log file

http://pastebin.com/raw.php?i=Vw2XbdRb

Please see it and suggest a solution

[deadlyhifi]

Can we focus on the positives:

bbPress was laying there dormant – it now has a future. This future isn’t going to suit everyone but that’s life.

I’m not at all surprised bbPress will become dependant on WordPress. People have wanted an easy to integrate solution for a long time. The majority of support posts on this forum tend to be about integration (if they’re not CSS based!). bbPress as a plugin will satisfy those needs.

Yes, there will be certain users that get burned, but there are ways around it.

People are falling into 3 groups:

1. Need a forum that works with WordPress
2. Need a standalone forum, but some WordPress integration is ideal (sign in/users)
3. Needs a standalone forum.

1. Satisfied customers
2. Satisfied customers – this will be easier than it’s ever been. I know, I’ve spent hours and hours theming bbP, making sure cookies work, and all the other hoops I’ve had to jump through.
3. Either run WP and don’t use it (just let it sit there, but really, how many sites don’t have some kind of blog associated with them?), and if it’s really not ideal or you’re completely against it there are plenty of standalone forum softwares out there.

At least we know what is happening and people can make informed decisions about which way to go with their site.

The decision has been made so accept it and use all this energy and knowledge to contribute to the project and make a great product.

_ck_, you know I always appreciate your efforts towards plugins and your extensive knowledge on bbPress, so why not use it to participate and keep the new bbP plugin streamlined – as much as it can be considering your comments on WP3.0 performance.

[pagal]

Support Ticket Answer,

Core files are generated when one of your scripts fails

I advise to check/update your plugns in order to fix this problem.

You are free to delete them all

Thank you.

---

Kind regards,

Yuri Peters

Just Host

http://www.justhost.com

It’s definately not from bbPress mate

@ Rich Pedley I’m still confuse that which bbpress/wp plugin is creating trouble and generating core files.