[Macmenddotcom]

its great to see more people trying a hand at bbpress themes, well done

[timskii]

Briefly on the bloat comments:

Forums are different from ‘blogs, and these differences need to be considered in the design:

• Users tend to interact more with forum pages – more page views, less use of remote feeds.
• Advertisers dislike forums – they’re much harder to fund using advertising.

So a “processor-intensive” forum can become a technical headache once you start seeing tens (or even hundreds) of thousands of users each day.

I’m in favour of features – BBPress clearly needs more to compete with mainstream expectations. The problem is specifically with features that are not optional – features that cannot be removed.

The logical approach is to include “standard” plugins in the distribution, which can be turned off as required. But that might still be problematic, if the most basic forum has to haul in the whole of WordPress before it does anything…

[Spindoctor]

Hi!

I also try to integrate Cookies, but I don’t succeed.

This might be due to the issue, that it’s not possible for me to follow every step of gerikgs instruction (by the way thank you for posting this instruction).

Here’s what I did:

my blog adress is http://www.<domain>/<home-folder>/

my wordpress adress is http://www.<domain>/<home-folder>/wordpress/

my bbpress adress is http://www.<domain>/<home-folder>/wordpress/bbpress/

(As I have no write-access on <domain> or <domain>/<home-folder>/, I had to keep the “www.”.)

Besides, I changed the table-prefixes of wordpress and bbpress to “<string>wp_” and “<string>bbpress_” when I installed wordpress and bbpress.

To integrate bbpress-cookies with wordpress, I changed the keys in wp-config.php and bb-config.php, just as described by gerikg.

Afterwards I changed Integration Settings in bbpress, so that WP-Admins are Keymasters in bbpress and every other role is member. (Again I had to keep the WWW in the URLs.) Sadly, the keys were not inactive…

Then I added “define( ‘COOKIEPATH’, ‘/<home folder>/’ );” (the plugin told me to add “define( ‘COOKIEPATH’, ‘/<home folder>/wordpress/’ );”, but when I did this I had problems with the cookies in wordpress itself, so I removed “wordpress/”)

Maybe that’s not surprising, but Cookie-Integration still doesn’t work.

I there a way to get Cookie-Integration working, with this setup?

Thank you for your help!!!

[citizenkeith]

John: Here are two active forums, one running 0.9.0.6 and one running 1.02. That latter is integrated with WP. Each install is on a different shared web host.

Running 0.9.0.6 on Hurricane Electric “Starter Virtual Host”

0.075 – 12 queries

0.518 – 16 queries

0.406 – 16 queries

0.334 – 15 queries

Running 1.02 on Media Temple Grid Service

0.580 – 21 queries

0.447 – 18 queries

0.376 – 16 queries

0.728 – 19 queries

[Gautam]

nice one!

[Elias]

The one thing I love on bbPress

The one thing I love on bbPress is: It is simple and fast. “Simple” means, its functionality is easy to understand and to use for a less experienced internet user and there are no features distracting from the one core thing in a forum, from that funny discussion thing. And “Fast” means, that the bbPress core is even faster than the rather minimalist PunBB on the virtual server I use bbPress on. These are the two “features” of bbPress I really want to see in the future.

The things I hate on WordPress

Following the current discussion reminds me on my own experience with the great WordPress blog software. I am a WordPress user since WP 1.5.x, and WP 1.5.x was the software making me a blogger. It was easy to use, had a clean and simple user interface for the blogger, could be extended easily and replaces my simple home-written system after one week of testing and comparing to s9y.

Now, I do hate my long ago decision for WP sometimes. The current WP version 2.8.x is bloated, slow and without a good caching plugin not well-suited for a blog with readers.

As an example, there is a tiny german blog filled by me and less frequent some other people. It is called “Blah”, and most of its postings are simply links to other internet resources, mostly political, conspirational and funny ones. Did I mention that the blog is called “Blah”? It is not really a “successful” one, in the last six months there were approximately 2,000 visits per day, that’s not much. The “average visitor” requests five postings, and only one percent of them ever leaves a comment. The blog’s database contains 4,300 posts at the moment, that’s not much too. If I deactivate the WP Super Cache plugin, the server fails to handle that little load, the response time of the tiny blog grow to 30 to 50 seconds, the apache processes accumulates and finally the server runs out of virtual memory, giving visitors that funny “Out of memory” PHP error messages or a plain white page.

