[Peter Westwood]

It will probably also suffer from what I call the “kitchen sink” syndrome of WordPress where massive chunks of code are added as features which should have been plugins. But Automattic in general has a “not invented here” attitude towards plugins – if it’s not in the core, it doesn’t count.

Firstly, 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.

Secondly, I strongly disagree with the implication that WordPress has a “kitchen sink” feature set – in fact we try very hard to only bring in the things which have a wide audience and leave the more niche things for plugins.

One of the factors which helps a feature come into the core is the existence of a plugin which is popular showing a clear demand for a feature and sometimes providing a starting point for the implementation as well.

[pagal]

Support Ticket Sent!

[Rich Pedley]

It’s a hosting issue. You should be ok to delete them, but I’d recommend talking to your host first.

[pagal]

I’ve same issue, I think its not a hosting problem, I did not contact my host yet (Soon I’ll be ). My hosting is shared, I’ve added my 6 domains in it. My other 5 domains are clear, but which domain I’ve uploaded bbpress it have

core.10523

core.10566

core.10576

core.27790

core.26889

that’s amazing, and confusing :-s

[mr_pelle]

Now available for download.

[_ck_]

@gswaim, except history is about to be repeated with nothing learned. “Very near” is also not likely this year. Completely different people worked on 0.9/1.0 and now the plugin version. There is going to be a learning curve.

The plugin version is going to have the same tumultuous development pattern that bbPress 0.7, 0.8, 0.9, 1.0 did and probably take a couple years to get stable and feature rich. It will probably also suffer from what I call the “kitchen sink” syndrome of WordPress where massive chunks of code are added as features which should have been plugins. But Automattic in general has a “not invented here” attitude towards plugins – if it’s not in the core, it doesn’t count.

There is also the problem that anyone on a shared host will unlikely be able to run WP 3.0 with the bbPress plugin unless they have a very small forum/memberbase. The resource demand is going to be massive and require hours of fine tuning which most novices will not be able to do. Forums cannot be heavily cached like blogs can.

Then you are right back to the same old WP problems which will be introduced into bbpress after avoiding them previously, plopping regular users into confusing WP admin menus to change settings and completely different than the site theme.

For the casual WP user that has a few dozen members and wants a simple forum, the bbpress as plugin will be very handy. For those with thousands of members and end up with a very active forum, they will spend a great deal of time dealing with the resource loads.

Remember, there are already a couple of plugins for WordPress that bring forum functionality – go look at their problems to foresee what is going to happen. That’s how I ended up adopting bbPress standalone in the first place, I decided it was the best way to deal with the problems (work AROUND wordpress, instead of through it).

[_ck_]

bbPress 0.9 downloads: 149095

bbPress 1.0 downloads: 106462

_ck_ plugin downloads: 93179

(but I think the plugin download counter was broken after bbpress.org 2.0)

[kevinjohngallagher]

It’s definately not from bbPress mate, and doesn’t sound good at all.

I’d delete or quarentine it asap, and maybe contact your host too.

Kev

[Earthman Media]

I just found a huge file “core” (no extension) in my bbpress root folder…

it is a binary file which has a lot of unreadable characters, interspersed with segments of code from bbpress and what appears to be log entries…

Is this supposed to be there, or is this some kind of viral invasion.

any advice would be most appreciated, before I delete it.

Thanks!

[Techpad1]

Hi! I’m a brand new bbpress user, and looking forward to getting better acquainted with all of you. However I do have an immediate issue on which I could use some advice.

I’ve made a conversion from vbulletin 3, via phpbb3, to bbpress 1.0.2. In the process, none of the slugs for the forums or topics fields were populated. Would any of you have a nice solution for that handy?

I’ve put this in the Installation topic, because bbpress isn’t broke. I believe this is more likely an artifact from the conversion. Please feel free to correct me if I’m wrong.

Regards,

Dan White

[gswaim]

At the end of the day it’s free, open source software. Polarized or not, bbPress has a team now. If this can just be summed up as a years worth of pent up frustration coming out, I can understand that, but we’ve all been going at this for almost 3 days now, and I’d rather write code and fix stuff and make progress than rehash bbPress’s tumultuous existence.

Exactly. There comes a time when it is time to move on. IMHO that time is very near.

JJJ has patiently articulated, to this group, the mission he was commissioned to handle and IMHO it is time to code. As I watched this thread, I feared that he would get bogged down and burnt out trying to make everybody happy. However, he seems to be keenly aware of this and has done a good job of keeping his eye on the prize.

I am a WordPress user that has been waiting for a core forum plug-in for well over a year. As soon as it is available I am installing it, and I suspect I will not be alone.

If only 10% of the WordPress.org-powered websites install this plug-in, the bbPress plug-in user base would dwarf the stand alone bbPress user base. Making bbPress available to a much larger audience cannot be a bad thing, in the long run.

[John James Jacoby]

Looking back through a lot of this discussion, I can see how some of my posts in here sound a little crass; and that isn’t my intention or goal.

