[Peter Westwood]

Westi didn’t comment on it in my email to him, though he did say that he didn’t know that bbPress was dependant on BackPress – and he’s the BackPress lead!! really lovely guy, but it hardly bodes well.

That isn’t a fair representation of what I said in reply to the email which was:

I was unaware that BackPress was blocking bbPress release this is the first I have heard of it.

Which is perfectly true – no one had tried to contact me directly about it before you.

I was and still am surprised that a point release of bbPress would be running with a floating external as trunk of BackPress is never guaranteed to be perfect code.

I would actually expect it to be run against the last revision that bbPress was release / against a branch with specific fixes as required.

If anyone want to be sure to get my attention for a BackPress issue then the extremely quite BackPress-dev mailing list is the best way – I read every email to that list promptly – https://lists.wordpress.org/mailman/listinfo/backpress-dev

[Anonymous User]

Hi John JJ,

thanks for your long statements here. For me – it’s great to hear about the future von bbPress. And even greater – bbPress has a team now!

Yeahhh…

[John James Jacoby]

All this has been said, and answered before. I just downloaded 2 plugins from the repo, and they worked fine enough. I am also of the opinion that this iteration of bbPress.org is the best looking and working one so far.

In Matt’s defense, I haven’t seen anything that Matt said qualify as berating, and the people he disagrees with, are people already on a verbal or moral offensive. Having been able to see through both sides of that looking glass, I can tell you with first hand experience that Matt is almost always on his A game, even if you don’t understand it at the time. But, this isn’t something I really want to get into because it just isn’t classy to do.

I get that everyone wants to hear from Matt and/or Jane. It sounds to me like you really want an apology more than you want anything else, because you’ve answered your own questions about how gaps in development have been filled in.

At the end of the day it’s free, open source software. Polarized or not, bbPress has a team now. If this can just be summed up as a years worth of pent up frustration coming out, I can understand that, but we’ve all been going at this for almost 3 days now, and I’d rather write code and fix stuff and make progress than rehash bbPress’s tumultuous existence.

P.S. – BuddyPress uses bbPress internally, so I’ve lurked for the past year+ and paid attention to the goings on. I just didn’t have the time or energy to have these discussions then. Now, I do, but there’s not much more I can say; it comes down to what we do about it. Like it or not, this is the hand we’ve been dealt… Time to make the best of it.

[kevinjohngallagher]

Indeed mate,

this is what I use, and it really is awesome.

I’ve managed to get my whole JS down to about 1-2% of what TinyMCE is.

A well written post too!

[pagal]

@kevinjohngallagher which keyword you’ve used for google to find this solution?

Why are you begging? I did not send you invitation to help me!

Sorry I don’t want to say any more, otherwise cris will close this topic.

[chrishajer]

Rescued this post from Akismet

[kevinjohngallagher]

OFC!

Thats daft of me.