This is a situation totally unwanted for a bulletin board, which is a highly dynamic kind of website that can not be cached as easy as the less frequent views of a blog.

From bbPress 0.9.x to 1.0.x, the number of database queries to view the same page has nearly doubled, and the execution time has grown by approximately 60 percent on the same server. From the user point’s of view, it was exactly the same page, and bbPress is at the moment still performant enough to be better than any other bulletin board software. But from my point of view it remembers me to the things I experienced again and again with many new WordPress versions in the past, reaching the current point of a blog, which isn’t made to have more than a handful of readers. But for a WP blog, I can work around with WP Super Cache, for forums this approach is nearly impossible.

Some words about readers

I’m looking at the statistics generated from the apache logfiles of the Blah-blog for the last six months. It is a blog in german language, and of course most readers are living in Germany, less in Austria or Suisse, some in the Netherlands, Danmark, Belgium, Poland, Russia or Hungary too. These are not readers from the so called “third world”. (There is only one world, and we all have to share it!) In the last six months, 19 percent of the Blah-blog readers used an old dial-up modem connection to access it. (Identified by the rather speaking hostnames given in germany for that kind of connection I can identify, there may be some more readers with a low-bandwidth connection.) For this fifth part of my readers (which may be a representative value for other websites in germany too, but most people seems not interested in this kind of information), every use of large JavaScript magic which has to be loaded via a low-bandwidth connection gives an impression of slowness, and this is something I do not want to give them. That’s a reason for the rather minimalistic design of this blog.

Let me compare that 19 percent to another statistical number for the Blah-blog. 12 percent of all readers uses that fu… fine Internet Explorer 6.0 for surfing. (Identified by the user-agent string, which may be faked in rare cases.) The IE 6 is an old and ugly browser with many problems and a CSS box model interpretation giving a good headache to designers, and there are much better browsers out for free. But in many cases it is unwanted to exclude that 12 percent of website users or to give them a totally trashed design experience. It is also amazing, how many people are still using Windows 98 or ME or even Windows NT 4.0. I assume these people use rather old computers, still working for their personal requirements, so they don’t want to throw them to waste. Yes, there are people out there, which are poor and simply cannot spend a few hundred euros for new hardware every few years — me too. These are people I don’t want to exclude from any website I maintain, and especially I don’t want to exclude these from pages about political or cultural subjects. Every kind of bloat is wrong in my point of view.

(I use bbPress for a small forum on an uncommercial artists’ webpage, and it is great for that. This usage is my reason why I’m maintaining an inofficial german translation of bbPress, there is simply no language file for German at the moment, and not to share this work is stupid.)

Some words about the dashboard

The current bbPress dashboard is fine, it is aesthetical appealing, easy to use (compared to other bulletin boards’ backends) and fast even via a low-bandwidth connection and on a not up-to-date computer. It can be used with all browsers, and it makes all administrative tasks easy. The current WordPress dashboard sucks. It is unuseable slow with the Opera browser, and even with other browsers needs an enourmeous transfer of data and an long initialization time before one can do that simple thing which is blogging: writing a new post. If someone uses an older computer (older than five years), it is unuseable with any browser, and it is unbelievable frustrating to use via a dialup connection. And no, that “Google Gears” stuff does not help.) The huge amount of features are overwhelming for an unexperienced user, and for the little artists’ site (with eight authors) I still have to help some people for every post they want to blog. Since I had to upgrade that site to WP 2.8.x (it used 2.0.x and 2.3.x for a long time), the other authors hate me. Some of them are poor people. I recommend the usage of BlogDesk for them, but sometimes there are tasks which cannot be done with BlogDesk, as deleting an unwanted idiot’s comment or declaring a post as sticky (to announce an action, happening, exhibition, sound vernissage, reading, party, etc.). Since WP 2.8.x, the posting frequency of some co-authors is reduced to zero, and if I had the possibility for it, I would create my own WordPress fork (a DietPress for people who wants blogging without bloat).

