[paulhawke]

In theory you would make a backup of your my-plugins and my-themes directories. Then, delete the files in your existing bbPress install. Next step, run through the famous “5 minute install” of WordPress, and download the bbPress plugin and activate it. That’s the obvious part.

I would assume that a bbPress plugin would create a new top-level menu in the WordPress admin area. In a brand-new install, this would allow you to create the bbPress specific data structures in your database or to migrate existing bbPress data from an old version. After that step, the bbPress admin menu would switch to showing admin options for forums / topics / posts, etc.

My guess (if data structures remain largely the same) is that the “installation” of the plugin would merely write a WordPress option value telling the bbPress plugin what its database prefix is, and all the data already there would appear automatically.

Assuming that a bbPress plugin is connected to its data, it would need to be connected to the GUI somewhere. My guess is that you would create a WordPress static page and its content would be a short-code that the bbPress plugin replaces with its entire display.

[paulhawke]

@kevinjohngallagher

… but if you give the data-structure to a DBA or heck, a basic developer they’ll scratch their heads.

The datastructures underpinning both WordPress and bbPress are shocking to me, as a senior level developer. Just because you can do a thing doesnt mean you should do a thing; just because you have “*_meta” tables that store key/value pairs (that is, post_meta, user_meta, topic_meta, etc) doesnt mean that you should use them for absolutely everything. Tables like those are a commercial DBA’s worst nightmare.

There is no way to set any forum as read only, or hidden, or anything else. Forums don’t have settings, and why is that? because they’re exactly the same as categories in wordpress. Which suits the current need of one type of forum, and that’s one that has no need for parentage (such as this forum and the WordPress support forums).

bbPress was originally designed to be simple and lightweight. There are heavy-weight PHP based forums out there and I dont believe that bbPress was designed to compete. Lean, mean and simple seem to be the guiding principles, and it shows. The design of the code is very much the minimal working set you need for a basic forum. Problem is, people expect more, so you get to the point of needing a half-dozen plugins to reach the new “baseline” expectation. Suggests to me that certain plugins need to be [a] pulled into core and need some decent data-modelling done before getting released as “core” functionality.

Hey has anyone used XML_RPC to post to their forums yet? it’s awesome…

ROFLMAO

I’d like to stress i’m not advocating a massive change to the core, honestly I’m just up for discussion. I’m really just wanting to know people’s feelings or thoughts on this. Far too much data is not readily/intrinsically/obviously available especially when said data is on a predefined 1-to-1 relationship.

I would be willing to go through and document the database, including a nice clear diagram. I would also be happy to talk (deeply) about database design issues. It wouldnt be hard to pull together a patch to submit to Automattic to enhance the internal data structures. The issue I have though, is the number of plugins that would need to be massaged after such an event. Still, I’d be up for it.

@johnhiler

My general sense is that most of what you describe can be pulled off with plugins…

Adding the end-user functionality, yes, but the issue isnt so much the functionality as the data-structures a plugin needs to wrangle to accomplish its desired purpose. Right now the low-grade of data model design hurts.

@Marius-

I would love to have a dynamic sidebar I could add or remove things with ease. Have polls on the sidebar, not arrested in a topic, and maybe a chatbox instead of having an “Off Topic” category or thread.

I would like to see all of the major pages in bbPress be “widget enabled” – the “forums list” and the “topics list” simply be widgets, the heat-cloud for tags be another and so on. That would allow me to create an alternative display of topics, and drop it onto my own forum wihtout needing to hack the template.

Not to be too controversial here, but if/when bbPress becomes a WordPress plugin, we would get that functionality for free, pretty much.

I really enjoy the beautiful minimalism of BBPress, and I dont want it to get more complicated.

Amen! Preach it brother!

[deadlyhifi]

You could do this in the theme files.

In topic.php, around line 35 where the topic posts are listed, check if they’re logged in.

e.g

<?php if ( bb_is_user_logged_in() ) { ?>



<?php foreach ($posts as $bb_post) : $del_class = post_del_class(); ?>

<li id="post-<?php post_id(); ?>"<?php alt_class('post', $del_class); ?>>



<?php bb_post_template(); ?>

</li>

<?php endforeach; ?>



<?php } else { ?>



<li>Sorry, you must be logged in to view this - register now!</li>



<?php } ?>

