[frooyo]

@ _ck_

And how once I had hope for bbPress, it seems like that hope dead with 0.9 some 3 years ago

_ck_, I’ll definitely make a donation, if you were to pick back up 0.9 and run with it. Fix the known bugs in 0.9 and add in native page (front page & topic) caching for non-logged in users.

I’ll donate $100. Seriously.

[kikko088]

Hi at all, I try to put a value on input form (like bbpress.org form), I use this code

<input name=”topic” type=”text” id=”topic” size=”50″ maxlength=”80″ tabindex=”1″ value=”text” onfocus=”if(this.value==’text’){this.value=”;this.focus();}” onblur=”if(this.value==”){this.value=’text’}”/>

normally it work, now the problem is that I use also related post and I think it conflicts with the input code, infact if I active plugin the code don’t work, if I deactive the plugin the code work perfectly.

Can you help me?

kikko088

[_ck_]

Let me clarify for those that don’t follow.

BuddyPress is JJJ’s pet project.

Buddypress relies on WordPress, currently it’s technically a “plugin” to WordPress.

Buddypress (pre-1.3) uses bbpress standalone to manage it’s groups by using bbpress’s engine to manage forums (buddypress “groups” technically are forums with specific memberships to limit who can post to where).

JJJ sees that there are far too many layers and way too much code being loaded which is making buddypress too slow. So his plan is to more closely tie bbpress into WordPress, making buddypress faster.

His motivation is not to improve bbpress for the sake of making bbpress better. He doesn’t need the front end of bbpress at all for buddypress. He already manages it through buddypress.

So by reinventing bbpress to use wordpress’s core, he can cut out some of the bulk and make buddypress faster. BuddyPress is currently very slow and bulky unless you have a decent server and good caching setup.

Taking control of bbPress is a side project to help buddypress for JJJ and he’ll never convince me otherwise about his motivations.

Note I am NOT saying you won’t be able to run bbPress without buddypress, of course you will be able to (because that’s even less complicated) But that’s not his motivation or priority, at all.

@frooyo

0.7-0.9 bbPress standalone, high speed core independent of WP

1.0-1.1 bbPress relies on backpress core, which uses WP functions (150% larger)

1.2/2.0 bbPress relies on WordPress 3+ for it’s core (200% larger)

If you think hooking into the bulk that is WP 3.x is going to make bbPress faster, well there’s going to be a mighty big wake up call sometime soon. It will make page caching easier, but that’s good because it’s practically going to be a requirement.

JJJ’s only motivation to do this is because his pet buddypress project relies on the bulk of WP so the logic is might as well force bbPress to also.

TL;DR bbPress rewrite makes buddypress faster but bbpress by itself slower than 0.9/1.1

[_ck_]

While I won’t say it’s impossible, doing this currently with bbpress is difficult because of how everything internally is geared for newest last.

The post_position and other issues make this tricky. Even something as basic as jumping to the current post becomes a problem and has to be worked around.

Matt just didn’t think of anyone desiring it any other way when he first coded things in bbpress and now it’s legacy.

This is something I plan to address in a future (forked) version as well as parent/child threading. I’ve actually already accomplished it using plugins for a specific client but it’s overly complex and non-standardized.

[RedBull]

The two above posts explain how to accomplish this.

If you are using _ck_’s bbcode-lite plugin: https://bbpress.org/plugins/topic/bbcode-lite/

You can use basic html

<img src=”http://mydomain.com/pic.jpg&#8221; alt=”Pic1″ />

[VirtualityStudio]

is there a way to change the default gravitar to something custom? i’m not talking about a member’s gravitar, but the one that shows up if they have not personalized it. there is a plugin to do this in wordpress, but i haven’t found one in bbpress yet.

also something i noticed is that under the gravitar… where the member’s name shows up, when you click on it the link takes you directly to their website instead of to their member profile……….. has anyone come across that and figured out a way to change that?

does bbpress have a permalinks option like wordpress does?

thanks!!!!!

[zaerl]

sorry….I don’t know this is a support forum.

looks like a demo site…

Well the title of this page is “okiss test topic << bbPress Support Forums.”

