[kevinjohngallagher]

Anybody? Nobody?

venividi,

you give us less than 24 hours to answer.

WordPress3.0’s been out for about 2-3 days, and you’re talking about something not working that has never been supported.

Automattic made no effort to make sure things were cool with bbPress before releasing so we’re all going to have to wait until we get more reports in.

Lets not forget that a large number of people wait until the first (if not second) bug fix release is made availible before chaning over.

Patience is needed my friend, just don’t push untested just release software onto a live enviroment and you’ll be fine – and we know you didn’t do that because that would be so silly ;-]

[venividi]

Anybody? Nobody?

The problem made me a strong headache for a long time.

Please ~

[kevinjohngallagher]

I get the idea that bbpress isn’t being actively worked

Nope, it is

…and that this Mat individual wants to abandon this project

Nope. Matt wants to convert it to a WordPress plugin.

Is this the person who made wordpress really great?

He’s one of the 500+ people that have contributed to WordPress.

Is this a good reason not to continue using bbpress? Is bbpress going to die out if Mat doesn’t work on it?

If bbPress works for you, then use it

If it doesn’t, then don’t.

bbpress is open source software, it’s not going to die. As long as you’re ok with a minimum year between releases, and a project lead who refuses to answer any questions or pass on any information (and most people are) then you’re fine with bbpress.

[pagal]

@ johnhiler also please read this post…and reply there…thanks

https://bbpress.org/forums/topic/extra-dropdown-field-in-registration-page#post-70052

[shsn]

I’m new at bbpress and don’t know much about php. I can edit stuff, but I can’t really come up with anything on my own.

I’m editing another theme for bbpress and changing it to my own theme. Somehow or another there is no log out link. I need to know what that is. For logging in it is this :

‘<?php login_form(); ?>’

what do I put for logging in. I have a sidebar file and I want to put it there, so that when members are logged in, they can click on logout.

thank you in advance

[Gautam Gupta]

We’re trying to get 1.1 release out, can’t say much about it. There are only 7 tickets pending.

[shsn]

I wanted to use bbpress because I thought it was really simple to use and it was easy to integrate with wordpress. I’ve been looking at some posts recently and I get the idea that bbpress isn’t being actively worked on and that this Mat individual wants to abandon this project (?)

Is this the person who made wordpress really great?

Is this a good reason not to continue using bbpress? Is bbpress going to die out if Mat doesn’t work on it?

i understand these may be silly questions, but I am not trying to make a joke of things

[saare2000]

sorry about that. basically what i’d like to achieve is “two forums in one page”.

here’s a simple scetch – http://cl.ly/5be25a250d64ba791405

forum has 2 categories/subforums. and when I come to main page I see both of them in two separate columns. left one is for ‘forum 1’ and right column for ‘forum 2’. something like 2 bbpress installations next to each other.

hope my question is now more clear

thanks!

[chrishajer]

Deep integration is when you include wp-load.php in your bb-config.php, so that you have access to WordPress functions (like get_sidebar(), get_header()) in bbPress. It’s not recommended, and it’s not an official bbPress term by any means. There are just several different types of integration and calling this one “deep” helps keep things straight.

[chrishajer]

There’s no such thing as bbPress 2. There is a new theme here which some people are calling bbpress.org 2 or bborg 2.

This site is running the 1.1-alpha trunk branch, not sure of the revision. It hasn’t been updated in a couple weeks.

[shsn]

Is this support forum using bbpress 2?

[johnhiler]

I’ve done something very similar using separate (but user integrated) installs of WordPress and bbPress.

Here’s the blog:

http://www.weddingbee.com/

Here are the boards:

http://boards.weddingbee.com/

And here is a support forum:

http://support.weddingbee.com/

You don’t need to add an extra column to restrict support access – you can use Roles and “Hidden Forums” to pull that off.

https://bbpress.org/plugins/topic/hidden-forums/

I’m actually using 7 separate bbPress installs for that site, along with two WordPress installs and some custom code. Just follow the instructions on integrating users between WordPress and bbPress, and wash and repeat for each additional bbPress install.