And this is the way bbPress should avoid, in my opinion.

The bbPress of the future I want

bbPress is great! The bbPress core is good, and the features in an out-of-the-box installation are enough in many cases. But of course, there are things that could be improved, and there are many features often missed by people who wants a bulletin board. The probaly most wanted features are (list may be incomplete)

• eMail notification for new posts
• A kind of bbCode, which meets better the standard people expect in a BB software
• An improved editor, helping the user to do the wanted markup (may be bloaty magic WYSIWYG, but even eight buttons with a little JavaScript are better than nothing for the inexperienced user)
• An internal system of personal messaging (I hate it, but others love it)
• Attachment of files to a post
• Perhaps an avatar system independent from Gravatar
• An easy to extend user profile with additional informations
• A “who is online now” display
• Counters how often a post has been read
• A “terms of usage” statement which is required to be accepted by newly registered users
• An extended search with criteria as forum, tag, date range, username. (The existing search is better than the WordPress search, but I can still be improved. In a support forum with ten thousands of topics, it would be good to have the accumulated information more “findable”.)
• An interactive (and plugin-extensible and i18nable) help system for all core bbPress features, explaining the bbPress usage to inexperienced users and the concepts they cannot understand directly, especially tags. This is something I haven’t seen in any other BB software, but it is something really needed. It may even contain some words about netiquette…
• Perhaps a “widget system” similar to WP as a simple way to modify the order of appearance of the displayed entities without editing in themes

And of course, bbPress must remain performant, non-bloated and easy to integrate with WordPress. That’s a lot…

Many of these frequently requested features are not a good “standard” functionablity.

• The eMail notification is fine for spammers too. I am registered in some boards with this “feature”, and from time to time someone registers, writes spammy posts to various topics and the BB software dutifully and reliable sends that spam to a lot of users, before a moderator can do something. That’s why I am deactivating it always — one day, I received more than 100 mails “from my favorite forum”… aaargh!
• An over-improved editor slows down the forum for people with old hardware and makes the forum unusable for blind people with their strange solutions for surfing. (Yes, some of my “readers” are blind.)
• Personal massaging is a poor reinvention of good old internet eMail that sucks. For someone active on various boards, he has to check it messages in many places, which is ugly.
• An extended user profile is exactly the thing spammers want. The links in approximately 5 percent of my eMail spam are going to user profiles in bulletin boards, which are misused in many ways.
• Every upload possibility to the server can be a security problem, can be used by spammers to put spammy graphics in the internet or can consume execessive hard disc space on the server if heavily used.

But of course these features are wanted in many cases.

We should have a bbPress slogan for all future development. My suggestion is: Let’s make simple things easy, and let’s make complex things possible.

Learning from that part of WordPress which sucks means: Doing it better in bbPress. The core system should kept as a small one, perhaps a little smaller than the actual core. (The current user profile is sometimes unwanted.) And all additional features should be implemented in plugins, that a forum administrator can activate and configure as needed.

Core Plugins

But plugins are a huge problem too. Using a plugin indenpendent from the core system means: Making the update of bbPress to a new version sometimes to a migraine upgrade, whenever the needed plugins do not work with the newer version. Sometimes, I have this problem with one of my sites based on WordPress. And if the plugin’s functionality does require editing in the themes, it excludes less-experienced forum-administrators with a lack of PHP knowledge from using the plugins, which is not exactly the way to make complex things possible.

So there should be a set of plugins which are part of the bbPress release, which are developed together with the core system, let’s call them “core plugins”. It is not required to activate them to have a simple and basic bulletin board, but if someone do so, he will never have problems with upgrades. The “core plugins” are guaranteed to be delivered and to work with every release version and every security fix ever released. We have this kind of “core plugins” already, bozo users and Akismet. But it is a concept to be extended. A better post editor, a “terms of usage” page, a PM system, an internal avatar system, attachments to posts and all the administrative stuff around these features are good candidates for “core plugins”. If someone does not need them, he does not activated them. But if someone activates them and only them, this will never make the next bbPress release to a upgrade hell.

