[kevinjohngallagher]

You’re not an idiot mate, but this is where bbPress starts to struggle a bit – especially with no documentation.

You want to make a call to the Database directly via SQL (SQLECT * FROM blah blah blah), but thre is no quick fix. You can use the $bbdb class to connect to the database.

If your’e still struggling, do a hunt for $bbdb with here on google. Remember that search on this site su… has many inbuilt features that are not bugs

[gjoseph]

You can edit the post.php file of your theme: find the line with post_author_avatar_link:

Replace <?php post_author_avatar_link(); ?>

by <?php post_author_avatar_link(132); ?>

for example.

[kevinjohngallagher]

Yeah, basically the global variable you’re using $forum/$topic/$posts etc. have been codedin such a way that they can only be iterated trhough once.

You’ll need ot make a separat SQL/data call for each bit of info that you need.

[saare2000]

thanks for the help. I started by maiking a new theme and almost blank css, but got stuck exactly where I need to modify the front-page.php and couldn’t find anything concrete from Docs.

seems like instead of

?php if ( $topics ) : ?

there should be something like

?php if ( $topics || $category-id ) : ?

… am I correct?

[kevinjohngallagher]

Thats the link, just hardcode it. It doesn’t need to be processed by PHP at all. Just add it to your HTML code.

And yeah, the formatting change is a bug we’ve been stuck with for weeks. It’s not being worked on.

[Gautam Gupta]

You have to edit logged-in.php, that would contain the logout link. login_form functions includes that file if the user is logged in, otherwise login-form.php.

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

[kevinjohngallagher]

bb-login.php?action=logout

[kevinjohngallagher]

Thanks, thats really helpful.

You could definately do this, though it’s not overly easy, it is relatively straightforward.

You’ve 3 options:

1) Edit the CSS to attempt to display things the way you want.

In theory it’s good, in practice it’d be a pain (imo).

2) Edit the theme file to put categories into their own DIV and then style them into two columns via CSS.

Probably the easiest without hacking any real PHP.

3) Write your own query on the database and output hte code exactly as you want it.

Tricky, mostly as we’ve no documentation or examples, but it’s definately possible if you know your way around PHP (and any cusotm wordpress theming experience would be helpful)

Basically though, you’ll have to code it and you’re somewhat on your own there, but we can try and help out if you hit a road block.

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

[saare2000]

Is there a way to set two different categories next to each other in main page.

---

---

| id 1 | | id 2 |

---

---

Thanks in advance!

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

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

[kevinjohngallagher]

I doubt it mate, to start with it means that the poster isn’t anonymous.

What you’re after is all the advantages of being a member, while still being anonymous and thats not too likely.

Basically, if you want email updates, register to the website

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

[citizenkeith]

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

[kevinjohngallagher]

What would you like me to say?

You haven’t told me what’s you’re expecting teh code to do, and what it does wrong instead?

Please, I want to help, but “it takes me to localhost” gives me nothing to work with

[pagal]

it takes me to local host… and my code was..

<?php

if ( is_user_logged_in() ) {

echo ”;

} else {

echo ‘

<table width=”480″ height=”90″ border=”0″ align=”right” >

<tr>

<td align=”left” >

<form class=”login” method=”post” action=”http://www.mysite.com/forums/bb-login.php”>

<div>

<label> Username

<input name=”user_login” type=”text” id=”quick_user_login” size=”13″ maxlength=”40″ value=”” tabindex=”1″ />

</label>

<label>

Password

<input name=”password” type=”password” id=”quick_password” size=”13″ maxlength=”40″ tabindex=”2″ />

</label>

<input name=”re” type=”hidden” value=”” />

<input type=”hidden” name=”_wp_http_referer” value=”/” />

<input type=”submit” name=”Submit” class=”submit” value=”Log in” tabindex=”4″ />

</div>

<div class=”remember”>

<label>

<input name=”remember” type=”checkbox” id=”quick_remember” value=”1″ tabindex=”3″ />

Remember me

</label>

</div>

</form>

</td>

</tr>

</table>

‘;

};