[kevinjohngallagher]

So my wish to BBPress is to keep it simple, and make the hard things even simpler.

The hard things right now is adding new features, polls and many of the plugins requires alot of work to plug in.

Yes, thats what we’re talking about

Things are harder right now, and we’re trying to discuss them to make them easier.

Why not make these into widgets instead, as a sidebar?

I would love to have a dynamic sidebar I could add or remove things with ease. Have polls on the sidebar, not arrested in a topic, and maybe a chatbox instead of having an “Off Topic” category or thread.

Who had under 2 minutes in the “ZOMG i cant code so ignore data structurz & make me XXX feature” poll?

Yeah, i’m going to hell, i understand. Well i tried.

[kevinjohngallagher]

Kind of mate

In fact, I’m sure that a lot if not everything bbPress related could be done with plugins, but it comes to a point in time where a certain number of plugins are needed as standard for the forum to function properly.

I mean, “forum_is_category” and “topic_voices” are in the core now, but rather than being in the core tables, are still added and fiddled around with as meta data, so there’s always an INNER JOIN needed or additional SQL calls.

Call up a topic, in SQL, simple. How many Posts? there’s the data. How many tags? there’s the data. Heck, last poster’s name? sure! How many voices? oh hell no! I don’t keep that data here. It’s a secret!! Even though it’s a one to one relationship and it’s in the core, we keep that somewhere totally different, and you need to come up with a totally different method of getting that info. Ha, i mean, just cos it’s in the core, doesn’t mean it’s laid out prof… well we don’t use it on the WP support forums.

I’m not suggesting anything overtly Machiavellian at all, please don’t assume that and if I’ve given that impression I’m sorry (sometimes i jokes dont translate well), but if you give the data-structure to a DBA or heck, a basic developer they’ll scratch their heads. There is no really good reason for something like “forum_is_category” or “topic_views” to be held in a separate table as a data row, other than the one major forum where it’s not used. And that’s ok, he who pays the piper calls the tune, but that’s a core issue.

Realistically, thats not a coding issue, it’s a perspective issue. In order to get at the data, we need to call additional database information that we don’t need. Why do we need that overhead, even if it’s small.

Deep down, I can’t believe I need a plugin for my forum to be able to say it has posts underneath it though. That isn’t a bug and it isn’t intended, it just wasn’t thought of.

Same with Mass deleting of users / topics / posts. Or the ability to be able to add any form of ordering or filtering to any of them. Just wasn’t thought of.

I can understand a plugin with a specific purpose in this field (I’ve written one that marks any “.ru” and “.cn” user as bozo automatically), that’s cool. But I still think it’s daft that I have to manually search the user list every day for members with certain words in it – that stuff became bog standard on the internet a long time ago.

You know, once i search for (and find) a user, it then takes me 7 clicks and 4 different pages to delete the user. And there is no en-mass option. 7 clicks and 4 pages!!!! That’s not a ‘plugin or not plugin’ issue, that’s no PM/BA/IA/common-sense issue. I mean, really, having to leave the admin area to interact with a user? They got rid of that idea in wordpress almost 3 years ago.

I don’t want to flog a dead horse, but now that WordPress isn’t being ported to backPress (at least in the next version minimum), can you imagine the difference that rolling in a moderation suite or really any of _ck_’s non-fluff (smilies, bbcode) plugins into the core would have made in the 14 months between 0.9 and 1.0 being released? Hey has anyone used XML_RPC to post to their forums yet? it’s awesome…

=====================================================================

Is the concern that since the data design isn’t optimized for inherited forums, the query count will go up?

Yeah, kind of. It’s more that it’s already gone up, and as themes become more complex, it’ll go up again.

Let me give an example, and it’s a walkthrough – there could be code optimization.

To load the last forum poster/post (and btw this is for the singualar, not the child, which would multiply this by each child forum), you effectively are looking up the topic with the last date that’s attatched to that forum, and then look up the last post that’s attatched to that topic. Ok, so that’s 2 additional SQL calls for every forum thats displayed in the forum list.

