[xarzu]

What is with the Menus in BBPress? Are they a feature of my theme? Do I have to hand-edit them in a php file?

I have managed to put a link from my wordpress blog to my bbpress forum. Now, how do I put a link back?

http://i67.photobucket.com/albums/h292/Athono/WordPress/arguemax2.jpg

[John James Jacoby]

I have funded the development of dozens of bbPress plugins, almost all of which are available on the plugins tab as open source. They are just not released under my name, as I didn’t do the programming.

I have gone out of my way not to bash on bbPress on the forums, and to be supportive of the platform. I have 19 pages of posts on the bbPress forums, mostly answering questions from users.

I don’t think I deserve the comments you directed at me. That said, I wish you all the best with your new project.

Plugins are great, but they haven’t helped lead bbPress or contribute to the core project. Everyone appreciates any plugin that shows up in any repo, sponsored or not, yours or not.

I say this in the nicest way possible, but you shouldn’t have to go out of your way to be a genuinely nice person. Any and all contributions are always 100% awesome, so nothing I say ever is meant to mean anything other than that. The topic here is bbPress core, which means what comes in the bbpress.zip.

I’m sorry if you feel anything I said to you was off-putting. Just trying to put out this fire and answer questions with what I know to be true.

there is no way a bbPress plugin is going to be robust enough in 2010 for the public

Probably very true, and I wish I had the chance to start this topic; it sort of got started without us. We’re still going to work really hard to get something out there. Compatibility is the number 1 priority before this should even be considered to use with existing data.

Thanks for sticking to the 0.9 branch _ck_. I’ll be keeping equal eyes on the bbPress trac and BuddyPress trac, so if something crops up in 0.9 that needs committing or requires a security release, we can make that happen.

The trac is open to everyone to snoop through all of the code, and I welcome the criticism of the plugin branch 100%. I want it to be the go-to discussion forum software for every WordPress powered site, and I know that a team of people can’t do that by themselves, nor should they have to.

[jomontvm]

How can I get the corresponding Arabic version of bbpress 1.0.2?

And can I install both English and Arabic versions of bbpress under a single installation of wordpress mu with the database shared?

Anyone please advice..

[John James Jacoby]

It’s hardly dismissive. Sorry you feel that way, but it’s meant to say that those of you that are upset, are also choosing not to hear what we’re saying anymore; you’re just mad and there’s not much I, or Matt, or anyone can do about that.

Over the past year, we’ve seen people request more features, people request less features, people want new leadership, people want to know the direction of the project, etc… The fact is that you can start developing the core right away by submitting patches in the trac. If you’re not doing that, then you’re not investing in the future of the platform, you’re investing in your own ventures which I’m happy to help with, but can’t be responsible for.

Sorry you feel it’s been badly handled, but to be quite fair, it’s partly because we’ve been directly answering everyone’s questions in this topic, and partly because this won’t happen for several months anyhow. This is big news to deliver, that’s why it hasn’t been delivered yet.

John, you can continue to spend as much money as you’d like on the future of bbPress, doing those exact same things the exact same way. If you’re satisfied with what you’ve invested in today, you will continue to be tomorrow. Nothing changes other than bbPress has a team of developers that are communicating to everyone now.

I’ve answered the ‘same name’ question a few times already, as have a few others. I mean nothing but the utmost respect when I say this, but there is nothing preventing anyone that’s upset here from developing bbPress core themselves and keeping up a stable branch if they see fit. It’s very much a meritocracy, so if you keep developing, you’ll keep climbing the ladder.

There’s also nothing wrong with forking it the same way WordPress did with b2 in the beginning. We’d rather have you on board, but if you just can’t and won’t be involved in the future bbPress plugin, then all I can do is keep repeating myself.

[chrishajer]

With layout issues like that, it’s nearly always a div issue (div size, float, unclosed, extra, something.) So, you should validate first:

http://validator.w3.org/check?verbose=1&uri=http://www.supporttheanimals.co.uk/bbpress/topic.php?id=3

Can’t validate because of an invalid character on line 8. I tried to view the source of the page to see what the character might be, but when I right click on the page, I get this:

http://www.chrishajer.com/bbpress/copyright.png

[johnhiler]

It’s pretty dismissive to compare an open source project to cars, turntables and crock pots. bbPress is not a “hobby” for me. I have invested years of my life and tens of thousands of dollars in the platform. I’ve sponsored plugins, worked with developers, and answered help requests. It’s been a big part of my life, and my career.

This is big news to deliver, and I wish that Matt had delivered it personally. Or at least weighed in on it on this thread.

This proposed transition has been very badly handled. I am not even referring to the past year or so, or Matt’s posts in these forums or his speeches elsewhere. I am referring specifically to this proposed transition.

Why not just announce the separate WordPress plugin project and use a new name – why use the same name, and confuse users and antagonize this thriving community?

[ColinBradbury]

Hi I have customised the default theme as to make it match the rest of my site but I am having a major problem getting this page to look right http://www.supporttheanimals.co.uk/bbpress/topic.php?id=3 as you can see all the posts are towards the bottom of the page, could anyone tell me which section of the CSS of files I need to edit to fix this.

Also as a not so important but just an annoyance thing, if you navigate to another part of my site you will notice that the BBPress theme doesn’t quite match the rest of my site, mainly I think due to an error on my part with setting up the margins and padding but I can’t for the life of me find that solution either so if anyone can spend a moment or two to maybe let me know what I have done there too please?

If you need any of my code please don’t hesitate to ask you can contact me here or via email colin @ supporttheanimals.co.uk (without the spaces).

Kind Regards

Colin

Founder of Support The Animals

http://www.supporttheanimals.co.uk

[John James Jacoby]

Yeah… We both basically missed each other when we started both of those. That was just a miscommunication and probably a blunder on my part. I’m not sure who did what first, but we’re going to merge those two and close one of them down soon.

The way it sits today, is that ‘bbdevel’ is and has been the existing standalone development blog, and I opened ‘bbpdevel’ back in January when I originally started writing plugin bbPress code, not knowing if there was an existing dev blog, because there weren’t really existing devs . I got busy with work, and it sat for a while, and now it’s back in full swing.

If you need a way to remember it, think ‘bbp’ means bbPress plugin maybe? It wasn’t originally intended to be like that, but might help. I basically mirrored wpdevel(WordPress) and bpdevel(BuddyPress)

[citizenkeith]

Which Dev Update site should we be looking at now?

http://bbdevel.wordpress.com/

http://bbpdevel.wordpress.com/

This is just the beginning of the confusion, I’m sure. Thanks for keeping us posted. We’ve been in the dark for a while, and it’s nice to hear from the plugin developers, even though some of us still use bbpress 0.9.

[John James Jacoby]

Can’t speak on anyone’s behalf, but I imagine he does. Those sites can continue to run bbPress all the same, and if a bug fix or security issues pops up with 1.0/1.1 branches, the responsible thing to do is to fix it and push out updates.

I think what I might be confused about, is if bbPress as it is today is close to exactly what it should be, what would you want it to do 2 years from now that wouldn’t add more bloat or slow it down?

If today, it’s good; then let’s fix up what we have to put out a solid 1.1 stand-alone, and when shift gears to focus on 1.2 as the plugin milestone.

If someone crops up in 1.1 while we’re working on 1.2, then we put out a 1.1.1, etc…

Nothing is being dropped, or abandoned, or tossed aside anytime soon. The plugin is just a new branch of code with the same heart and soul, that will be able to import existing installations into WordPress.

[luminousnerd]

You could just modify the theme that comes with bbPress. Just change the url in the CSS to your header instead of the WP header.

[kevinjohngallagher]

The answer is both simple and not so simple.