?>

<?php } ?>

@kevinjohngallagher please did not say this time “write your own code”

[pagal]

_ck_ you are always smarter then others……

I’ll wait for your answer

I will pray for you that that migraine did not try to tease you….

Thanks for your hope…

[kevinjohngallagher]

Gautam my friend,

I may face your ire here a little, but looking at the 1.1 trac list, i’m going to bump some more things to 1.5.

With the focus being on 1.0.3 for the last while, there’s been a few things that definately fall under the heading of “Scope Creep” in the 1.1 Milestone.

Now that 1.0.3 isn’t being released as Matt emailed Chris saying to release 1.1 when it was ready, I believe we should focus on what needs to be done for 1.1, and not do additional coding.

Yes there are things we’d all like to see, but given the HUGE amount of changes (over a year’s worth of code), lets just get it out without adding more functionality simply because we’re not under a strict time limit.

Again, I’m deleting nothing (though whoever put in the YouTube video as high priority is having a laugh), and just moving somethings to 1.5. Lets knock out what we can in the 1.1 milestone, and if we’re still waiting on BackPress to roll out it’s fixes we can hunt some of those nice to have’s that I’ve moved to 1.5

[ciaravino]

There isn’t even labels or text boxes for auth_salt, secure_auth, and logged_in_salt in the actual wp-admin/options.php page when you view it from the admin area. There’s a bunch of other options but I’ve looked through them and used Find, but I don’t see them

WordPress Integration Settings for bbPress admin even gives me a direct link to the options page that it says those settings are, but they aren’t there. Here’s what it says for each of the 3 required salts:

“This must match the value of the WordPress setting named “auth_salt” in your WordPress site. Look for the option labeled “auth_salt”.”

“This must match the value of the WordPress setting named “secure_auth_salt” in your WordPress site. Look for the option labeled “secure_auth_salt”.”

“his must match the value of the WordPress setting named “logged_in_salt” in your WordPress site. Look for the option labeled “logged_in_salt”.”

[kevinjohngallagher]

No question is dumb mate, though the idea of testing your users to get 9/10 questions right before allowing them to talk on a forum might be very close to it

It’s just a SQL call.

You can store the information you need in the “_meta” table.

Basically don’t think about it as a bbPress plugin, just code the PHP as you would if it was a website you’d built yourself.

[kevinjohngallagher]

If I wanted to make it so people had to register and login through the blog, I would just replace all the login stuff on the forums with a link that takes you to the blog?

No, you could just point the action part of your login/registration form to the WordPress one. That way people could login/register from wherever they want, but your WordPress install does all of the difficult work behind the scenes.

The salts are all in the wp-config file on my blog, but they aren’t showing up in the options.php page in the blog admin

Yeah, just copy them from the WP-config file.

Also, my blog and forums both have different $table_prefixs. Should they both have the same

Nah, thts fine as long as you have changed the bb-config to let it know what the WP user table is called.

Also, WP3.0MU is totally new to us (it’s been out less than 48 hours), so if there are any additional issues you might be the first to find them.

[Taeo]

I guess I wasn’t involved with the community long enough to feel the burn from the back and forth decisions you mentioned. That does sound pretty shitty!

This is just pure speculation here but maybe the information from Automattic was so inconsistent because they weren’t sure what direction they were going themselves. I don’t know the whole history of BackPress but it sounds like it was a pretty big undertaking that would have had implications for WordPress as well. Going off my knowledge and what Matt said in the keynote it sounds like the BackPress project just didn’t work out in the long run but it was too late to take it back from bbPress.

Again, thats pure speculation so treat it with a grain of salt

BTW Taeo, I miss not being able to recommed your UI

Heh sorry about that. It was too much work to maintain between patches I’ve posted some new stuff on my new website ( http://www.wowuigallery.com/topic/taeo-333-ui ) but it doesn’t have all the auto-config bells and whistles of the original.

For an good looking, easy to setup UI I usually recommend TukUI to people. I helped him build his site (WordPress and bbPress of course).