(EDIT: actually, I’m confident it’s just 1 INNER JOIN SQL call now, but it’s still not needed really).

Now on a forum like this, or on WP support forums, thats only 6 forums. ok, so 6 additional calls total. Meh, not fussed.

But do you see how this doesn’t scale? On one of my forums, a football one, we’ve a “forum” for every football team in the UK. There’s no “latest” list, as we want people to talk in their own club’s section. Thing is that’s:

England

– Prem

– – 22 teams

– (Another 4 divisions of 24 teams)

Scotland

– SPL

– – 12 teams

– (Another 2 divisions of 16 teams)

It was facing meltdown every now and then, and I realised why, I’m placing an additional 150 SQL calls every time I want to display the list of forums, simply to find out the last post in a forum (and that’s NOT including the code needed if I was to respect genealogy).

Here’s the thing though, the TOPIC table has a column called: topic_last_post_id. Do you know why? Because it allows an inner join rather than an additional SQL call. Very sensible. Of course, it just wasn’t transposed to the bit that a certain support forums didn’t use.

If we applied the same logic to “forums” as to the topics, heck even put it in the meta data table, we’d add 1 SQL command in total when a new post was added, instead of 1 SQL per forum listed per pageload per user. Now, i could write a plugin to do that, but it’s not solving the issue, it’s just papering over the cracks in the datastructure.

I’m sure there will be some people reading this and they wont get that that i’m talking about data structure and optomization, and not specifically about “last forum poster”. I’m not advocaating category heavy forums or flat file forums, i’m saying that we’ve got some real data holes, and i think we should discuss them. How long until i’m told to leave bbPress because on some of my websites I use it differently to someone who has relatively few uesers and so isn’t hitting any of these issues? I bet not long.

I am not in any way having a go at any current/ Past developer/ development team/ Santa nor the Easter bunny. But the data is set up in a way in which it is ideally suited for 1 type of forum, and not for any of the others. Thats cool, but if bbPress is going to be a WPplugin, then this doesn’t matter. If there’s going to be a standalone version, then this sort of thing really needs to be looked at.

There’s countless examples of this; I’m just going with the one that people can replicate easily.

=========================================

I’d like to stress i’m not advocating a massive change to the core, honestly I’m just up for discussion. I’m really just wanting to know people’s feelings or thoughts on this. Far too much data is not readily/intrinsically/obviously available especially when said data is on a predefined 1-to-1 relationship.

Maybe if the data structure wasn’t so wishy-washy at points, there might be more plugin developers, or themes that looked a little more like the themes available on any of the other forums.

=========================================

John you’re also right that a “moderation suite” could be done via a plugin, my thoughts on that though would be “XML-RPC is a standard feature, but moderating my forum is a 3rd party plugin”?

I don’t think that making Forums read only on a selective basis is the work of a plugin, thats integral to how a forum works. Same with certain forums being visible to certain people.

The ability to move/sticky/resolved a topic/post from inside the admin area isn’t the job of a plugin, thats the job of the admin area. otherwise, what the point of the admin area

I’m sure there are things that I think should be standard that many other don’t; and vice versa. I don’t want bloatware, i’m not suggesting we copy phpBB or anything else, but i also think that just because we can have a plugin to do a job that we should always have a plugin to do a job. Also, just because something works with the current datastructure, doesn’t mean it’s even close to optimal.

=================================================================

Phew, longer than i wanted. Probably wrote many things which people will get annoyed at. Then again, i’m sure some idiot will be along in a minute demanding that we stop talking about this and include Facebook Connect, Polls, Smileys etc. I wonder how long that will take before my data structure conversation gets it’s first “ZOMG i cant code so ignore data structurz & make me XXX feature”.

[kevinjohngallagher]

Hi John,

I’m not proposing anything right now (maybe in the long term), but it’s not my purpose.

Its really jsut one of the topics i wanted to discuss at “Bob’s no show of an IRC meet” (it’s now official title until we hear from bob – who i hope is ok btw). I’m not a developer, i can code, but i’m very poor at it. I am though not bad at the bigger picture stuff, and this year i’ve had to move 2 forums away from bbPress (we’re only 7 weeks in), and i’m not sure that by the end of the year my “convertin to” will be more than my “moved away from”.