So, let me apologize to each of you for that, if it came across that way.

My intentions with bbPress are to be helpful, provide guidance, be a sounding board, commit patches, and make the bbPress plugin something everyone here can be proud to use.

I don’t want anyone to fork anything; to feel left out, pushed out, forced out, any of that stuff. I very badly want everyone to feel comfort that we’re putting bodies and eyes on something that’s needed it for a long while, even if it isn’t exactly the way everyone agrees it should be.

You all have my word that I’ll be combing the trac, and helping things around and about as much as I can. My concentration is on bbPress the plugin, and BuddyPress, but any place else I can spread some bandwidth, I’m glad to do it. If anyone else wants to help out, I’m happy to have you aboard.

Pete Mall stepped up right away to help several months ago when this idea first cropped up in IRC and at a few WordCamps, so naturally he’s on board. The existing committers aren’t going anywhere, and everything is going to be A-okay.

[kevinjohngallagher]

Peter,

I sincerely apologise for the paraphrasing.

I didn’t mean to misrepresent what you’d said in anyway.

[Peter Westwood]

Westi didn’t comment on it in my email to him, though he did say that he didn’t know that bbPress was dependant on BackPress – and he’s the BackPress lead!! really lovely guy, but it hardly bodes well.

That isn’t a fair representation of what I said in reply to the email which was:

I was unaware that BackPress was blocking bbPress release this is the first I have heard of it.

Which is perfectly true – no one had tried to contact me directly about it before you.

I was and still am surprised that a point release of bbPress would be running with a floating external as trunk of BackPress is never guaranteed to be perfect code.

I would actually expect it to be run against the last revision that bbPress was release / against a branch with specific fixes as required.

If anyone want to be sure to get my attention for a BackPress issue then the extremely quite BackPress-dev mailing list is the best way – I read every email to that list promptly – https://lists.wordpress.org/mailman/listinfo/backpress-dev

[Anonymous User]

Hi John JJ,

thanks for your long statements here. For me – it’s great to hear about the future von bbPress. And even greater – bbPress has a team now!

Yeahhh…

[John James Jacoby]

All this has been said, and answered before. I just downloaded 2 plugins from the repo, and they worked fine enough. I am also of the opinion that this iteration of bbPress.org is the best looking and working one so far.

In Matt’s defense, I haven’t seen anything that Matt said qualify as berating, and the people he disagrees with, are people already on a verbal or moral offensive. Having been able to see through both sides of that looking glass, I can tell you with first hand experience that Matt is almost always on his A game, even if you don’t understand it at the time. But, this isn’t something I really want to get into because it just isn’t classy to do.

I get that everyone wants to hear from Matt and/or Jane. It sounds to me like you really want an apology more than you want anything else, because you’ve answered your own questions about how gaps in development have been filled in.

At the end of the day it’s free, open source software. Polarized or not, bbPress has a team now. If this can just be summed up as a years worth of pent up frustration coming out, I can understand that, but we’ve all been going at this for almost 3 days now, and I’d rather write code and fix stuff and make progress than rehash bbPress’s tumultuous existence.

P.S. – BuddyPress uses bbPress internally, so I’ve lurked for the past year+ and paid attention to the goings on. I just didn’t have the time or energy to have these discussions then. Now, I do, but there’s not much more I can say; it comes down to what we do about it. Like it or not, this is the hand we’ve been dealt… Time to make the best of it.

[Milan Dinić]

There are some improvements that are made to this feature that will solve some opinions expressed here. Read my detailed post for more information.

[Milan Dinić]

chrishajer just committed patches that improve subscription feature. Now we have a lot of new features:

• option to disable/enable subscription in Options>Discussion
• function for changing subscription status for user on topic (which means it could be used in plugins/themes
• function for retrieving subscription status of user for topic
• checkbox below post form for change of subscription status
• links for subscription are now added to topicmeta action so on most if not all themes it will be shown without need for theme edit
• a lot of filters/actions so you can remove features, change text etc
• everything is well documented

What this means is that now users don’t need to receive emails for every post since there are hooks in function that sends emails. Developers could make new features like sending digest email, one notification until user visits topic, page with list of subscribed topics for user. option to auto subscribe user to particular forum/tag (useful for plugin developers etc) and other.

What you can also expect is that today or tomorrow you’ll again have option to subscribe to topics on this forum.

Thanks to Gautam for a lot of improvements to my patch(es) and to Chris who committed final one.

[Milan Dinić]

If anyone reads this, link to download page from blog is broken.

[Gautam Gupta]

The disorder of posts on profile page is related to #1301

[mr_pelle]

It’s probably related to this: https://trac.bbpress.org/ticket/1310

[chrishajer]

That has been like that for a while.

https://bbpress.org/forums/topic/all-member-names-anonymous-on-front-page-bbpressorg#post-70653

[kevinjohngallagher]

Homepage is broken again.

Says everyone is Anonymous.

[chrishajer]

Rescued from Akismet. I don’t think it’s a spammer…

[chrishajer]

Rescued this post from Akismet