if (! bb_is_user_logged_in() && basename($_SERVER['PHP_SELF'] != "bb-login.php")

{

header( 'Location: bb-login.php' );

}

Pagal, please mate, i beg of you.

Google for 5 minutes before posting these requests and telling everyone they don’t understand what you want, and never saying please or thank you.

We want to help bro, help us by using Google first

[mr_pelle]

You would get into a redirection loop with that. Add a filter to ignore bb-login.php in the if and it should work.

[kevinjohngallagher]

if (! bb_is_user_logged_in() )

{

header( 'Location: bb-login.php' );

}

Ok, so i’m guessing here, but whouldn’t those 2 lines of code work?

btw, i used google and that solution was the first one, i’m just copy and pasting

[mr_pelle]

In the script you linked, usernames and passwords are stored in clear in the php file: why do such a bad thing when bbPress has a database and encrypts passwords for you? Just login using its login form and that’s it.

[kevinjohngallagher]

I browse the net with javascript disabled, and JS is disabeld as standard on every PC at my current client (4th biggest uni in UK). All it does is slow people down who want to help

[kevinjohngallagher]

Hi Joe,

There is (or was) a TinyMCE editor back in the day, but TinyMCE is so far from Tiny it’s unreal.

I tink you’re also giving you users too little credit. A large percentage of people who use forums are used to seeing bbCode (though they may not know it themselves), but I always like to give my users buttons to press.

Latest update on my old plugin can be seen here:

http://www.fellowshipoftheding.org/forums/topic/shammy-changes

Please excuse the awful defualt theme and Play around with the text area.It’s 2k of code, or just uner 1% of TinyMCE.

I’d also advise to stay clear of WYSIWYG editors. People like to go absolutely nuts on those things. Everything bold and red and big fonts because “the world NEEDS to hear them”

and then ofcourse someone responds…

[pagal]

Oops! you are still confuse to understand my question

I also know very well that bb-login.php need for access the forums.

Let me tell you!

I’ve deleted the

bb-reset-password.php

register.php

xmlrpc.php

bb-admin/

rss/

from swirl-unknowns.php: lines 72-77.

Then I add this code in template’s login.php

http://pastebin.com/raw.php?i=MdzzJc3T

That what exactly I want

[Joe Gibson]

Greeings, all –

First off, I installed bbPress yesterday and I admit I’m impressed. A very well-thought-out piece of work. It dovetailed perfectly with WP without a hitch.

The one thing it obviously needs is a slightly better editor. Asking the readers to use actual code to italicize or bold a word is decidedly old-world.

I’ve just spent an hour on Google (and here) searching for relevant terms, such as ‘WYSIWYG’ and ‘TinyMCE’, and while there seems to be lots of chatter about the subject, I haven’t found anyone with a definitive “Do this, this and this” page that’ll replace the stock editor with something like TinyMCE Advanced or NICEdit.

Anyone know what the latest scoop is?

Thanks,
Joe

[mr_pelle]

Just remove the pages you do not need from swirl-unknowns.php: lines 72-77. You may add pages too.

Remember, though, that you’ll NEED bb-login.php to be swirl-immune in order to actually be able to access your forum!

[pagal]

thanks pelle

I know very well .htacess really easy, but for some reasons, I don’t want to use it.

Second your plugin also great, but need some functionalities, can you update it?

I need following action,

Complete protection not even show

bb-login.php

bb-reset-password.php

register.php

xmlrpc.php

bb-admin/

rss/

there should just a protect.php page for asking user name and password, If i enter correct user, pass then the forums should display, then I can access the bb-login.php and other Swirl-immune pages. otherwise not!

Thanks

[mr_pelle]

Why not using .htaccess? It’s easy!

By “I want to protect my forums directory”, do you mean you want to turn all your forums private? If so, use this plugin.

[Rich Pedley]

No the error is more likely to be in your CSS.

I tried adding

position: absolute;

width: 75%;

to your mainContent. This seems to on the right track, at least in Firefox.

Your disabling of right click doesn’t work in Firefox. If it had then I wouldn’t have been able to help.

[ColinBradbury]

<?php bb_get_header(); ?></p>

<p><div class="bbcrumb"><a>"><?php bb_option('name'); ?></a><?php bb_forum_bread_crumb(); ?></div>

<div class="infobox" role="main"></p>

<p><div id="topic-info">

<span id="topic_labels"><?php bb_topic_labels(); ?></span>

<h2<?php topic_class( 'topictitle' ); ?>><?php topic_title(); ?></h2>

<span id="topic_posts">(<?php topic_posts_link(); ?>)</span>

<span id="topic_voices">(<?php printf( _n( '%s voice', '%s voices', bb_get_topic_voices() ), bb_get_topic_voices() ); ?>)</span></p>

<p><ul class="topicmeta"></p>



<li><?php printf(__('Started %1$s ago by %2$s'), get_topic_start_time(), get_topic_author()) ?></li>

<p><?php if ( 1 < get_topic_posts() ) : ?></p>



<li><?php printf(__('<a href="%1$s">Latest reply</a> from %2$s'), esc_attr( get_topic_last_post_link() ), get_topic_last_poster()) ?></li>

<p><?php endif; ?>

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

<li<?php echo $class;?> id="favorite-toggle"><?php user_favorites_link(); ?>

<?php endif; do_action('topicmeta'); ?></p>

<p></div></p>

<p><?php topic_tags(); ?></p>

<p><?php do_action('under_title'); ?>

<?php if ($posts) : ?>

<?php topic_pages( array( 'before' => '<div class="nav">', 'after' => '</div>' ) ); ?></p>

<p><ol id="thread" class="list:post"></p>

<p><?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(); ?></p>

<p><?php endforeach; ?></p>

<p><div class="clearit"><br style=" clear: both;" /></div>

<p class="rss-link"><a>" class="rss-link"><?php _e('<abbr title="Really Simple Syndication">RSS</abbr> feed for this topic') ?></a></p>

<?php topic_pages( array( 'before' => '<div class="nav">', 'after' => '</div>' ) ); ?>

<?php endif; ?>

<?php if ( topic_is_open( $bb_post->topic_id ) ) : ?>

<?php post_form(); ?>

<?php else : ?>

<h2><?php _e('Topic Closed') ?></h2>

<p><?php _e('This topic has been closed to new replies.') ?></p>

<?php endif; ?>

<?php if ( bb_current_user_can( 'delete_topic', get_topic_id() ) || bb_current_user_can( 'close_topic', get_topic_id() ) || bb_current_user_can( 'stick_topic', get_topic_id() ) || bb_current_user_can( 'move_topic', get_topic_id() ) ) : ?></p>

<p><div class="admin">

<?php bb_topic_admin(); ?>

</div></p>

<p><?php endif; ?>

<?php bb_get_footer(); ?>

I think my problem is somewhere in here… if that helps…

[ColinBradbury]

I have managed to run the validator and sorted out some of the problems but its left others that part of the bbpress code.

Unfortunatly this hasn’t fixed my sites problem any other ides?

[kevinjohngallagher]

I think what I might be confused about, is if bbPress as it is today is close to exactly what it should be, what would you want it to do 2 years from now that wouldn’t add more bloat or slow it down?

bbPress0.9 is as good as any forum software out there, save for 2 things. Moderation and the Admin section. It’s crazily fast, secure, and extentable. It’s let down by lack of actions/filters, default theme and documentation.

bbpress1.0 is 50% slower and breaks alot of plugins but has some more hooks and an Admin section. Moderation is still the big thing, as is the default theme.

A clear out (archiving) and rethink of the plugin section and the creation of a new theme would make it very very useable.

Additionally both have also been let down by the layout/use of this forum, which makes finding information difficult; and a plugin section that doesn’t work.

Basically, all the feature requests we recieve, all go over the same ground – and can be covered by plugins. Most are covered by plugins (in a 90%) sort of way. With everything in Limbo there is no need to take things to the n-th degree.

From an honest to goodness Project management point of view, bbPress can be where we need it to be within 9 month – a year. But that time grows as we add more features (that we already have as plugins grrr) and less bug fixes.

So yeah we could fork it as is. But given Matt’s current desire to berate us (both the people here and the software) in public at Wordcamps, and his latest more… evangelistic approach to publicly taking umbridge at anyone he doesn’t like or disagrees with him; he makes the envornment out there relatively difficult to consider moving into, while intentionally hampering our efforts here.

If today, it’s good; then let’s fix up what we have to put out a solid 1.1 stand-alone, and when shift gears to focus on 1.2 as the plugin milestone.

Dude, we’re trying.

I mean, i know you know that

But in order for that to happen, we need the head honcho or “he who wont talk to us, only about us in keynote speeches”. All Keymasters, all of those who package things up and can edit the website… AutoMattic. The same folks who’re scrapping us for you.

I hate this looking like an US vs. THEM scenario, it just polarises people, and looks childish. But in honesty, “we” didn’t put ourselves in this holding pattern.

Additionally, putting out a solid 1.1 standalone will be tough and time consuming. We’ve 13 months of bugs, we’ve 13 months of backPress changes and potential changes in 3 releases of WordPress to contend with; there is going to be alot of bugs found in testing – and with Jane telling people that bbPress in its current implementation isn’t going to even work the WordPress.org forums and Matt telling people not to use the software we’re are hemmoraging people.

[kevinjohngallagher]

it also works for me

Then why the bumping?

Can I just add one page in root and include all template pages in this file?

No.

I’ll stick to create multiple pages in root for making multiple template pages?

Yes

[kevinjohngallagher]

Does a plugin (sponsored or otherwise) help new and updated versions of bbPress core get released to everyone that’s using it? No.

But then JJJ mate, nothing does.

We’ve not had a core release in over a year. It’s not like theres not been code added. Our only option was to add plugins to fix the functionality.

I’m not wanting to get too historical, but you’ve not been here in the trenches for a while bro. Your last non BuddyPress topic you opened was well over a year ago. Other than teh welcome back Matt stuff, you aint been here my friend. You’ve not been here during the “all your plugins won’t work – lets take stock after 1.0’s released” era where we entered limbo.

That limbo stayed when Sam left, so our bug fixes added to the core weren’t released.

That limbo was compounded when Matt came and announced no bug fix release.

Since then we’ve been adding to the core, and now Matts against us releasing (not that we can because we’re tied into BackPress which has only had 2 core updates in 5 months – instigated by us).

With respect, what you fail to realise here is that bbPress is very close to being ideal for alot of us. Not adding to the Core is not down to a lack of desire to add to it, but rather not able to jump through the gates of the gatekeeper – especailly as he refuses to talk to anyone about bbPress (unless insulting us publicly).

The major gripes that people have with bbPress have all been fixed. Yes 90% of them are currently in plugins, but they would be alot tighter and brought into line if 1) we weren’t in a holding pattern for over a year and 2) Automattic stopped fucking with the website so people could actually get at the plugins!!!

