[inkey]

I’ve installed bbPress 1.0.6. alpha and integrate it with WordPress 2.7.1. Everything is fine.

But there is one big problem:

When user with IE is registered, he can use forum for 2 or 3 days, after that he cannot open no one topic. After User is log in and click on topic link page loads and there is error pop-up, that says (translated to English):

Can not load page –there is url to topic page–

Operation aborted

With “OK” button.

After clicking “OK” there is IE page, that says “Internet Explorer can not view this page”.

In Firefox, Chrome, K-Meleon and Opera everything is fine.

You can test it on: http://oakdaily.ru/forum

Sorry for my English.

[superann]

Thanks johnmc! I worked hard on the site; haven’t spent nearly as much time with bbPress as I have with WP so I kind of did the absolute minimum to start and was lazy about the cookie integration that didn’t work out of the box… until someone else on my forums complained…

WP and bbPress are running side by side off the same user database, same process to set up as described in the integration thread here. No deep integration, just customized the templates to match. Registrations are routed to WP via a direct link to it in the login-form.php template, which is cool as I use the Register Plus plugin there to customize things a bit. Logins (and outs) are integrated via cookies using the plugin which you can grab here:

http://superann.com/2009/02/26/wordpress-26-27-bbpress-09-cookie-integration-plugin/

Also, thanks for the welcome, ck! I do more theme customizations for WP but usually do it all the quick and dirty way, cramming things into function.php file rather than packaging it up nicely, and I often just hack features into other plugins to get it all working the way I want. Right now as far as bbPress is concerned on my to-do list is to find a good solution for manually marking spam posts, work email notification into the pm plugin, and set up the post notification to send email by default. Just haven’t had time to look into all that yet… if there are any existing solutions/patches, please let me know! Otherwise I’ll probably look into it at some point and contribute what I can (if anyone else is interested).

[superann]

Yep, cleared all my cookies and it appears that things work as they should. I haven’t pored over the source too considerably but from what I saw it looks like there are very few dependencies, which makes sense as I’m guessing WP wants you to be able to integrate sign on systems without jumping through hoops.

My sites aren’t “deeply” integrated, so it would be great to get some feedback from anyone who tries this on a deep integration.

Plugin here:

http://superann.com/2009/02/26/wordpress-26-27-bbpress-09-cookie-integration-plugin/

In retrospect I shouldn’t have put this at v1.0, but I expect its useful life might be short anyway once bbPress 1.0 is released…

[_ck_]

Oh and by the way Ann, welcome to bbPress (though I see you were around here a few months ago for a short bit).

Seems like you know how to code so that’s great to see, hopefully you’ll get addicted to bbPress too and churn out some plugins

[_ck_]

It’s strange that I didn’t think to downgrade WP 2.7 to match bbPress 0.9 but I guess I overthought the process and figured the new “auth” cookie method would be required in the admin area on WP so it would break. I assume you have tested your admin access in WordPress after your changes?

WordPress 2.7 added three new kinds of cookies, surprised it doesn’t break anything when you force it backwards. Did you delete all of your old cookies on your browser to make sure it wasn’t “cheating” ?

In any case, my new plugin is here and should be downloadable for testing shortly:

https://bbpress.org/plugins/topic/freshly-baked-cookies/

One plus to the WP downgrade method is it might work with deep integration where mine will definitely not work and should not even be tried that way.

[_ck_]

What she did is downgrade the cookie functions in WP 2.7 to the cookie functions from WP 2.5

This takes away the extra auth cookie that WP 2.6-2.8 uses but it should be okay.

There are only 4 functions that need to be replaced.

However I’ve just finished a plugin that does the opposite approach, it allows WP 2.7 to keep it’s cookies and bbPress 0.9 switches to the newer cookie method instead.

[_ck_]

On a funny coincidence, I just finished a plugin to make 0.9 work with 2.7 cookies.

But are you saying you downgraded WP 2.7’s cookies into 2.5 cookies to make it work with bbPress by replacing the functions from the WP 2.5 pluggable?

Mine is the opposite approach, it let’s WP 2.7 keep it’s cookies and bbPress uses the logged_in cookie from WP.

I guess either technique is valid. You must have forced the salt to be the same on both sides though.

[superann]

Yep, same method above works with WP 2.7.1 and bbPress 0.9.0.4. Just tested and there’s full cookie integration.

[johnmc]

That looks awesome! Do you have a writeup or even some basic instructions on how you managed to get this working?

[superann]

WP 2.6 and bbPress 0.9 completely integrated with single sign-ons and offs sitewide. Themes are integrated for a consistent design. Tons of custom and customized plugins with no edits to the core!