I’m totally cool if people dont agree, and i’m cool if people do. I’ve been wrong many times before, and will be again

But, um, please right more than “report it in trac”

Cheers

[kevinjohngallagher]

*life is too short *

[kevinjohngallagher]

Last Thursday, after an email conversation with 3 people I respect from this board, i decided to take a look at the old bbProgress code. With a bit of dusting off, the weekend has seemed quite fruitful. there are though, still a few things that bother me greatly, and the more I delve into bbPress and the ability to theme it differently or extract data in a different manner, the more questions it raises.

Specifically, bbPress is effectively set up to meet singular criteria, and really struggles to be adaptable. I’d go as far as to say it’s far to blog like in data structure. I’m confident that if i had a few days off work (and with no kids) that i could easily make a wordpress theme that would look and work exactly the same as bbPress. That’s fairly disappointing.

It’s disappointing because forums and blogs are very different in their make up. Forums have genealogy and many to many relationships, while blogs do not. It’s not just a case of a feature wishlist, or replicating features on other forum solutions, it’s rather the mindset that bbPress has evolved with. The “this works for us” mentality. Here are some examples:

Genealogy

bbPress makes no attempt to update parent forums. It’s a major flaw that leads to forum X having no information on forum Y at all, even though they are directly related. Instead, in order to find this out, a plugin that makes numerous SQL calls every time a forum is loaded (and for every forum listed) must be created to fake this basic functionality.

Should your forum have no parent/child relationships (such as this forum and the WordPress support forums), then the issue probably hasn’t arisen.

This somewhat forces bbPress forums into linking via topics/posts rather than forum structure. I’m neither for nor against this, it definitely has its advantages for some forums, but for larger more structure forums where parent/child/child relationships are helpful, this quickly becomes very difficult when it doesn’t need to be.

More importantly, by only storing information in this blog-esque flat-file scenario, we’re keeping theme development very tied into plugins for even the most basic of information such as:

Forum – > Last Post

I’ve raised this one for a year and a bit now, but its a great example (imo).

Lets say, i run a review forum for restaurants in Pennsylvania (i don’t):

Forum

---

Topics — Posts — Last Post

=======================================

USA

---

0 topics – 0 posts – No posts

– Pennsylvania

---

0 topics – 0 posts – No posts

– – Philadelphia

---

0 topics – 0 posts – No posts

– – Pittsburg

---

0 topics – 0 posts – No posts

– – Allentown

---

0 topics – 0 posts – No posts

– – Scranton

---

0 topics – 0 posts – No posts

– – – chinese restaurants– 1 topics – 1 posts – nom nom nom by fat albert

– – – french restaurants— 3 topics – 42 posts – i hate snails by Jody

– – – italian restaurants— 9 topics – 99 posts – i love pasta by Bob

Ok, so i hope this will illustrate the problem. According to bbPress USA, Pennsylvania, Scranton all have 0 posts in them, but that’s not true. They are parents in a forum sense, and have 13 topics and 142 posts under them.

The issue as a theme developer is that if you attempt to emulate the look/feel of any other forum software out there, then you have to make crazy complex SQL calls just to display the data that your users are used to. Or worse, (as i’ve shown in some real world examples) display “No Posts” on a forum that actually has loads of posts, just divided into their children.

I’m not saying that one way is better than another, but right now we’re stuck with only having data that fits one type of forum, and that’s one that has no need for parentage (such as this forum and the WordPress support forums).

Definition of Forums, Categories etc.

bbPress, in an attempt to roll in some backward compatibility of a plugin, included the “forum_is_category” meta. The issue here is that it’s a 1 to 1 relationship, a boolean, a yes/no; and yet we’re holding this data in the meta table, rather than the forum table.

What this means is that anyone pulling a list of the forums in a plugin, then has to compare each one to a different SQL against the meta table. Why isn’t their just a column in the forums table “is_a_category”? or even better, “forum_is_category”, and then no code would need to be changed in the existing “bb_forums()” loop. Why? well because if a forum doesn’t use categories because it has no need for parentage (such as this forum and the WordPress support forums) its not something they’re going to run into.