There may be bbPress-tags which are implemented empty if a core plugin isn’t activated, to make it easy to program the default theme and any other theme independent from the activated set of “core plugins” and without that sucking lines of if (function_exists ('bb_great_feature')) bb_great_feature ();. This kind of interface can be defined long before the “core plugins” are stable, and it can be documented for theme developers to allow them making their themes future-proof. (Oh yes, we need some good themes, the default one is fine, but some people want a richer selection.)

The bbPress features eighty percent of people want can be implemented in “core plugins”. Simple things will be easy. And if someone wants a small bbPress, that’s easier, he simply does not need to activate any “core plugin”. And there is still a plugin interface which makes complex things possible — sometimes a little editing in themes is required, but most people never needs to do so.

That’s the way bbPress should go, in my opinion.

(It may be a way for the future of WordPress too. But that’s not the topic here, and the WP developers do their work for a huge community of users and simply cannot change earlier decisions easily.)

And excuse my english. My poetic german is much better… and shorter.

[kevinjohngallagher]

Wow, for some reason half of my post doesnt’ appear until i’m logged in. That can’t be good…

@grassrootsspa

Bloat of the code isn’t the Physical Size mate, its how well written the code is, how processor intensive it is, and how many Database queries it needs etc etc.

v1.0.2 with 0 plugins is about 150% more processor intensive than v0.9 with all my plugins running. On small sites it makes very little difference, on large sites it makes a heck of a difference.

The two websites i’ve upgraded to v1.0.2, simply did to having to upgrade WP on them, are far more processor intensive than all my other sites. Faaaar more. _CK_ had some really good stats on this before she left, which we now dont have access to, so i apologise for my annacdotal evidence.

My point was, not to nit-pick over your statement or get into a discussion about which specific features YOU and I want in the core (because that would vary from everyone else here), but merely to come to some form of concensus about how we should talk about what we all think BBpress needs.

I say this because, since BBprogress closed and i’ve tried to be more involved with the BBpress site again, i notice that people mix up Feature requests quite a bit. If i can again take your post:

“…private messaging, TinyMCE/rich text, topic views, Allow Images, Smilies, User Directory, Members Online, Related Topics, Reputation, Top Posters…”

Topic Views is a great example of something that is pretty bog standard in terms of user’s experience of forum software. X thread was viewed Y times and replied to Z times. Without adding much/any bloat to the forum software, you’re adding a feature any user from ages 1 to 100 could use without requiring interactivity.

Private messaging, Reputations, Rich Text Editors etc all work on the presumption that the average/most users want that. Experience tells us otherwise.

“Let’s make bbPress more robust in features so it blows vBulletin out of the water”.

I’m not sure why anyone else came to BBpress, so i dont want to presume. But there seems to be 2 camps, those that wanted totally customizable well written code with hooks in a way we were used to and those that came to BBpress because WP is awesome and easy to configure/download themes for and they wanted to create something as good as vBulletin but easier to control.

I’m quietly confident people in camp 1 are not fussed in the slightest about blowing “vBulletin out of the water”, because if it did, then i’d just have something along the same lines as vBulletin. Not wanting that is the reason i joine dup here in the first place, again thats just me.

People in camp 2, have a tendancy to want core Features to be things (while useful) that aren’t neccessary for forum software to fulfill its duty in the most efficient manner.

There’s nothing wrong with either opinion, but taking the fight to other forum software via cool features that on the whole are rarely used by the end user, is not in anyway the focus of BBpress.

@johnhiler

It is good to see an old voice

You’re ofc right about fixing this website (in the first instance to remove all the wrong information), and the plugin section, but i’m going to say that documentation on functions is not something i’m too fussed about right now.

I think you’re right that, even with Matt taking over BBpress, we wont have a new release anytime soon, and as such this is BBpress’ most stable time in years to design theme’s and plugins. And yet, thats not happening.