BayAnime.com – San Francisco Bay Area community and resource for fans of anime, manga, and Japanese pop culture

[superann]

Are the login functions any different in 2.7 from 2.6? I just wrote in the WP + bbPress integration forum about having successfully integrated WP 2.6 and bbPress 0.9 logins by just overriding all the WP pluggable cookie functions via a plugin with code copied right from WP 2.5’s pluggable.php file. I was thinking I could just do the same for 2.7…

[superann]

I followed some of these instructions and completely integrated WP 2.6.2 and bbPress 0.9 logins on my site today (BayAnime.com). I’d already had 2.6 up and running when I installed bbPress and didn’t want to roll back (I really need to roll forward at some point), so I just copied and pasted all the old WP 2.5 cookie functions from pluggable.php into a separate plugin file for my 2.6 install, set all the paths and keys, and it’s working well. I expect you can just do the same with WP 2.7 if you want to integrate it with bbPress 0.9. Anyway just wanted to report that it IS possible to get 2.6 (and up probably) working with bbPress 0.9 without too much more pain. If anyone’s interested in the plugin file that has the WP 2.5 functions you need, just let me know!

[Ipstenu (Mika Epstein)]

Gaaah! The bbshowcase.org site is seriously screwed up. It loops to demo.bbshowcase.org, prompts for password, and I can’t seem to get past that. Had to shut down firefox.

_ck_ yer site puked!

[tza79]

I really like the theme and would possibly like to use it for a project, but it seems that bbshowcase.org has been taken down. Is there somewhere else I can download it?

[refueled]

I know these have been done before, but I have released 3 blank bbPress themes that match my blank WordPress themes.

You can download them here.

I’ve also taken a long break from bbPress theme development. I’m getting back into it, so expect more themes for bbPress soon.

[Ipstenu (Mika Epstein)]

Probably. Looking at this page for an example…

<div id="othertags">

Tags:

<ul id="yourtaglist">

<li id="tag-87_349081"><a href="https://bbpress.org/forums/tags/tag" rel="tag">tag</a> </li>

</ul>

</div>

349081 is the user ID of whomever made the tag

tag-87 is the tag ID of the tag (which in this case is ‘tag’)

Now you can go to https://bbpress.org/forums/profile/349081 and easily see who that is so you can probably use get_username(349081) or something to get the name for a mouse over. I don’t know of a way to parse the tag ID number, though.

[Ipstenu (Mika Epstein)]

Getting slashes before quotes/apostrophes in bbPress 1.0-alpha-6 integrated with WP.

What does that mean? /’ doesn’t work or …?

[Ipstenu (Mika Epstein)]

I doubt the post is being “mulled over” though, as it’s been deleted and not closed. I know this because i went to fix a typo less than 2 minutes after posting (there’s a typo in the firs paragraph) and it was closed. So who every closed it, did so without reading the post. It was deleted not long after.

As a fellow bbAdmin, I’m sure you know that a deleted post remains in the DB and can be read from the admin console. https://bbpress.org/forums/topic/how-to-help-us-help-bbpress?view=all will work for an admin/mod/key master etc.

i would like to reiterate that if people still refer to this as an open-source project and us contributors as a community, then we have to accept that there will be voices out there that don’t 100% agree with us on everything. Deleting posts that detail such opinions only makes the consensus of a view point insular and narrow.

I don’t feel the same, which is not to say I disagree with the sentiment. I can see how it could be viewed that way, but that isn’t how I see it. Nuff said, we can chat semantics of open-source ethics elsewhere!

Also to your three questions: No one can answer # 1. Ever. The ‘Right’ direction for you is different than for me and for _ck_ and for everyone else. ‘Right direction’ is way too subjective. And as a developer, I hate when people ask me ‘Would it be easier to start over?’ Maybe. But I can’t tell you how long it’d take to reinvent the wheel, and I’m sure that I’d have problems that other people have already solved. It’s a Catch-22 to the extreme.

I’d ask this:

1) Is bbPress moving?

2) Are you (developers) satisfied with the direction it’s moving in?

3) Are you (users) satisfied with the product, as it is? Does it live up to the goals, as expressed by the development team?

If # 1 is a no, then you leave the project or fork it.

If # 2 is a no, then you scrap and restart (or fork it).

If # 3 is a no, bear in mind I do not mean ‘Yeah, but I want built in smilies!’ That’s not a design goal. That’s a wishlist. Design goals are things like WP/BB integration (stated as a goal by the devs). But if it is, indeed, a no, then you really are left with the same choices. Leave or fork.

I think I’m just really keen on saying fork today *halo*

[chazbeaner]