I’m not against you making an awesome forum plugin for WordPress (little p); I contributed a little to Justin Tadlock on his 2nd attempt (although at a high level) and I’ll be glad to help you on this project too. But make no mistake my friend – you’re views on bbPress have been tainted by the perception that Automattic has been (mud?) slinging for a while.

Now you may think i’m wrong on that, no worries.

Can i ask then, what advantages will this plugin have over the current bbPress, and what disadvantages?

I’m presuming that someone thought that out before making this decision

[John James Jacoby]

I have funded the development of dozens of bbPress plugins, almost all of which are available on the plugins tab as open source. They are just not released under my name, as I didn’t do the programming.

I have gone out of my way not to bash on bbPress on the forums, and to be supportive of the platform. I have 19 pages of posts on the bbPress forums, mostly answering questions from users.

I don’t think I deserve the comments you directed at me. That said, I wish you all the best with your new project.

Plugins are great, but they haven’t helped lead bbPress or contribute to the core project. Everyone appreciates any plugin that shows up in any repo, sponsored or not, yours or not.

I say this in the nicest way possible, but you shouldn’t have to go out of your way to be a genuinely nice person. Any and all contributions are always 100% awesome, so nothing I say ever is meant to mean anything other than that. The topic here is bbPress core, which means what comes in the bbpress.zip.