Good luck!

[NumberKruncher]

I am designing a website which will utilize WordPress for a blog and bbPress for its forums (both linked). I would also like to run ticket-based support using bbPress. My first thought was to create a custom theme for bbPress which would achieve this but I do not know if this would be possible.

Requirements:

– Website structure would need to be as follows:

/blog/

/forums/

/support/

– All three of these would share the same users.

– Ideally an additional column would be required in the user database to specify if a user is allowed to open a support ticket (limited to customers).

Can this be achieved with one single installation of “bbPress”? I was thinking about giving all forums a parent forum “Forums” and all support forums “Tickets”, and then somehow mounting one to “/forums/” and the other to “/support/”.

If not, how would I go about doing this?

Kind regards,

Lea Hayes

[kevinjohngallagher]

Gautam,

This won’t be a short post, but I truly wish for you to know this comes from a place of respect and admiration for both your code and your commitment to bbPress and it’s community.

Please, let us focus on what we need to get the next release finished.

We simply cannot fix everything.

We have to prioritise.

Matt, who is the project lead, did the prioritising for us.

• Critical Bug fixes
• Email notifications
• Anonymous posting.

That’s it. Once those are ready, we release.

Matt himself said that the focus should not be on bugs, but on the 2 new features and critical only bugs.

It’s not for me to tell you, nor even ask, what you should be working on; but please allow me to help you. As a developer, and someone who loves this project, you are trying your best to solve as many problems as possible. It is so admirable, and we all appreciate your efforts. But in the long run, you are only going to slow us down. How?

Bugs.

When a developer writes code, especially large pieces of code, there are bugs. It is the nature of the beast. We have very very few testers, very very few people who download the latest trunk version to test. The chances of us catching anything but the most obvious of bugs are slim.

Take the new default Kakumei theme you’ve included. While I’m in total agreement that the default theme needs changing, this is not the way forward. You’ve changed about 400 lines of code, and there will be bugs. Given that a new Kakumei theme isn’t part of the feature list, those bugs are going to count against us, not be a positive.

You’re giving theme developers slighty more tools to work with, but all you’re giving the average user and the new users is an untested theme that looks like the old one (which looks crap still).

Regardless of how awesome your code is, and it looks brilliant, the best we can hope for with it is that it doesn’t go badly. If it works flawlessly, no-one will notice. There is no winning scenario here. No part of releasing a new theme in 1.1 will be beneficial, especially as it looks identical to the old one.

Sadly the same can be said for your efforts to totally rewrite the entire tag system. I’ve absolutely no doubt, 100%, that your code and functionality would be amazing. But right now, it works. Same for your Mass Delete / User handling functionality. etc etc

There comes a time when Less is More.

Less code changes means less new bugs, means less “OMG it’s taken a year to come out and it’s still terrible” posts. Less code means less to test, it might mean more bugs are caught, it means less bugs released. Less code means we can release quicker. Less code means less testing time.