But of course, there is a bigger issue. A forum can only be a category or not a category. A Category is described (and categorised as) being Read Only and having Sub-Forums. The thing is, what if I want to make a forum read-only, but it already has child forums (for example, i want to make Philadelphia read only because i’ve divided the city into North/South as sub forums), would that mean that i want Philadelphia as a category? no. But that’s the bbPress definition.

bbPress has no way to add any form of settings or meta data to a forum. Forum A is treated the exact same way as forum B and forum Z, when in reality for forums rather than blogs, that’s not always the case.

There is no way to set any forum as read only, or hidden, or anything else. Forums don’t have settings, and why is that? because they’re exactly the same as categories in wordpress. Which suits the current need of one type of forum, and that’s one that has no need for parentage (such as this forum and the WordPress support forums).

A forum (n to n) not a blog (1 to n)

This is where the problem starts to expand. bbPress’s 1 to 1 reliance does not play well when attempting to assign other meta data. This really starts to throw issues as soon as your board becomes a certain size. Moderation is a nightmare because the whole n-to-n abilities of every other forum is non existent. Users to groups, groups to permissions on a forum per forum basic, rules on a forum per forum basis and per user and/or group.

Outside of WordPress integration the most common questions on this board are “how do i do X basic forum feature (read only, hidden forums, assign moderators etc)” and the answer is never good.

These are not issues for bbPress’s major role (the WordPress support forums), a forum with 5 sections, no parentage, and everyone is a WPuser already. But if you look around any of the “powered by bbPress” forums, and then look around any of the not-powered by bbPress forums, there are amazing differences. Those differences suit Automattic, and they may suit you (awesome if they do), but why do we continue to code/design/develop in a static flat-file based way that only meets the needs of one system, instead of assigning data in an N-to-N structure so that people can theme/develop/forum their own way?

My name is Kevinjohn Gallagher, and this is the 3rd February in a row i’ve written this (or v similar) post. I fully expect to be called an Angry Celt, “concern trolling” or whatever else is popular these days. In honesty, i’m holding my hands up to not being a great IA or Developer, and hoping that if i can raise these issues maybe we as a community can solve them.

Have a great day!

[wpcode]

when I logout, it display the error code below:

pls help me! what’s wrong with my site?

Database error: [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘LIMIT 1’ at line 1]

SELECT * FROM bb_online WHERE user_id = LIMIT 1

Caller: bb_logout, do_action, call_user_func_array, online_logout

Warning: Cannot modify header information – headers already sent by (output started at /home/whg/public_html/wpcode/bb-includes/backpress/class.bpdb.php:569) in /home/whg/public_html/wpcode/bb-includes/functions.bb-pluggable.php on line 232

[Taeo]

Heya,

I posted in a thread a while back about a project I was working on with bbPress and some people were interested in it so now that it is complete I thought I would share.

WoW UI Gallery

I have created a community website for enthusiasts of custom user interfaces for World of Warcraft. Users make a post consisting of a description of their UI, screenshots, and other various meta data. Other users can comment on and rate the UI’s that have been posted. And of course they can discuss further in the forum.

Aside from some small modifications to the profile page code (why isn’t there a template for this?!) all of the additional functionality has been achieved through plugins and theme code. I wrote most of the functionality into a plugin I am called bb-gallery. I am also using ajaxed-quote (detective), bb-ratings (mdawaffe), bb-topic-views (wittmania, _ck_), my-views (_ck_), and front-page-topics (_ck_, mdawaffe).

There were a few snags here and there but overall I was very happy to work with bbPress and it will definitely be my first choice for any other forum project in the near future. The site has been up for less than 18 hours at this moment but I’ve already gotten over 1000 page views and a promising lead for a possible “digg” effect of sorts.

If any of you are WoW fans I invite you to join the community!

[chrishajer]

If you can log in at WordPress, navigate to the forums, still be logged in, and then log out and do the reverse, your cookie integration is fine. To test the rest (the reason you included wp-load.php) try using a WordPress function (wp_list_pages()) in a bbPress template and see if it works. Those would be good tests.

[chrishajer]

Is this require_once('/../wp-load.php'); inside PHP tags near the top of your bb-config.php file? Like this

<?php