[VirtualityStudio]

thank you so much!!!!!

[okissliu]

sorry….I don’t know this is a support forum.

looks like a demo site…

anyway…

Topic-reply-email is also not what I need.

Suppose mail-to-forum is what I want.

Any idea??

[Ashish Kumar (Ashfame)]

lol

testing live on support forums, thats new

[Paul Gregory]

frooyo, if you see point 7.4 of the draft proposal you’ll see that it shouldn’t negatively affect this fork. Kevinjohn reckons that the bbPress plugin code and community will be excellently managed by JJJ. The fork will not prioritise integration with WordPress, meaning the fork can instead concentrate on being lightweight and modular (with 25 modules bundled in).

So that’s alright then. Oh, except at least one supporter of the fork thinks that “we will surely need to keep it tightly integrated with WordPress to market it and make it a success”.

I don’t really understand what part of bbPress it is that Kevinjohn wants to save. To me, it seems that the main thing he wants to keep from bbPress is the developers…

Right now, we’ve alot of exceptionally talented Developers, and not so much in the PM/BA department, and I’m merely trying to fill the gap I can be most helpful in.

Kevinjohn, you’re not filling a gap in bbPress, you’re creating a new project with all-new gaps and filling one or two of them.

Throughout the document you say “we” and “us” to mean either the bbPress community or the fork community. I wonder if at some points you forget that there even is a difference – that a fork is a breaking away. A new software, not a saving of the old software.

I was attracted to bbPress because it is the forum from the WordPress people and I like the tags. It is a shame that the project hasn’t flourished like WP has. I can understand that people will be attracted to a continuation of bbPress, but without the ties to WP the fork needs to stand alone with a clear identity. Heck, bbPress’s main problem is that it has a muddied identity – is it 0.9, 1.0 or plugin?

You say the proposal is a draft one, but I’m not entirely clear when/if you plan to release an amended version. I think that what you need to do after your blue-sky and requirement refinement phases is to publish a detailed proposal, a manifesto for the project, identifying what parts you’re taking from bbPress and what parts need to be rewritten, and asking “who’s with us?”.

Indeed, that’s what I hoped to see in the draft document, but instead I was disappointed by the contradictions and lack of detail. However, a definition that is refined by community consent rather than one man’s vision may well be the best start, and this fork may excite me yet.

With the fork defined clearly in a proper proposal, people who were particularly attached to rejected ideas can leave, and other developers and contributors will join. Everyone on the fork will believe in the project. You’ll know how many people are truly committed, and you can plan accordingly.

And this process will probably inspire even more forks from teams and individuals.

I suspect that the best post-bbPress projects will be rewrites of the core, like _ck_ has identified is necessary for her intriguing project. And that’s fine. Take the spirit, learn the lessons. Don’t keep bbPress code alive for the sake of it, just write the best forum software you can.

Kevinjohn, it may not seem it, but I wish your project well.

[_ck_]

I totally agree that _ck_’s involvement is crucial.

Y’all don’t need me. I highly encourage you to keep going with the fork and there doesn’t have to be just one fork.

Remember, WordPress itself is just one (big) fork (of b2evolution).

I’ll be taking a sabbatical for the rest of the year starting next month or so as I have serious real-life things to deal with, and then *maybe* announcing my own project next year in the spring. Instead of a fork it will be a 50% or more rewrite of the entire core, fixing a few legacy problems. But it would not be available to the public for at least a year from now at the soonest and it won’t be fully backwards compatible.

It literally took me three years but I kinda figured out an indirect way of doing something like this. Part of the solution is so simple that I guarantee WordPress will “steal” the idea within six months of me publishing the code because it’s backwards compatible and a great idea that no-one else apparently has thought of yet for some mysterious reason. I’ve already tested a proof-of-concept and it’s one of those things that once you see it, everyone says “well that’s so simple anyone could have thought of it”. But no one has, yet.

[_ck_]

Looking good!

Now just put some margin on your #content box (for bbpress) and it will be set, ie.

#content {margin:0 50px;}

unless you want it to touch the sides.