You’re basically taking advantage of how modern browsers will give you wiggle room on your code. For example you’ve set your header to height 200px, and thus the background will only ever be 200px, even though your header is about 350px long (the content doesn’t start for 205px).

What I suggest is this:

– Remove the hight property from your header.

– Add a padding to your header of 205px to put all header content starting below your image.

– add a clearing div after every section of Floats. (above the closing tag of the header div for example).

One of the things IE6-8 does really well, is that it wraps everything in the code you put it in, which was in the original specification for HTML and CSS (IE was the first browser to support CSS, some 2 years before any other after all).

“modern” browsers won’t consider anything with a float to belong to the parent, so as your form and link are floated although in the header, they won’t ever be wrapped by it.

This is a good example, and I cant wait for some folks to read this, where testing in IE6 is brilliant. It would have caught these v early – as its unforgiving.

EDIT: Actually Pastor Bob, why not copy over the header of your WordPress site. It’s very nicely made.

Kev

[pastorbobsforum]

Hello again.

Thank you for the tip.

It seems to be working now, even though I don’t know where I was going wrong.

Another thing that I don’t seem to be getting to work my way, is the fact that after I (or any user as a matter of fact) log in, both the redirect link and the login form move from their position before the login (which is underneath the header), to that immediately after the search bar, placing it on top of the header.

Here are two samples of what I mean

Before: http://i896.photobucket.com/albums/ac166/nobody5973/before.png

After: http://i896.photobucket.com/albums/ac166/nobody5973/after.png

Suggestions?

Regards,

Bob

[Deewon]

I’m not after fully integrating my forum into my website, would be happy with a basic forum theme just want my website header along the top.

An example of this is: http://www.jfarthing.com/forum/

He has the forum under his header.

How would I go about this?

[kevinjohngallagher]

Hi Pastor Bob,

I’ve had a quick look at your forum and it appears to be working.

What I’d suggest is making it even simpler.

<div id="returntomain-site">

<a href="wordpress-link"> My WordPress Form </a>

</div>

From there you can build up

As a tip, add this line of code after your 4 divs inside your footer div.

<div style="float:none; clear:both;"></div>

[pastorbobsforum]

Hello.

Thank you for the fast intervention. I should have thought twice before asking my uneducated questions.

After a few modifications in my header, I cannot access my forum at all.

This is what I have in my style.css

#returntomain-site {

font-family: Georgia;

font-style: bold;

float: left;

position: right;

font-weight: bold;

width: auto;

font-size: 16px;

padding: 205px 0px 0px 0px;

margin: 5px auto 10px 20px;

}

#returntomain-site a {

color: #000;

font-weight: bold;

text-decoration: none;

}

#returntomain-site a:hover { color: #666; text-decoration: underline;}

This is what I use in header.php, to get my link underneath the header, on the right side, opposite to the login.

<div id="header" role="banner">

<?php if ( !in_array( bb_get_location(), array( 'login-page', 'register-page' ) ) ) login_form(); ?>