require_once('/../wp-load.php');

/**

* The base configurations of bbPress.

.

.

.

?>

If it is properly inside PHP tags, then there might be something wrong with the syntax of that line.

The other thing is, chances are the file is NOT located at the root of the server. You have it starting out here: / – which is the root. Might look more like this:

require_once('../wp-load.php'); if wp-load.php is located one directory up. You can also use the full path to the file, if you know it. Like this:

require_once('/var/www/htdocs/wordpress/wp-load.php');

Looks like the path is wrong there if you have it starting with a slash, at the root.

[kevinjohngallagher]

Your error log is something you get form your hosting people. If your server has a Control Panel of any kind then there should be a link to it on there. If you can’t find it, ask your hosting provider

[thelobbyist]

Using bbPress 1.0.2 and WP 2.9.2

Where would I find my error log? And I’m assuming you mean when I add the deep integration code into the bb-admin.php file? Because when I don’t add the deep integration code snippet everything works flawlessly.

[Dailytalker]

@Il Gatteo

Regarding smilies…how about this smilies:

http://www.dailytalk.ch/forum/stammtisch/ddd/

You need the bbpress smilies plugin and the smilies you want. Than you can replace the ugly wordpress-bbpress smilies with the smilies you want. Its easily done.

Regarding polls: Take the plugin “bbpress Polls”.

What I need is a much better BB_code toolbar Plugin and a facebook connect plugin….

[Il Gatto]

I have many ehehe

from most important to least important:

1) Better BBCode (like PhpBB, VBulletin or any other forum) + Quoting (“user says”)

2) Better MULTILANGUAGE SUPPORT!!! (this would rock – like qtranslate in WP)

3) Advertising manager (a port of the popular Advertising Manager plugin in WP would do)

4) User profile pages (with many customizable profile fields, etc)

5) User photo galleries

6) Better moderation tools

7) Some social networking tool like Facebook connect, OpenID connect, Twitter feeds, etc.

Better Smilies

9) Better User Avatar System (Bavatars does a neat job though)

10) Better Integration with WordPress (sometimes sucks)

11) Customizable Forum icons

12) User can post Polls / Surveys

13) Event calendars…

[Marius-]

That entire code` should I find those #codes in the stylesheet and plase the // infront of?

Are you saying that I dont need to delete anything from the php files if I use this code. I just let everything be, and place that in the CSS?

–

I tried putting it in Firebug, and nothing happened.

[Ashish Kumar (Ashfame)]

email me ashishsainiashfame[at]gmail[dot]com

You can see my bbPress resource page here – http://blog.ashfame.com/bbpress/

[Ashish Kumar (Ashfame)]

email me ashishsainiashfame[at]gmail[dot]com

[paulhawke]

Getting back to what @frooyo asked at the start…

Since the future is that bbPress will be a plug-in of WordPress, does that still allow bbPress itself to have plugin capability? Because essentially then, any plugin of bbPress would be a plugin of plugin to WordPress.

Plugins would be managed in a single interface. They would use the regular WordPress functions to add admin-area functionality, and to add action hooks and insert themselves into the filter processing. The issue is which actions and which filters are registered in a given plugin. As bbPress is migrated to being a plugin the developers will make sure that it will broadcast its own actions, separate from WordPress, when it makes sense to, and share action/filter hooks when it makes sense. For instance, I could see the “talk like a pirate” plugin for WordPress being shared between bbPress and WordPress on a given site.

In addition to action and filter hooks being distinct between the two systems, or shared in certain cases, it’s entirely possible to write code that a plugin registers with, separate from the main WordPress. Take for instance the current “Topic Icons” plugin that allows other plugins to register new “rules” on how to apply icons. This capability allowed the “Topic Icons” plugin to support skinning the “Support Forums” icon set without ever needing to be coded into the core “Topic Icons” plugin – people who dont run “Support Forums” never need activate that piece of code. What I’m getting at here is that one plugin can register and talk to another – there just has to be a little care about how its done; if bbPress becomes a WordPress plugin, there’s nothing to stop it having its own sub-set of plugins specific to it.

How would the Admin interface look for bbPress within WordPress

Its very easy to add a new top-level menu item in the admin interface, its just not something plugin writers normally do. In the case of bbPress, I could see a “forum” menu being added that then contains a sub-menu of management pages specific to bbPress. That said, we get user and theme management for free from the main WordPress.

@bobtheman – you asked an interesting question

on a side note, this sorta makes you want to ask yourself, will every project that automattic picks up be transformed into a worpdress plugin?

It’s been said that “when all you have is a hammer, all the worlds problems look like a nail”

The fact is, WordPress is a thoroughly versatile foundation to build upon. To quote another software engineering saying, “it isnt code re-use the second time some code gets used – that’s just a happy accident. Code re-use doesnt happen until the third and subsequent time.”

What do I mean here? Simply this: the foundations of WordPress (user management, theming, admin, plugins, etc) are great. They make a solid basis for building from. BuddyPress started down that road and by a “happy accident” made use of the features. Now we are looking at bbPress and saying “wow – code re-use!” but there are large slabs of code that will not be used when you’re a bbPress user/admin. The thing which needs to happen is to look, now that a third (WP, BP, bbP) project is building on the same backend, and refactor the truly common code into a modular WP-Core that is lean-and-mean, and the additional functionality builds upon. We have an opportunity to drive the architecture of WordPress into a better place as bbPress becomes a plugin.

For instance, what if I want to swap out and run my WordPress against Microsoft Active Directory for all the user management thereby gaining single-signon in a corporate shop? Impossible right now, but if the core is more modular, maybe it would be possible. If the core were more modular, then an install of bbPress need not drag the entire WordPress codebase along with it.

[Marius-]

To be more specific. I use Kakumei theme, so what files include tag codes?

I know post-form.php, front-page.php probably has them. But which others?

Is it safe for me to just delete those lines from these files? Or should I do something else?

[johnhiler]

Tags is part of the bbPress core, so you can’t just turn them off by deactivating a plugin.

There are two ways to do it that I’m aware of:

1) Remove the tag code from your templates:

Tags only appears in a few places in your templates though, so it shouldn’t be too hard to remove!

https://trac.bbpress.org/browser/trunk/bb-templates/kakumei

Tag code appears in the following template files:

tag-simple.php

tags.php

tag-form.php

topic-tags.php

topic.php

There are descriptions of each template file here:

https://bbpress.org/documentation/themes/

2) Hide the tag fields in your stylesheet:

https://bbpress.org/forums/topic/remove-tags

Good luck!

[Marius-]

I want to get rid of Hot Tags. Im not just talking about the menu on the left, but completely remove it.

Remove:

-Hot tags menu

-Listed tags in topics

-Tag box in reply-form

Is there an easy way to do this?

I now have 100 members on my forum, and nobody uses it, and its just ugly.

Is tags a widget, or is it so hard coded into wordpress that I have to edit loads of files to get it away?

Should I bother removing this now, or will this be easier with an updated bbpress, thats perhaps coming sooner than I happen to know?

[talatorre]

aprendedor

This is how I understand the code:

function pages_table() {

global $bb; //calls global variable

// Compute the name of the table we need to query

$table = $bb->wp_table_prefix; //this calls the wp prefix from the wordpress integration settings, ex: wp_

if ($bb->wordpress_mu_primary_blog_id != “”) //checks for a WPMU id in the WP integration settings

$table .= $bb->wordpress_mu_primary_blog_id.”_”; //appends the id, ex: wp_1

$table .= “posts”; //appends “posts”, ex: wp_posts or wp_1posts

return $table;

}

To answer your questions the code works no matter which type of WP flavor you are using

[bobtheman]

“My concern is that by making bbPress a plugin of WordPress, it’s DRASTICALLY moves bbPress away from the original goals because we already know that 1) bbPress would be *more* code, 2) much more complicated, 3) definitely slower given you have to load now WordPress and 4) fundamentally, this is not putting the user first.

Just my 2 cents … also, thanks in advance for answering my questions above “

I agree, making bbpress a plugin to WP is not in the best interest of bbpress. If this happens, our existence and success would be contingent on wordpress. The moment bbpress becomes a wp plugin, we are no longer a forum solution but rather a wordpress forum solution and we limit ourselves to just that.