Isn’t it great how easy bbpress can be shoved into existing pages?

[kevinjohngallagher]

it’s really “I want to manage a bbPress fork. Here’s my feature wishlist. Who wants to code it?”

Haha, thanks for telling people what I actually meant Paul, but I’m a half (quarter?) decent developer. Not as good as some of the great developers we have around here already, but but i’m more than happy to get my hands dirty when needed.

Right now, we’ve alot of exceptionally talented Developers, and not so much in the PM/BA department, and I’m merely trying to fill the gap I can be most helpful in. Apologies to all those that my document offended enough to take pot-shots at the language used.

It’s a high level effort of one person to kick start something bigger than himself, if its all the same with yourself, i’ll hold off on the low level fine tuning for quite some time, even though you raise some interesting points.

We’ve a software to save

[_ck_]

Looks great but frame is definitely not the way to do it

If the part on top is just html, copy the html into bbpress’s header.php and make sure you include the stylesheet.

If it’s being rendered by wordpress, just copy the final result (use the view selected source feature on Firefox, etc.)

Although I would not attempt what I am recommended unless you know html+css.

[Paul Gregory]

The title is “I want to fork bbPress”, but it’s really “I want to manage a bbPress fork. Here’s my feature wishlist. Who wants to code it?”

Kevinjohn, one of your 4 “Key Points For Discussion” is a matter you want to draw a line under (which was covered by the word “fork” anyway), and the other three are the areas that need the least discussion and the text itself explains why they don’t need discussing.

Indeed, a number of the points you make are a natural consequence of forking (eg ‘have a new website’) followed by some adjectives (‘have a better website’). However some of the ideas point towards a more substantial rewrite – rethinking categories and changing the database schema. The “blue sky” metaphor doesn’t exactly chime with a continuation of existing code either.

You prefer to fork 0.9 rather than 1.0 but you’re open to decisions from others.

You deride duplication of effort, yet you intend to fork bbPress.

You have “Focussing development efforts on the administration of the software, over front-end user needs” as a goal, which appears to mean that having a nice admin interface without any need to edit text files is more important than having a forum that people can use.

You may possibly have meant “needs” over and above basic functionality but if there are no fancy features on the front-end, how will the support forum “show-off”?

What sort of timeline are you attaching to this project?

[Ashish Kumar (Ashfame)]

Contact me – ashishsainiashfameatgmaildotcom

[ckeck]

The only comment I can make here is that they are moving forward and making progress…I don’t see much of that happening here unfortunately

[Ashish Kumar (Ashfame)]

Ease vs Performance

Tradeoff

[ph23man]

I’m on bbpress 1.1-r2537 and adding tags in topics displays this error:

---

Warning: Invalid argument supplied for foreach() in [path]/bb-includes/backpress/class.wp-taxonomy.php on line 1789

Catchable fatal error: Object of class WP_Error could not be converted to string in [path]/bb-includes/functions.bb-formatting.php on line 241

---

Please note I’ve substituted the actual file path with [path].

Sometimes only the 2nd error is displayed, sometimes both. I believe this problem was introduced in 1.1-r2530 because that revision changed class.wp-taxonomy.php.

The tags don’t update through AJAX, but after refreshing the page, the new tag does show.

[jurasiks]

https://codex.wordpress.org/Writing_a_Plugin

[Ashish Kumar (Ashfame)]

Yes keep it and just don’t show it. Better incase you want to do something about your data when you will need post times.

[Ashish Kumar (Ashfame)]

You can do that with deep integration by what MathiasB suggested or how your theme handles it. wp_page_menu or wp_list_pages()

Pros & Cons – http://blog.ashfame.com/2010/02/bbpress-deep-integration-advantages-disadvantages/

Deep integration – http://www.wpwebhost.com/make-bbpress-theme-match-with-wordpress-by-deep-integration/

Better one – Copy over the html of navigation to bbPress side. Its not worth using deep integration just for this alone.

[Ashish Kumar (Ashfame)]

Its very much similar to a WordPress plugin. Get started with those. Hope that helps

[MathiasB]

<ul class="topicmeta">