Realistically, we have only 2 bugs in 1.0.3 ( #1228, #1276 ) and 2 bugs in 1.1 ( #1244, #1268 ) that are stopping us from releasing this thing to alpha for testing. Thats great work, even if #1244 looks like it will be a lot of work.

The other bugs (#538, #1183, #1277, #1243 ) are all “nice to haves”, and yet somehow contain about 800-1000 lines of code with changes. There has to be some form of Risk Assesment here bro. 1000 lines of code changed with no functionality to forum users, but instead increases the chances of bugs?? Risky, very risky.

Look, BackPress might never include the fix we need to get this thing working, so lets focus on the outstanding bugs that are blocking us, and lets worry about the others after. Because lets be honest, if we’re building a new theme for bbPress, it’s should look nothing like KAKumei (emphasis on KAK)

[Taeo]

Its amazing that only four people are behind WordPress, plus some new ones now. To me, it seems like WordPress is a company on the level of Apple. I imagined there would be hundreds of employes behind WordPress. They really give the impression of being the most professional people in the business of cloud-computing.

Welcome to open source software development Marius

What you are saying is *sort of* true. There have only been 4 main code “committers” in recent years but there are actually a lot more people involved in making WordPress what it is.

WordPress is “owned” by a company called Automattic. Everything they produce is open source and therefore free to use and/or modify. It’s not a huge company but it’s not tiny either. They are comprised of 40+ developers, designers, engineers, etc who all work from their homes spread around the globe. They make their money mostly from WordPress.com which sells WordPress hosting as a service.

The beauty of it, since it’s all open source, if you decided you wanted to become a developer and you came up with a great idea for a new feature and coded it up as a plugin – Automattic might decide that they want to incorporate it as a core feature and implement YOUR code. This is exactly how the new menu feature in 3.0 came about. People had been making plugins that worked in a similar fashion for years.

[Marius-]

Aw Kevin dear, thanks for understanding me lol.

This speech we talk about, was held last month, has there been any development?

Its amazing that only four people are behind WordPress, plus some new ones now. To me, it seems like WordPress is a company on the level of Apple. I imagined there would be hundreds of employes behind WordPress. They really give the impression of being the most professional people in the business of cloud-computing.

Same goes for BBpress. And to learn that most of this business is handled on forums and chatrooms is almost near the point of being unbelievable.

I imagined huge office landscapes, designer glasses, modern art on the walls, a brass mailbox full of offers to buy the company.

To learn that what we say on these forums, actually gets noticed by the makers is a huge privilage though. That never happens on places like Apple.com. Imagine Steve Jobs going, on the launch of iPhone 4: “So this guy Marius on the forums, really gave us a hard time about this the other day, so we decided….”

[kevinjohngallagher]

The “subscribe to topic” link is on the left hand side, above Tags.

It just doesn’t work. One of the joys of releasing a broken untested theme.

[Gautam Gupta]

*Obviously* bbPress is about working with WordPress, so those complaining about it becoming a plugin really need to get over yourselves. bbPress wasn’t made to cater whatever bizarre whim you wanted it to, it was made to provide a forum that functions with WordPress. A plugin works great for that.

You’re totally wrong. Integrating with WordPress was an after-thought. At the beginning, it was made as a standalone software.

[venividi]

Please don’t confuse ‘mu’ and 3.0’s new ‘multi site’.

Any one who has the same problem or who has no such a problem?

[ciaravino]

I think integration on MU is just broken because mine doesn’t work if you log into the forums and then try to access the blog.

[venividi]

WordPress 3.0 + bbpress 1.02 : integration works fine.

but,

wordpress 3.0 multisite + bbpress 1.02 : integration doesn’t work.

….

when added the code below in wp-confeg.png

define(‘WP_ALLOW_MULTISITE’, true);

define( ‘MULTISITE’, true );

define( ‘SUBDOMAIN_INSTALL’, false );

$base = ‘/’;

define( ‘DOMAIN_CURRENT_SITE’, ‘myhomepagename.com’ );

define( ‘PATH_CURRENT_SITE’, ‘/’ );

define( ‘SITE_ID_CURRENT_SITE’, 1 );

define( ‘BLOG_ID_CURRENT_SITE’, 1 );

the integration breaks.

What’s the problem, and what’s the solution?

Any help will be appreciated.

[chrishajer]

Pagal, please describe the problem you’re having in a new topic. It’s not clear what is happening, when it’s happening or what you expect to happen instead. Please start a new topic with that information.

[yutt]

I don’t understand why you people “looking for a lightweight forum” don’t just use Vanilla.

*Obviously* BBpress is about working with WordPress, so those complaining about it becoming a plugin really need to get over yourselves. BBpress wasn’t made to cater whatever bizarre whim you wanted it to, it was made to provide a forum that functions with WordPress. A plugin works great for that.

If you want something else, look elsewhere and stop blaming others for making a poor decision.

[citizenkeith]

One of the many broken aspects of bbpress.org 2.0.

[pagal]

In last bbpress.org theme there was an option for “subscribe for this topic”…But I can’t find In new one….

I can not stay in touch with this forums regularly but its nice to get email updates abt my topics and I don’t like rss feeds….can any mod activate this plugin?

Thanks