With Sam’s moving on, and then then _ck_’s moving on, the project appeared (emphasis on appeared) to be shelved or forgotten about. Development has slowed to a crawl, and many sites that use BBpress are still choosing to use 0.9 (I know that both you and I are for the most part).

The realism is that 1.0.2 wasn’t seen to be a full on stable release by many, rather a rushed stop gap. This wasn’t helped at the time by _ck_’s negative comments about it (which i agreed with both at the time and now). It was largely rewritten between the 2nd and 3rd alpha, and beta testing was scrapped before it was released to us. 2 small bug fix released 1.0.1 and 1.0.2 and c.15 days later the main/only developer leaves town without saying anything. *tumbleweed*

Whatever Matt and the team do, it’ll need some serious project management, and some serious PR to get people beliving in the project again. Looks to me like he’s started both, which is wonderful, but i still doubt that many people will be up for documenting a version of BBpress that is likely to be replaced realtively soon – especially given how few plugin or theme developers there are for BBpress, and the sheer drop in numbers in comparison to how many there were a year ago.

Good night all and take care.

[johnhiler]

Hey citizenkeith… do you have bbPress benchmark installed?

https://bbpress.org/plugins/topic/bb-benchmark/

I’d be interested in the number of queries/output time for your installs… I’ve seen a 10x speed difference in test installs and am wondering how common that is!

[citizenkeith]

I’ve tried both 0.9.06 and 1.02 and didn’t notice much of a difference. I stuck with 0.9.0.6 simply because there are more plugins available.

[johnhiler]

@grassrootsspa – The size of the code isn’t necessarily the key factor in bloat. A tiny but poorly coded feature or plugin can put an immense load on the server! I think for most personal sites this isn’t a big factor, but scaling is a huge factor for some sites and I greatly appreciate having the choice to keep features out of my core engine.

In any case, history is on your side… Matt tends to move features from the plugin into the core (or just add them straight to the core). Sam was moving in that direction too – Voices went straight into the core without any discussion or debate, even though it could easily have been implemented as a plugin:

https://bbpress.org/plugins/topic/topic-voices/

Overall what bbPress needs right now is not new features or a new release. It needs documentation of what we have, and a focus on building a developer/designer community. A themes directory would go a long way towards that. So would sprucing up the Extend/plugins tab not to be using the 0.8.x version of bbPress… which isn’t even signin integrated! And Stats have been “coming soon” for several years now:

https://bbpress.org/plugins/topic/bb-cumulus/stats/

Implementing this stuff (along with a site redesign) would also give the Automattic leadership time to get to know the bbPress community better, before any hasty design decisions are made.

[grassrootspa]

@ kevinjohngallagher:

One doesn’t need bbpress to display Voices, but it’s built into the core.

One doesn’t need bbpress to give every registered user a profile pic or gravatar, but it’s built into the core.

One doesn’t need bbpress to display Tags, but it’s built into the core.

One doesn’t need bbpress to allow users to ‘favorite’ posts, but it’s built into the core.

One doesn’t need bbpress to display a user’s recent activisty, but it’s built into the core.

One doesn’t need bbpress to display a user’s location, occupation, and interests, but it’s built into the core.

We could go on, and on, and on. One could make the argument that those features above (as well as others) could easily just be offered as plugins (no one REALLY needs to use them) but they are there to make the software more robust, fun, and useful! Think about each one and how things like Tags, favorites, gravatars, profile pics could simply be kept as plugins. Thank God those features were incorporated into the core.

Yes, bbPress could be the most barebone of all barebone bulletin board programs, with multiple plugins required to do anything more than throwing up a forum post, but for this software to become what WordPress is to blogging/CMS software it needs to offer a more robust list of core features that can be refined and further fleshed out with future plugins.

Again, I’m not saying you NEED to have TinyMCE turned on, use bbPress widgets, show how many times a topic has been viewed, display how many users are online, or use (new) default topic icons, but build this stuff into the core so folks can optionally use it, develop plugins to flesh those features out (imagine plugins/themes built around customizing various icon sets), and this stuff can grow with bbPress.

