[xarzu]

I did everything I thought I should do.. Still, it does not seem that when a blog is made there is an automatic form addition. Isn’t that how this is supposed to work? It seems it is just cookie settings and sharing user ID and passwords

[_ck_]

_ck_… you’d rather let bbPress die than let it be reborn and successful as a plugin?

To clarify, I’d rather see the name “bbPress” be retired than recycle the name for another purpose when there are years of development and history already in existence.

I have no problem with you/automattic/whomever making a new forum program, zero problem with it and I honestly wish you the best.

My problem is calling it “bbPress” when it has virtually nothing to do with the original bbPress project. Even worse, it’s being called bbPress 1.2 which is downright weird. 1.2 implies updates to 1.1 – but this is a complete rewrite into something else.

The only reasons I can conclude why it’s being called bbPress is because Automattic/Matt already owns the name, and y’all can’t think of another name or simply don’t want to bother.

Like I said before, and feel it’s worthy of explaining again: What if the WordPress core was suddenly completely re-invented on a whim, breaking all compatibility, and it was simply called “WordPress 3.1”. Wouldn’t that be really dumbfounding and confusing to the community?

@gswaim – the reason why this topic isn’t being closed, is because this is the most conversation we’ve EVER had about bbPress’s future/politics. Even during the backPress changeover we had nothing really like this, just bits and pieces. Matt would make a decision and we’d hear about it a month later during an interview or speech.

I believe this talk/venting is good and healthy as long as it’s not done by attacking individuals personally.

And I’d rather see it all focused here in this topic than a dozen topics eventually created on the subject, (especially since after all these years we still do not have a topic merge function in the api).

But if you want it closed in the hopes it will end people’s feelings on the subject, that’s not really how people behave/think is it?

[_ck_]

This utility has been delayed a bit as a few things came up this weekend but I fully intend to finish it soon.

Thanks for volunteering citizenkeith, I’ll keep you posted.

[xarzu]

In the FORUM dashboard, I found under settings, “WordPress Integration”

[xarzu]

(continued)

Making a new Blog post does not create a new forum topic. Shouldn’t it?

Creating a new catagory in the Blog does not create a new forum group in the bbpress forum. Shouldn’t it?

It seems that the users are sync’ed. I mean if someone logs on to the blog, their user ID works on the forum.

How do I further link up the Blog and the Forum.

[gswaim]

How about a little wisdom about now… somebody please close this post.

[John James Jacoby]

_ck_… you’d rather let bbPress die than let it be reborn and successful as a plugin?

I didn’t expect that from one of bbPress’s most vocal supporters and longest standing contributing members.

That being said, I very much appreciate your volunteering to continue to maintain the 0.9 branch; I appreciate everyone that’s worked hard on the 1.1 branch; and I very much look forward to the success of the 1.2 branch.

[John James Jacoby]

Again, just too many of the same points to repeat myself, but bbPress standalone isn’t going to be “unsupported”, it just isn’t going to see any additional features, which is exactly what I think most of you want. Correct me if I’m wrong here?

If I wasn’t on my iPad I’d quote myself volunteering personally to commit any bug fixes to the 1.1x branch of code if anything comes up, but again, that went totally unresponded to.

All of the things I’ve offered to do, to help continue the 1.1x branch of standalone code in addition to creating the 1.2 plugin, have gone totally unacknowledged. If you want to be able to do it yourself, you’ll need to have the experience to understand that the code you write is responsible for powering millions of sites around the world, and that you can easily create global chaos with one click of a button. Call me melodramatic, but in environments like WordPress.com, it’s very true. My experience over the past year has had me much more close to that kind of environment, particulalrly with BuddyPress.

A year ago I felt keeping bbPress as a standalone made sense because a year ago I didn’t comprehend what was coming in WordPress, particularly 3.0 where custom post types have made much more possible. I also had less experience with BackPress, and don’t get me wrong; BackPress is awesome, but bbPress won’t reach its full potential until it’s a plugin for 25 million other websites.

Kevinjohn, I’m sorry but you’ve got a knack for twisting words around and quoting things totally out of context. That’s not really fair, and I wouldn’t do it to you or anyone else so I’d appreciate the same.

I don’t get what you all want bbPress to do differently that would even require a new standalone version. I’ve asked that before, and there’s no answer; just frustration.

bbPress has always been an Automattic endorsed project, and considering without Matt it wouldn’t exist, or have a trac, an svn, or core developers thus far, it seems like he’s the one who’s earned the ability to make decisions on the future of the project. If you call me believing that to be true drinking that Kool Aid, I’m happy to do it because I believe Matt and Automattic and bbPress has earned that from me. If Matt wanted to abandon bbPress completely and close up shop, he could, and someone could graciously keep it alive by forking it. None of that stuff, should make anyone this upset.

