[Ben L.]

bb_auth() can be called with 'logged_in' as the $scheme to check if a user is logged in.

[chrishajer]

Yes, if the updates work as designed. We always were running the trunk version, but for some reason, the updates didn’t always work. I’m not even sure when they run. But the new code appears here automatically.

[Ashish Kumar (Ashfame)]

@Ben

Didn’t get your point. I can’t see that in file either functions.bb-pluggable.php

[Gautam Gupta]

Do you load WordPress’ wp-load.php in bbPress?

[Ben L.]

There’s also bb_auth( 'logged_in' ) if you aren’t checking if the user can be in bb-admin.

[Gautam Gupta]

It is used for the bb_get_uri function (which generates the URL).

[rohan_shenoy]

It is fixed in trunk, you can copy the changes to your install from here – https://trac.bbpress.org/changeset?new=2383%40%2F&old=2381%40%2F

Thanks a lot Gautam

On second thought,

Can you please tell me why the error arised? I had not edited any php file. All I did was fiddled with database!

[chrishajer]

Heh – the update finally took place automatically. We added that revision to the header a while back, but the code was not being updated here.

Also, We’re actually running 2442 here – the note I added to the version was the current revision. I should have jumped ahead one when I checked the code in. So, trunk and here are the same thing, despite the meta header.

[astaganaga]

Love it

[kevinjohngallagher]

Folks,

please don’t derail this thread with nonsense about another forum software, we’re still trying to sort this one

[kevinjohngallagher]

function bb_auth( $scheme = 'auth' )

{ // Checks if a user has a valid cookie, if not redirects them to the main page

}

I’m guessing it “Checks if a user has a valid cookie, if not redirects them to the main page”

First link on google

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