bbPress is like 1.93 MB is size. Plugins like mini-stats are 37.9 KB. You guys are killing me, like incorporating stuff like some of the more popular plugins is going to make bbPress too bulky and bloated to use? Someone isn’t going to go, OMG, bbPress is 2.20 MB in size, its just to bloated to download and install on my server and it offers too many optional features! Come on guys, this is getting silly. Let’s make bbPress more robust in features so it blows vBulletin out of the water.

[refueled]

Live Preview

Release Page

‘Marked’ is based on a design by freewpthemes.net.

[johnhiler]

Yes, 1.0 has a dramatically higher load.

I’m running 9 0.9.x bbPress installs along with a WordPress install on a single machine that’s doing around 10mm pageviews a month. If I was using the 1.0 branch, I don’t think I could come close to that.

[kevinjohngallagher]

It is, by about 50%.

That said, no version of BBpress is particularly heavy on the processor

[gerikg]

Heavier, yes. Will the average user notice, no.

[kevinjohngallagher]

@timskii

“Joanna Average forum reader doesn’t care about any of that, and is probably keener on things like WYSYWYG, email, etc.”

This is a really excellent point, but you have to realise that “Joanna Average” doesn’t hang around on these forums, and so any suggestions of what the ‘average’ user wants – especially in terms of interactive functionality – is generally the poster projecting their own wishes.

There is also this great myth that the ‘average user’ is a tech savvy person, running JavaScript on a fast machine, who greatly enjoys a every feature out there. If you look at the trend of the internet over the past 15 years, almost all types of interactivity on the client-side or ‘feature requests’ become popular and then get phased to a small percentage real quickly.

@grassrootspa

“…private messaging, TinyMCE/rich text, topic views, Allow Images, Smilies, User Directory, Members Online, Related Topics, Reputation, Top Posters…”

The issue i have here mate, is that very few of these are essential to the running of a forum.

I use, and one or two other do two, something called E-mail as a private messaging system. My website, bless it – almost 14 years old now – has something called a Contact Form. I’m not sure that forums absolutely *need* another way of contacting people to function.

I don’t want to debunk your list, but given what you and timskii have said that we should redefine the categories we’re placing things into:

1) Features that are essential to administer a forum.

2) Features that are essential for users to use a forum.

3) Features that you’d like to see available to your forum.

4) Features that could be kind of cool.

5) Features that are useless.

BBpress development should, in my opinion, focus on Section 1 and then Section 2. Once we have a working stable and maintained version of BBpress, plugin developers will start to work on Sections 3 and 4. We know this because that’s how WordPress works, and its how BBpress was working about a year-18 months ago with version 0.9.

My issue is, while everyone’s opinion would vary, i don’t see many of the features you think should be included as standard being in Section 1 or 2. I understand that they may be features you want in t a forum as standard, or features that you think your users want as standard – and that’s totally cool – but lets focus on the features that both we (admins) and the users need as a minimum to use our forums effectively.

Just my two cents.

[claudiuro]

I want to install bbpress but I am considering server load, so can anyone tell me if 1.0.2 in terms of server load is “heavier” than 0.9?

Thank you.

[kevinjohngallagher]

OK, i may be a little off the reservation here, but for me the One feature that BBpress has seriously lacked has been… The ability to complete simple/standard Administration tasks form the Backend.

Heck, some of them cant even be done at all…

Why is it that we’ve not been able to move a post from one Topic to another for 2 years (since 0.7’s plugin stopped working for 0.9a)? That seems a fundamental to me.

Why is it that we cant move/edit/delete/administer topics (and/or posts) from the Backend?

Matt, i realise that you’re trying to get to grips with a community that’s been downtrodden for the last year, and you’re re-galvanising what’s left, and that’s all very cool. But may i strongly, and humbly suggest, that BBpress to made to work as a forum and then we go about adding things?