I’m sorry if you feel anything I said to you was off-putting. Just trying to put out this fire and answer questions with what I know to be true.

there is no way a bbPress plugin is going to be robust enough in 2010 for the public

Probably very true, and I wish I had the chance to start this topic; it sort of got started without us. We’re still going to work really hard to get something out there. Compatibility is the number 1 priority before this should even be considered to use with existing data.

Thanks for sticking to the 0.9 branch _ck_. I’ll be keeping equal eyes on the bbPress trac and BuddyPress trac, so if something crops up in 0.9 that needs committing or requires a security release, we can make that happen.

The trac is open to everyone to snoop through all of the code, and I welcome the criticism of the plugin branch 100%. I want it to be the go-to discussion forum software for every WordPress powered site, and I know that a team of people can’t do that by themselves, nor should they have to.

[John James Jacoby]

It’s hardly dismissive. Sorry you feel that way, but it’s meant to say that those of you that are upset, are also choosing not to hear what we’re saying anymore; you’re just mad and there’s not much I, or Matt, or anyone can do about that.

Over the past year, we’ve seen people request more features, people request less features, people want new leadership, people want to know the direction of the project, etc… The fact is that you can start developing the core right away by submitting patches in the trac. If you’re not doing that, then you’re not investing in the future of the platform, you’re investing in your own ventures which I’m happy to help with, but can’t be responsible for.

Sorry you feel it’s been badly handled, but to be quite fair, it’s partly because we’ve been directly answering everyone’s questions in this topic, and partly because this won’t happen for several months anyhow. This is big news to deliver, that’s why it hasn’t been delivered yet.

John, you can continue to spend as much money as you’d like on the future of bbPress, doing those exact same things the exact same way. If you’re satisfied with what you’ve invested in today, you will continue to be tomorrow. Nothing changes other than bbPress has a team of developers that are communicating to everyone now.

I’ve answered the ‘same name’ question a few times already, as have a few others. I mean nothing but the utmost respect when I say this, but there is nothing preventing anyone that’s upset here from developing bbPress core themselves and keeping up a stable branch if they see fit. It’s very much a meritocracy, so if you keep developing, you’ll keep climbing the ladder.

There’s also nothing wrong with forking it the same way WordPress did with b2 in the beginning. We’d rather have you on board, but if you just can’t and won’t be involved in the future bbPress plugin, then all I can do is keep repeating myself.