My employment status or relationship with Automattic aside, I’m happy, blessed, and consider it a great privilege to have the trust of Automattic and the surrounding community to take this on, even if some of you don’t understand why it’s me, or why now, or why a plugin.

Regarding TalkPress, the main reason it’s named differently is to avoid the confusion people have with WordPress.org and WordPress.com. bbPress is the opensource forum software of choice for WordPress users. If any of you want to help the plugin work on top of backpress, patches welcome and I’m open to the idea. Otherwise, I’d wager 60% or more of the support questions regarding bbPress are incorporating it with WordPress. It’s been said in this topic already, but making it a plugin alleviates those issues, and still allows everyone to keep loving bbPress.

In all honesty, all this back and forth is tiring, and all it’s doing is taking the team of people that are here to help keep bbPress alive, and make us the enemy to the people that are just happy to see life again. That, and it’s taken our ability to communicate news to the bbPress community away from us, and instead forced us to try and put out this fire for the past 4 days.

Quite frankly, it all kinda sucks.

I get that the reality (for some of you) of switching bbPress to rely on WordPress instead of BackPress doesn’t sit well or even make sense, but I promise you it does. I might even have a trick that will help make the admin area a little more familiar. But 1.2 isn’t going to use BackPress anymore. Instead it’s going to use WordPress. bbPress itself is getting lighter, and we inherit all the eyes and updates that WordPress has had that BackPress hasn’t. That alone, if you ask me, is more than enough reason to be thankful for this move. If you need it super optimized, we’ll inherit all the caching plugins for WordPress. If you need bells and whistles, we get WP plugins. There is too much to gain, to not have bbPress be a WP plugin.

The existing standalone committers, are doing a great job already. There are very few trac tickets to work through in terms of bug fixes, and most of the enhancements would naturally get fixed by making it a plugin.

So… I want to say again, your passion and enthusiasm is something I want, and appreciate. If any of you are going to WordCamp Savannah, I’ll gladly discuss this over drinks and dinner. Whatever you need, I want to make it happen for you, but the name isn’t changing, Myself and the team are going to support the standalone with security updates as needed. Since I have commit access, I’m happy to commit fixes as needed because I’ve been trusted with that ability and I want everyone happy with a safe and functional piece of software, plugin or standalone.

I also, typed this out entirely on my iPad over the course of an hours worth of “leisure time.” if that doesn’t say you have my attention and commitment, I dunno what does.

[chrishajer]

Wait – if you are NOT logged in, can you get to wp-admin and log in? Maybe it’s just a cookie issue.

Are you logging in with bbPress or WordPress? And did you integrated the two some how? At this point, I think it’s got to do with the login cookies. Try a different browser and see if you can log in to wp-admin first, without trying to log in to bbPress.

[chrishajer]

If you cannot access the WordPress admin, even without bbPress installed, then some other change is making your WordPress admin inaccessible. Did you modify wp-config.php in any way? Can you access your WordPress site without getting a white screen?

If you have access to logs on your server, you can find out what Internal Server Error (500) is causing the white screen.

To uninstall, you just need to remove the folder and drop the tables in the database. But with the folder removed, I don’t think your white screen has anything to do with bbPress at all. Unless you modified wp-config.php or any of your template files to incorporate bbPress.

Did you make any changes other than installing bbPress, at or around the same time?

Sounds like you have it installed in the correct place, according to the layout you posted here.

[citizenkeith]

I’d love to help out. I’m capable of backing up my database and restoring it. :

[_ck_]

This will probably be low on the priority list but tags are no longer being imported from the readme.txt in the plugin section, so any updated plugin since the bbpress.org 2.0 upgrade has lost it’s tags.

[zaerl]

The micro-plugin (I have written for you) activate the s HTML tag (as you requested) <s>your text here</s> but zaerl Editor 0.3.2 does handle only standard tags plus the img tag as I said here: https://bbpress.org/forums/topic/latest-on-better-editor#post-71194

[johnhiler]

The “Edit Post Attributes” plugin lets you edit timestamps and even usernames!

https://bbpress.org/plugins/topic/edit-post-attributes/

I use it on several sites and haven’t had an issue with it yet… highly recommended.

[john010117]

My two cents (if it’s worth anything): Keep bbPress 1.1 and continue to maintain it. However, get a new dedicated group of developers to actively code and maintain a wordpress forum plugin (named differently like talkpress for example). And on both website’s front pages, specifically list the differences between bbPress and “talkPress” so people won’t get confused.

[_ck_]

Once properly configured and running, administrators can get easy access to the log by just adding ?browsertimer to the forum url.

The view right now is very basic and looks like this:

https://bbpress.org/plugins/topic/browser-timer/screenshots/screenshot-1.png

I’ve done some fancy parsing of the user-agent to attempt to strip it down to the useful bits. (in the example the IP addresses are partially obscured for visitor privacy)

[johnhiler]

I completely support Automattic’s investment in a new WordPress forum plugin!