I know that could sound a little condescending, but 0.9 had loads of plugins (they were horribly organised but they existed), and infact development of plugins and functionality for BBpress only started to slow down once the 1.0.3a debacle kicked off. Without getting all historical out of the 10 features you’ve asked us to vote for on the Poll, 8 of them existed and were working in a stable plugin for 0.9.

The realism is, BBpress has been a moving target for way too long and while its really great that you’re stepping in (and it is – thank you) there were 9 months of sheer Project Management craziness that have scared alot of Plugin Developers away.

Please, before you go adding any crazy “the public have spoken and they want …” features, how about getting a Project Plan, a Trac with actual data (and not a Trac that’s 4-5 months out of date as you’re trying to release software you’ve decided not to beta test, even though the last alpha had a huge number of bugs), and give us a platform to once again build upon.

Many Thanks,

Kevinjohn

ex- http://www.bbprogress.com

[citizenkeith]

@grassrootspa : Remember back in 2004 when Movable Type pushed everyone away with their new pricing plan? The result: BLAM! WordPress REALLY took off, fitting the bill as a viable free easy-to-install, easy-to-use alternative.

I remember it well. I was using Blosxom and decided to finally move over to MT right before they changed their pricing plan. I switched to WP and never looked back.

I hope Matt and all the developers will discuss this in the next IRC meeting.

[adamcap]

nvm I’m cool now, all I had to do was disable then reenable permalinks

[refueled]

@fmimoso

This version is completely rebuilt and is meant for bbPress 1.0+. If the older version works for you though, no need to upgrade.

[adamcap]

I changed my directory as according to sonza’s instructions and it worked…but I have a problem.

I had bbPress synchronization set up, but it’s not quite working anymore. It creates the new topic whenever I make a new post, but when I click on it in the forum, I get redirected to a “Nothing found…” page.

Other than uninstalling and reinstalling everything, is there anything I can do to fix this?

Thanks, Adam

[fmimoso]

What’s the difference between this one and the older? Changelog?

My (fast) interpretation of this theme: http://forumemprego.net/ (a work/job discussion forum).

Thank you.

[bmft2000]

Solved. Please see: https://bbpress.org/forums/topic/adding-location-to-users-post-info#post-6692

[timskii]

Cross-Domain Intergration

I’ve not seen anything about messy cross-domain integrations, so I thought I’d share my method. I’m using WordPress 2.8.6 with BBPress 1.0.2. Your mileage may vary on other versions. I suspect this method is not valid for 2.5/0.9.

The setup:

– example.com/blog

– example.com/forum

– example.org/forum

With shared user tables and database.

The config AUTH_KEY/SECURE_AUTH_KEY/LOGGED_IN_KEY should be the same for all (remember to add BB_ to the forum config files). Within the BBPress admin intergation, have the same auth/secure/logged in values for all forums (remember it’s the value shown within the WordPress options screen, not the values in the config files).

In this case cookiepath should be ‘/’ ($bb->cookiepath = ‘/’; // in bb-config and, define(‘COOKIEPATH’, ‘/’); // in wp-config). Set other $bb->style configurations as you wish.

Basically, everything is the same. Except: The Cookie Domain must be explicitly set**. And not always set to the same value.

In example.com/blog’s wp-config add: define(‘COOKIE_DOMAIN’,’.example.com’);

In example.com/forum’s bb-config add: $bb->cookiedomain = ‘.example.com’;

So far, so simple.

Now, in theory, example.org/forum can be set with $bb->cookiedomain = ‘.example.com’; // But I’ve not tried. Paranoid browsers would surely reject this. Instinctively having the forum rely on something that might look like a security risk is bad.

Instead, try adding this to example.org/forum’s bb-config: $bb->cookiedomain = ‘.example.org’; // Users will still need to log in separately when they switch domain, but all the other integration features seem to be fooled, with no adverse problems.

I’d welcome any feedback on this method. I’m still not sure this is the best approach.

( ** Not setting the cookie domain appears to work, until the user switches between domains – example.com/blog doesn’t simply fail to find a cookie set by example.org/forum, it may fail a fresh blog login until cookies are cleared. I’m not sure exactly what’s happening, but it’s messy.)