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

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

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

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

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

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

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

[refueled]

A new two column theme for bbPress.

Live Preview | Download

Matching WordPress Theme

More themes on the way!

[refueled]

The Carrington Blog WordPress theme now has a matching bbPress theme.

Live Preview

Download

Please report any possible issues in my forum:

http://www.refueled.net/forums/

I have more bbPress themes on the way!

[timskii]

You need to recognize that there are distinct groups of people with different answers. For example:

Plugin Programmers: Lack of stability of core behavior and data structure over the last year-or-so has become a real grind. A lot of 0.9 code partly stopped working in 1.0 – “partly” being particularly annoying, because those issues are harder to spot. For the rest of us, that grind means that plugins cannot be relied upon: There’s a risk of being unable to upgrade because a key plugin won’t work anymore. While you can argue “that’s inevitable”, if important features rely on plugins, a lot more care needs to be taken to ensure those plugins don’t break.

Server Administrators: One look at this forum tells you all you need to know. WordPress’s installation is accessible to people that know almost nothing about teh internet. In contrast, BBPress integration sucks: Manual, generally bewildering, and prone to unexplained failures. Worth adding here that there is a valid “no bloat please” option: BBPress is currently attractive precisely because it can deal with massive amounts of traffic. Not everyone wants to re-create the internet in one piece of software.

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

Obviously these groups influence one another, but it seems likely that this poll will be swamped by the desires of the Administrator group. Now, if nobody ever installs BBPress, nobody will get to use it or write plugins for it – so there’s no harm keeping the administrators happy. But don’t forget the other groups – they’re also important!

[micksay]

Hi all

I have had a look at bbPress to integrate with my WordPress site/s.

I really like bbPress – well done developers. However the only theme I can find that I really like is the one on this forum.

Trouble is I can’t find it anywhere – Can someone direct me to a download of this theme or let me know if it unavailable.

Thanks a million – Mick

[gerikg]

do you want me to look at it??? email me ftp and give me admin access.

[shaunkrd]

Hi, I’m brand new to bbPress and hoping to integrate it into my client’s existing WordPress powered site. One of the key requirements for the Forum is for registered and logged in users to be able to choose to post anonymously, maybe by way of a checkbox on the ‘Add New Post’ form. I’ve searched for a plugin to do this but had no luck.

Can anyone please offer any tips or advice? It would be very much appreciated.

[chrishajer]

What is a subforum? bbPress has forums as categories, where the parent is a category and cannot accept post, and can have just child forums. Is that sufficient?

It cannot be managed from the backend of WordPress – they’re separate pieces of software.

[codebuddha]

Hi,

I’ve had a search around but kind find anything relevant, bbPress looks perfect, but can it support sub-forums? Not seen any screenshots of the backend, can it be administered through the backend of WordPress?

Cheers,

[daudev]

It works when i login first in bbpress, then I’m logged in wordpress also, but first in wordpress and then in bbpress is not working!

[daudev]

I don’t need to clear the cache, just the cookies, but yes I did, i cleared both!

[grassrootspa]

I honestly don’t get this sudden push to make bbPress a WordPress plugin rather than continue as standalone software. There is so much potential for bbPress to grow and succeed in the 2010 standalone bulletin board market. Disagree? Think about this:

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.