<div id="returntomain-site"><a>" title="<?php esc_attr_e('Return to main website's home page', ''); ?>" rel="site"> <?php printf( __('%s', ''), 'Go back to The Christian Study' ); ?></a>

</div><

</div>

Now, what I don’t get is why when I simply comment these sections in header and style, the forum is still down, but when I remove them completely, the forum comes up again. In both situations (commented bits vs.removed), I can perfectly well login into my account. There is definitely something wrong with my theme. If only I knew what…

My forum is here http://www.pastorbob.limewebs.com

Any advice?

Thank you.

Bob

[Rich Pedley]

Firstly, thanks JJJ for actually confirming that bbPress as a standalone will be dropped after the plugin is released – that does make a difference to things being discussed.

Non WordPress uses can’t use VaultPress, or BuddyPress. As the plugin is being developed, if you have suggestions on how it might still be able to sit on top of BackPress, I’m open to building that into it also provided it doesn’t overly sacrifice performance in other areas.

I keep having a weird thought which I know it not practical, about a cut down version of WordPress – oh wait that was what BackPress was supposed to be wasn’t it? Then within it you could have an option to upgrade to get full WP functionality. It would literally only need the files that bbPress utilises.

Ok I have weird thoughts – I admit it – hangs head in shame.

[kevinjohngallagher]

You can edit your Template/Theme and add a link manually

[kevinjohngallagher]

bbPress 1.0.3, and bbPress 1.1, are still being actively developed. Once those versions are available, what /more/ would you want bbPress to do on its own?

Honestly mate? Bug fixes.

Some big bugs that we’ve had for over a year have been bumped because Matt told us we weren’t to have a bug fix release, and instead were to roll out a release with 2 new features instead.

8 weeks ago Matt started deleting milestones from Trac. Didn’t tell anyone. Took him 3 weeks to reply to emails wondering why.

bbpress1.0.3 was ready over 3 months ago (save for a Backpress bug we could live with/patch ourselves). Matt decreed we’ve not to package it and give it to folks as an alpha or even an actual release. We have to wait for 1.1 and the next version of BackPress to be ready. In order to speed that up, we’ve had to bump loads to 1.5, which now isn’t going to happen.

This is the end of the line for the current implementation of bbPress.

Yes. Just like 2.9.2 was the end of the road for the 2.9 branch of WordPress when 3.0 came along. I understand the obvious differences, but at the end of the day, it’s just another day.

Two differences here though bro.

1) No-one has actually said that yet.

2) The new bbPress plugin is a totally separate project, being run under the same banner. Other than being able to import the data from the existing project, its totally different. It doesn’t even have the same requirements. Or any of the same code.

This isn’t resistance to change, nothing is being changed, it’s being replaced. And someone needs to be very clear and categorical about that. This is very very different from going from WP2.9.2 to WP3.

This is effectively a hostile takeover. The people with the keys to this website are handing the reins over to new management; while everyone is speaking in positive PR/Management speak. I’m not saying that the hostile takeover won’t be benefitial in the long run or benefitial to more people than currently use this product – i’m just syaing that hostile takeovers breed questions and uncertainty. Some of that uncertainty needs to be managed.

I know that you’re a real positive guy JJJ, and I’ve said before it’s infectious because you deliver, and deliver with a smile. I can think of no-one better to deal with this.

But the horse has bolted, the cat’s out the bag, the jig is up; and it’s a shame your left here answering questions, but in honesty – to some of us this is our livelyhood and we really need definative answers that are crystal clear so we can quote them as needed and make business decisions that affect our lives.

I am sorry tht you couldn’t have done this in your own time and in your own way. Your handling and galvanising of the BuddyPress community has been great, as I’m sure it will be here as well, we just need to get over this hump so that we can work with you

[pastorbobsforum]

Hello.

I was wondering whether there is any plugin that would give me the possibility to go back to the main wordpress website (through the medium of say, a button underneath the header, or anything as practical as that).

If there isn’t any, could I get some advice on how to do just that?

I haven’t tried the integration yet.

Thank you.

Bob

[mr_pelle]

This wouldn’t have even started if your brand new forum plugin for WordPress (for which I wish you the best of luck) were named NOT bbPress!

This community and its software have survived the last months and I think they will, if this forum won’t be flooded by newbies not knowing exactly what software they are asking questions about…

My email for further discussion: http://scr.im/mrpelle

[John James Jacoby]

Probably.

I just feel sorry for all the plugins developers…

No. Not probably, and not at all.

So far everyone’s managed to keep this pretty light and well mannered, and the easiest way to keep that pace is to not fuel any fires.

And what about non WordPress users?

Non WordPress uses can’t use VaultPress, or BuddyPress. As the plugin is being developed, if you have suggestions on how it might still be able to sit on top of BackPress, I’m open to building that into it also provided it doesn’t overly sacrifice performance in other areas.