Getting slashes before quotes/apostrophes in bbPress 1.0-alpha-6 integrated with WP.

Have searched forum for solution, but most seem to be from 2 years ago (what can be found anyway). The core file that needs to be edited (bb-includes/template-functions.php) in those instructions is no longer called that (yes, i know which one it has become), but the code also looks markedly different.

While I have *some* PHP knowledge and can follow most step-by-step stuff, I’m starting out with a different syntax than the instructions, which makes me a little nervous.

Here’s the code I think I may need to change:

‘function get_post_text( $post_id = 0 ) {

$bb_post = bb_get_post( get_post_id( $post_id ) );

return apply_filters( ‘get_post_text’, $bb_post->post_text, $bb_post->post_id );’

and then what about forum titles?

Is there an easier way to do this now, or do the core files still have to be edited?

[kevinjohngallagher]

Hi Ipstenu,

Once again you are spot on mate.

I’m not in anyway suggesting that the mods/owners don’t have the right to close / delete a forum post, in fact i respect their right to do so. But i also think if someone’s taken the time to write a constructive post then there should be a common decency to at least tell them why it’s been closed and then deleted within 5 minutes of it being posted. Respect kinda has to go both ways.

I doubt the post is being “mulled over” though, as it’s been deleted and not closed. I know this because i went to fix a typo less than 2 minutes after posting (there’s a typo in the firs paragraph) and it was closed. So who every closed it, did so without reading the post. It was deleted not long after.

I’m not going to flog a dead horse, or push a personal agenda; the mods have a right to do what they want – but i would like to reiterate that if people still refer to this as an open-source project and us contributors as a community, then we have to accept that there will be voices out there that don’t 100% agree with us on everything. Deleting posts that detail such opinions only makes the consensus of a view point insular and narrow.

BBpress has amazing potential, I hope it succeeds, i want to help make it succeed.

If _ck_ isn’t updating her plugins for any of the alpha or beta releases, then we’re effectively given a free-er reign here to not worry about backward compatibility (as lets be honest, _ck_’s plugins are freaking’ awesome); then surely now is the time to ask the hard questions.

I am not, in any way shape or form, suggesting a complete rewrite or anything like that. But if we put our BA or PM heads on and ask ourselves:

1) Is BBpress moving in the right direction?

2) Is the legacy code from before Sam took ownership causing issues?

3) If we had a clean slate and unlimited time, what would be fix?

Now the answers may be 1) Yes, 2) No, 3) nothing it’s all working fine. And if they are that’s cool, but sometimes there is a big difference between am end-user view, a developer view, owner view and a Project Manager view. Even if everyone is in complete agreement (unlikely in any community), the right and ability to question can only help but guide the project and give reassurance to its contributors.

It might also end all of these timeline/compatibility/development/plug-in questions we’re getting (and going to get more) – thus making the lives of the mods alot easier.

BBpress has amazing potential, I hope it succeeds, i want to help make it succeed.

[Ipstenu (Mika Epstein)]

I’m of divided opinion there, danblee.Yes, it should be noted (but alas a lot of the documentation is ‘in progress’) but then I think PHP 5 came out in 2004, that’s five years ago. It’s not unreasonable to say you should upgrade.

[danblee]

This worked like a charm, Ipstenu. Thanks for the fix. I find it strange that there wouldn’t be a warning regarding the issue with PHP4. It’s kind of a big deal.

[chrishajer]

You need to create a file called .htaccess in your forum root. Be sure the file starts with a period, and this only works if you’re on an Apache-based web server. IIS will not repond to this.

Point your browser to bb-admin/rewrite-rules.php and paste the output of that screen into the file called .htaccess in your forum root. Now change the setting in the bbPress admin. Hopefully all will be well with that setup, but if not, post here.

For example, if your forum is at http://www.example.com/forums/ then you need to point your browser to http://www.example.com/forums/bb-admin/rewrite-rules.php and grab the output of that to paste into your new .htaccess file. Also, I think that only works if you’re logged in as keymaster. I don’t think you can just do that on any bbPress site.

Also, you might need to put this at the top of your .htaccess file:

Options -MultiViews

Some hosts won’t work without that (like mine for, 1and1.com).

[chrishajer]

Permalinks are just that – permanent. I don’t believe the permalink will change even if you change the topic title. I don’t think that’s a bug, I think that’s intentional.

For example:

https://bbpress.org/forums/topic/modify-existing-permalink

[frooyo]

To help get more people actively involved, why doesn’t bbPress host a “bug fixing marathon weekend” and offer a prize to the most bugs fixed within a 48 hour period.

Or a contest to redesign the web site.

Or a contest to improve the documentation.

Just trying to come up with ideas to help.