That said, I think it would avoid a lot of confusion if it were named something else besides “bbPress”.

[Joe Gibson]

Z –

I copied the code to a PHP file and it activated from the bbPress ‘Plugins’ panel, but I can’t figure out how to make it work in the editor. I tried both angled brackets and backticks. Thoughts?

And the next big challenge would be to have it open links in a new window. Is that possible?

Thanks,

Joe

[_ck_]

This is a very early beta release for advanced users who may find it useful.

http://bbpress.org/plugins/topic/browser-timer/

(works in 0.9 and 1.x)

example log:

http://bbpress.org/plugins/topic/browser-timer/screenshots/screenshot-1.png

While my bb-benchmark plugin will tell you how long it’s taking your server to make pages, you really have no idea how long it’s taking your users to browse your forums and see those pages.

ie. 200ms on the server side may be 5 seconds with javascript on the visitors side

You can time your own browser, but often you have many things already cached and might use a faster browser or live much closer to your server than someone else across the country or the other side of the world.

So now you can know exactly how long it’s taking for them to see your pages.

It’s very accurate in my testing, within 100ms typically.

Basically it works by using a sort of “round trip” timer.

You can add a geo-location database and it will tell you what country the visitor is in, which helps to understand why a time may be so high/low.

[kevinjohngallagher]

Yutt,

Like everyone else, you’re entitled to your opinion; and i am truly sorry if i’ve left you with an overly negative one – though I apprecaite I am a tad less forgiving of people who can’t even get my name right

[_ck_]

Well actually I am typically fairly quiet about the back end stuff and community politics.

But I’ve regretted over the past year or two not voicing enough concern at the start over backPress so now I simply do not want to see another big mistake, the bbPress name hijacked for a third, completely different forum program.

My request is quite simple: do whatever else you’d like but please do not call it bbPress when it has no relationship with any previous version of bbPress.

If bbPress truly is an open source community project and not exclusively owned/managed by Automattic, well then here’s the chance to prove that.

If Matt suddenly announced that WordPress would radically change from 3.0 to 3.1 and out of the blue use a newly developed core that completely invalidated all existing themes, plugins, utilities and knowledgebase – wouldn’t you be just a little bit concerned and upset? Would you speak up or “go with the flow” ?

In the above scenario, if you were new to WP 3.1, you wouldn’t care and would wonder why people were complaining so much. But if you had a few years invested, maybe you’d feel a little differently. Maybe you’d ask them to leave the old version alone and call it something else.

[yutt]

Just so the new developers understand, trying to have a discussion with kevinjohngallagher or _ck_ about the future of bbpress is an exercise in futility.

They are extremely vocal and belligerent members who have dictated the tone of the community for over a year. kevin smiles while talking over you, but it isn’t any less damaging.

Frankly if this site is moved to an alternate subdomain and they disappear completely, *that alone* would improve the bbpress experience.

Thank you for keeping us informed on the progress and your intents. Please focus on coding and not community management on this point. The only “community” here are a dozen diehard, entrenched and bitter people who have been too stubborn to adjust their vision over the year we have known this change was coming.

[_ck_]

I should have a database downgrade tool finished by the end of this weekend.

I need a few testers who know what they are doing and can backup their database (and restore it) if something goes wrong.

Technically you’d have to clone the database anyway since you’d want to install bbPress 0.9 into another directory, at least for testing purposes. But that requires you to override some settings via bb-config.php to tell it where everything is, or re-run the install routine for 0.9

Obviously this does not do anything magical to your plugins, they have to be backwards compatible with 0.9 also (if you are using mine in 1.x successfully, they will work in 0.9 but I can’t speak for others).

[_ck_]

By the way, Matt owns talkPress.org and it’s not being used.

So there’s a solution. With a new name, it’s clearly a different product and there are no expectations and no conflict.

I’d promise not to join or comment on it in any way and you can start with fresh faces ignorant of any legacy baggage.

[willcrain]

sorry about that. I did have it set up like that. (my spaces didnt show up in the post)

wordpress-instance ( http://www.examplesite.com )

---

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

---

>[folder] wp-admin/

---

>[folder] wp-content/

---

>[folder] plugins/

---

>[folder] themes/

---

>[folder] myCustomTheme/

---

>[folder] index.php

---

>[folder] wp-includes

---

>[folder] bbpress instance (which i call ‘discussion-center’)

in this case in order to access my bbpress site i use:

http://www.examplesite.com/discussion-center

and that works, i can see it all and interact with both…but, once logged in however i can not access the wordpress admin panel, http://www.examplesite.com/wp-admin … just a white page… as well as http://www.exaplesite.com/wp-login.php… even if i remove the [folder] bbpress instance from my wordpress instance it still doesnt offer access for wordpress… i would try uninstalling it and reinstalling it but what else would i have to remove other than the instance folder?

thanks again for any help