One can make a strong argument that vBulletin is currently doing the same exact thing Movable Type did with their pricing plan snafu! (http://www.technologyquestions.com/2009/10/28/vbulletins-visceral-price-structure-angers-clients/) Check out this comment by donnacha which says even more: (http://weblogtoolscollection.com/archives/2009/12/11/bbpress-lives/#comment-1321740)

Throw in how complicated phpBB and vBulletin are compared to bbPress (not to mention how easy bbPress is to pickup for those familiar with WordPress) and there is a major bulletin board niche opening for Automattic.

This current bbPress 1.1 development push can really provide a great vBulletin alternative if it is done right. Shine up bbPress so it has some of the default features vBulletin and other boards offer (as OPTIONS in the admin interface) and we will see an exodus a la Movable Type to WordPress in 2004.

[gerikg]

Do you want me to look at it? and did you clear your cache after you just have one line?

[buddha-trance]

@ipstenu – I see… if there is duplication with deep integration, then as a plugin it would be lighter. I was also under the impression that a decision in this direction has been taken already, looking at the IRC chat…

I’ll continue to use, and love, bbPress regardless (and already use WP), though I’d prefer that it stayed as a standalone, because I think it has more potential this way, and it continues to cater also to those who are not interested in having to run WP at the same time. It is fair that opinions against the plugin idea be expressed and that Automattic becomes aware of the reasons behind them. This will allow for a better final decision.

It could be that the plugin idea is an impulsive one, based on the long lapse suffered by bbPress, and lack of a “grand” vision for this platform… or maybe they know what they are doing and the direction to take is to create an extra feature for WP, rather than a separate platform. In the end, of course, it’s up to Automattic.

Obviously, the decision is based on the potential number of new users. And the numbers increase if the platform is easy to use (a one click deal) and it integrates seamlessly with the blog. Though a plugin would deliver all this, it would also take away from a different crowd and future potential, and maybe there is a compromise. Some solution offering the one click deal like BuddyPress, while at the same time being able to run as a standalone and cater to the non-WP users who just want a forum. I don’t know if that is technically possible to achieve.

If theme integration is the only reason for bbPress to become a plugin, maybe there are alternatives, like something similar to the embed plugin https://wordpress.org/extend/plugins/embed-bbpress/, also mentioned in the IRC chat. One could build on that idea… and bbPress can be run as a standalone for those who choose to do so.

Maybe that is not the only reason, and the way things unfold will be (catered strictly to WP users + goodbye bbPress plugin developers and community):

WP(MUmerge) –> platform

BuddyPress –> plugin

bbPress –> plugin

[Maurice]

I’ve finally finished bbBlog 2.0. This plugin adds a blog page to you bbPress forum, using posts from a forum category, specified by you. (For those wanting to do some simple blogging without the WordPress installation hassle…)

You can download it here:

http://www.bbportal.org/bb-downloads/bb-blog2.0.zip

Demo:

http://www.bbportal.org/mssp/view.php?view=blog

Features:

– Total rewrite of the bbBlog plugin (1.0 compatible)

– Now a link to the blog is created under the “Views list” at the front-page (forum index)

– The blog items are now correctly filtering bold text, hyperlinks, smilies, etc (thanks _ck_)

– Comments() link now goes to the first comment made (thanks _ck_)

– You can now prevent members and guests to start blog posts (they can still reply)

– Now also showing topic tags

– Added sticky support: Topics marked as sticky now show on top on the blog page

– Admin display redesigned to match bbPress 1.0 admin area

– Blog post date uses the same Date Format as set in: Admin -> Settings -> General -> Date Format

– Now shows blog main category no subforums yet)

– Now pre-loads the selected (blog) forum in the dropdownlistbox in the admin area (thanks Ben L.)

To do:

– Set as start page, can be done by htcacces, how does WP do this?

– Generate a nicer error message when there are no topics in the blog like: “No blog started yet”

– Show some confirmation when settings are saved (this is broken in 1.0)

– Add pagination

– A “Read more” functionality. Show a Read more link after an amount of words set in the admin

– Add: You are not allowed to create new topics (like when locked topics)

– Sub category support (admin option?)

– Separate tags with commas

Enjoy!

ps: I am NO programmer, so don’t expect much support. Code suggestions and help (esp. with Read more and pagination) are welcome.

[daudev]

Still the same, logged in the wordpress, not logged in the bbpress but can do it.

only with define( ‘COOKIEPATH’, ‘/’ ); in the both files!

But i look very carefully into the cookies.

I found 2 differences!

First for wordpress cookies

login cookie is with name wordpress_logged_in_xxxxx and path /

and other cookies are with path /wp-admin, wp-content/plugins, /forum/bb-admin /forum/bb-plugins

and for the bbpress cookies are

wordpress_xxxxxxx and path /

and other cookies are with path

website.com/wp-admin

website.comwp-content/plugins

website.com/forum/bb-admin

website.com/forum/bb-plugins

I think this is the problem, but I don’t knew how to fix it, to have path without the host in bbpress cookies…

[grassrootspa]

If I had to rank them:

1) WYSYWYG / rich editing (tie!)

1) Facebook Connect (tie!)

3) Integration with WordPress (that login cookie thing really needs to be fixed)

The rest: interesting but the above 3=LOVE

4) Anonymous posting

5) Private messaging

6) Embed support, like videos

7) Email notification

Keyboard navigation

OMG, it would be awesome if ‘FB Connect’ was introduced into 1.1. This would mean it would only be a matter of time before ‘IntenseDebate Connect’! WOO HOO!

@ Olympus: I bet FB connect was a second or third choice for many folks

[Matt Mullenweg]

Just because there’s a plugin for something doesn’t mean it couldn’t be better integrated into core, in fact almost every feature in WordPress existed as a plugin first, the most recent example being the update system.

[chrishajer]

You have to log in there with a wordpress.org account, then you have some additional options. I’m not certain I see a way to create an account there, so create one at wordpress.org and then click “login” https://trac.bbpress.org/login – once that’s done, you will have the option to create a new ticket https://trac.bbpress.org/newticket