There’s a lot of goals we hope to hit by doing this, one of which is allowing bbPress to be pocket sized and extensible from within WordPress, so that it can do other unique things that existing plugins have needed to jump through hurdles to achieve. Dedicated user forums, user groups, post/topic syncing, better BuddyPress integration, attachments, revision history, proper moderation, etc… If you don’t need those things, you can turn them off in WordPress all the same.

I know that my vote isn’t the popular one amongst the dedicated bbPress lovers, and there are lots of logistics to make this a smooth transition. With this initiative we have more people dedicated towards making this smooth and successful than bbPress has ever had in it’s 6 year history. That along with complete support from the original plugin author means it’s the next evolutionary step in bbPress’s journey.

I’ve been involved in too many hobbies to not know what it feels like when the version of something you love is discontinued, and something else replaces it that just ain’t the same. Cars, turntables, computers, cell phones, crock pots… You name it, I’ve dealt with the expiration of one thing, and moved on to the next.

The major difference with us and bbPress, is you all can help make the plugin do what you need it to by contributing code with patches. I couldn’t force Honda to bring back the del Sol CR-X if I tried.

[mr_pelle]

Something else just occurred to me.

Is Matt planning to just “nuke” all the existing content on bbPress.org ?

Do we need to start archiving ?

Probably.

I just feel sorry for all the plugins developers…

EDIT:

If they’ve never used bbPress before, then they will come here not knowing it was ever standalone, and won’t have any issues installing a plugin, and turning it on.

And what about non WordPress users?

[John James Jacoby]

They will if they came here for a stand alone software (or if they don’t use the latest version of WordPress).

If they’ve never used bbPress before, then they will come here not knowing it was ever standalone, and won’t have any issues installing a plugin, and turning it on.

This is the end of the line for the current implementation of bbPress.

Yes. Just like 2.9.2 was the end of the road for the 2.9 branch of WordPress when 3.0 came along. I understand the obvious differences, but at the end of the day, it’s just another day.

This entire support forum and plugin section for bbPress will have ZERO meaning for the plugin and will only serve to confuse people.

All the years of advice here for the two major versions of the standalone version will be useless for the plugin version.

It will have meaning for supporting legacy code, which happens all the time when something gets refactored in WordPress. Get it working in it’s current incarnation, then ensure backwards compatibility with existing installations that are already integrated with WordPress.

bbPress 1.0.3, and bbPress 1.1, are still being actively developed. Once those versions are available, what /more/ would you want bbPress to do on its own?

The *plan* is for everything to stay how it is, with no loss of data on bbPress.org, or anywhere else.

The bbPress extend section doesn’t include half of the things the WordPress.org section does now, in terms of compatibility checks, etc… By having bbPress as a plugin, we inherit that too.

I know that there’s broken spirits, and I don’t want it to be this way, but I can’t say anything any more clear to ease anyone’s anxiety about it.

Btw, the first commit is in. As you can all see, there’s plenty of work to do, so you’ll have nothing to worry about for a while.

[_ck_]

Please do not call the plugin version bbPress.

This entire support forum and plugin section for bbPress will have ZERO meaning for the plugin and will only serve to confuse people.

All the years of advice here for the two major versions of the standalone version will be useless for the plugin version.

Please call it something else.

Matt once said he didn’t like the bbPress name anyway, here’s his chance to change it.

Please change it before there are 1000 newbie questions from the WordPress forums clogging up this entire site and making all the old valuable advice disappear.

Need I mention the search for wp/bbpress is horrible so it will be impossible to sort out questions about the plugin vs standalone version.

The extend plugin section has absolutely no data or way to sort by which bbPress version they are for. This will only become much worse when there is yet another major derivative of bbPress.

The standalone version will be in use and independently developed for many years, perhaps even the remainder of this decade, so please use the opportunity start things off right for your plugin project.