Search Results for 'bbpress'
-
Search Results
-
bbPress 1.0.3, and bbPress 1.1, are still being actively developed. Once those versions are available, what /more/ would you want bbPress to do on its own?
Honestly mate? Bug fixes.
Some big bugs that we’ve had for over a year have been bumped because Matt told us we weren’t to have a bug fix release, and instead were to roll out a release with 2 new features instead.
8 weeks ago Matt started deleting milestones from Trac. Didn’t tell anyone. Took him 3 weeks to reply to emails wondering why.
bbpress1.0.3 was ready over 3 months ago (save for a Backpress bug we could live with/patch ourselves). Matt decreed we’ve not to package it and give it to folks as an alpha or even an actual release. We have to wait for 1.1 and the next version of BackPress to be ready. In order to speed that up, we’ve had to bump loads to 1.5, which now isn’t going to happen.
This is the end of the line for the current implementation of bbPress.
Yes. Just like 2.9.2 was the end of the road for the 2.9 branch of WordPress when 3.0 came along. I understand the obvious differences, but at the end of the day, it’s just another day.
Two differences here though bro.
1) No-one has actually said that yet.
2) The new bbPress plugin is a totally separate project, being run under the same banner. Other than being able to import the data from the existing project, its totally different. It doesn’t even have the same requirements. Or any of the same code.
This isn’t resistance to change, nothing is being changed, it’s being replaced. And someone needs to be very clear and categorical about that. This is very very different from going from WP2.9.2 to WP3.
This is effectively a hostile takeover. The people with the keys to this website are handing the reins over to new management; while everyone is speaking in positive PR/Management speak. I’m not saying that the hostile takeover won’t be benefitial in the long run or benefitial to more people than currently use this product – i’m just syaing that hostile takeovers breed questions and uncertainty. Some of that uncertainty needs to be managed.
I know that you’re a real positive guy JJJ, and I’ve said before it’s infectious because you deliver, and deliver with a smile. I can think of no-one better to deal with this.
But the horse has bolted, the cat’s out the bag, the jig is up; and it’s a shame your left here answering questions, but in honesty – to some of us this is our livelyhood and we really need definative answers that are crystal clear so we can quote them as needed and make business decisions that affect our lives.
I am sorry tht you couldn’t have done this in your own time and in your own way. Your handling and galvanising of the BuddyPress community has been great, as I’m sure it will be here as well, we just need to get over this hump so that we can work with you
Some time ago I came across markItUp! – a markup editor written as a jQuery plugin. It can be attached to any textarea, providing editing interface to it. The best thing is that it that interface can be totaly customized and there are many sets that are ready to be downloaded, among which is a bbCode set.
I’ve been using _ck_’s bbCode toolbar plugin but it lacked buttons for adding colors and changing font-size, so I decided to swap it for markItUp. It turned up quite nicely and the code is dead simple. Here it goes:
First, download markiItUp, along with the necessery bbCode set
http://markitup.jaysalvat.com/downloads/download.php?id=releases/latest
http://markitup.jaysalvat.com/downloads/download.php?id=markupsets/bbcode
http://markitup.jaysalvat.com/downloads/download.php?id=addons/bbcode/colors
* the color set is seperate by default, so you’d have to merge it to the bbCode set later
Upload the downloaded files to a directory on your server (my choice was
my-plugins/scripts) and include them in your template. You can do that usingbb_headinfunctions.phpof the theme (bbPress 1.x) or as a mini plugin (bbPress 0.9.x)/*
Plugin Name: markItUp! for post form
*/
function mark_it_up_init() {
echo '
<!-- markItUp! scripts -->
<script type="text/javascript" src="' . bb_get_option('uri') . 'my-plugins/scripts/markitup/jquery.markitup.js"></script>
<script type="text/javascript" src="' . bb_get_option('uri') . 'my-plugins/scripts/markitup/sets/bbcode/set.js"></script>
<script type="text/javascript" >
jQuery(document).ready(function() {
jQuery("#post_content").markItUp(mySettings);
});
</script>
<!-- markItUp! stylesheets -->
<link rel="stylesheet" type="text/css" href="' . bb_get_option('uri') . 'my-plugins/scripts/markitup/skins/simple/style.css" />
<link rel="stylesheet" type="text/css" href="' . bb_get_option('uri') . 'my-plugins/scripts/markitup/sets/bbcode/style.css" />';
}
add_action('bb_head','mark_it_up_init');* Or you could just add that code to your
header.php(without the PHP function wrap-up).And last but most important – include jQuery before markItUp! in your template. That is best done using
<?php bb_enqueue_script('jquery'); ?>You can see it in action on the forum that I manage:
http://comicsbistro.net/forum/?new=1
Hope that this will be useful to someone
Cheers!
To turn the whole forum private: https://bbpress.org/plugins/topic/swirl-unknowns/
To hide single forums: https://bbpress.org/plugins/topic/zaerl-visibility/
P.S: why on earth do you want your site to be invisible to websearches? Are you planning something evil??
Probably.
I just feel sorry for all the plugins developers…
No. Not probably, and not at all.
So far everyone’s managed to keep this pretty light and well mannered, and the easiest way to keep that pace is to not fuel any fires.
And what about non WordPress users?
Non WordPress uses can’t use VaultPress, or BuddyPress. As the plugin is being developed, if you have suggestions on how it might still be able to sit on top of BackPress, I’m open to building that into it also provided it doesn’t overly sacrifice performance in other areas.
There’s a lot of goals we hope to hit by doing this, one of which is allowing bbPress to be pocket sized and extensible from within WordPress, so that it can do other unique things that existing plugins have needed to jump through hurdles to achieve. Dedicated user forums, user groups, post/topic syncing, better BuddyPress integration, attachments, revision history, proper moderation, etc… If you don’t need those things, you can turn them off in WordPress all the same.
I know that my vote isn’t the popular one amongst the dedicated bbPress lovers, and there are lots of logistics to make this a smooth transition. With this initiative we have more people dedicated towards making this smooth and successful than bbPress has ever had in it’s 6 year history. That along with complete support from the original plugin author means it’s the next evolutionary step in bbPress’s journey.
I’ve been involved in too many hobbies to not know what it feels like when the version of something you love is discontinued, and something else replaces it that just ain’t the same. Cars, turntables, computers, cell phones, crock pots… You name it, I’ve dealt with the expiration of one thing, and moved on to the next.
The major difference with us and bbPress, is you all can help make the plugin do what you need it to by contributing code with patches. I couldn’t force Honda to bring back the del Sol CR-X if I tried.
Hey guys,
I’ve started sniffing around bbPress a few days ago and I wanted to integrate it with WP. I’ve simply followed the installation procedure and filled in all the data, integrated the databases and cookies and that works just fine.
When logged in on WP – I’m also logged in on bbPress.
However, I cannot access the admin panel of bbPress. When I try to do that I just get redirected to the forum’s homepage.
I’ve tried solving this by installing a few WP plugins to use the bbPress interface on WP and here are the errors I got:
Warning: require_once(/home/rockstar/public_html/rockstarplr.com//forums/bb-admin/admin-functions.php) [function.require-once]: failed to open stream: No such file or directory in /home/rockstar/public_html/rockstarplr.com/wp-content/plugins/bbpress-admin/bbpress-post-admin.php on line 9
Fatal error: require_once() [function.require]: Failed opening required ‘/home/rockstar/public_html/rockstarplr.com//forums/bb-admin/admin-functions.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/rockstar/public_html/rockstarplr.com/wp-content/plugins/bbpress-admin/bbpress-post-admin.php on line 9
The forum is located at http://rockstarplr.com/community/
I’ve checked for that file, admin-functions.php and I don’t have it anywhere. Seems like the plugin can’t load that file because it doesn’t exist. Can anyone help me with this?
Thanks!
Could anyone tell me if it is possible to lock my bbpress forum so that there is one central login page. I want to reserve my site for members only.
Furthermore, is it possible to hide my site from webserches?
Thanks in advance
My point is that 99% of people won’t know the difference.
If I choose to download and install a development version of Windows 8, I do so totally at my own risk. If I get burned by it, I can’t be mad at Microsoft.
Same rule applies to bbPress.
The development of the future plugin version does not impact what is available today. You either choose to be involved in that future, or you don’t.
Me saying (the plugin) is only in reference to conversations where it isn’t clear what we’re talking about. By the time anyone should realistically be trying out the plugin branch of code, we won’t need to use code words to talk about the differences.
One day hopefully in the not too distant future, we’ll flip this very site over to using the plugin without telling anyone, and when there is 0% difference in functionality and presentation, it will be time to start downloading it.
P.S. – I’m about 15 minutes off from committing they very primitive framework I have laid out, in case anyone wants to keep tabs.
Morning all,
I know I’m a vocal one (even more so with just 3 hours sleep), but I think there’s 2 things we need to accept here:
1) JJJ isn’t making these naming decisions himself
and
2) bbpress (standalone) isn’t going to be suported or developed any further. This isn’t a side by side project. It’s the end of bbPress without being a WordPress plugin.
In large part, thats why the name is being kept as bbPress. It’d be hard to convince people to undertake yet another compltely new piece of software after the debacle of bbpress0.9 and 1.0. So instead write something completely new, call it the old thing, and release it as an “upgrade”.
Given that we’re reliant on Matt to release bbPress1.0.3/1.1, and he’s been so active in the last 5 months, it’s hard to see how the next month(s?) are going to resolve themselves. And thats not a reflection on JJJ or PeteMall.
1) None of us are worried about the name from a personal view point, it could all could be renamed Bob’s Super Duper Forum for all we care ;-] , only form the perspective of not confusing users.
Then bbPress it is.
Doesn’t it sound strange that you, JJJ, had to specify “bbPress (the plugin)” everytime not to get users confused? -_-” I’m not a native English speaker (I’m Italian), so I can tell you people are going to be confused by this!
I loved this line by KJG:
So to clarify for those who are confused:
bbPress for BP is bbPress with bPress without bPress.
But that’s not the same as just bbPress, the bbPress plugin, BP,
bPress, BuddyPress nor BackPress.
Is it any wonder, honestly, that people get confused?
Just try to think what would a newbie find googling bbPress+plugin…
Anyway, I think there are some users, like me, not really looking for a WP-integrated forum software, but just for a standalone forum: do you all really want us to “use different software instead of bbPress”? That’s odd…
So bbPress1.0.3 isn’t going to be released? What of 1.1?
My involvement in the 1.0.x/1.1 branches is limited, but if I had to guess (without checking) 1.0.3 will happen if there’s anything important to push out or there’s some kind of delay with 1.1, and 1.1 will happen before it’s a plugin for sure.
Who makes these decisions?
Honestly, whomever is in charge of the project sets the roadmap. If there’s no lead developer, then there’s no release schedule, because everything is just stagnant. I recently said something similar over on the BuddyPress blog regarding activity and how it only serves to perpetually foster more activity. Ultimately, I defer any major decisions about bbPress back to Matt, if anything simply because numero uno through numero un hundred are almost all his. If someone comes along and starts ripping up the trac and contributing patches and just overall making bbPress (the plugin) awesome, and for whatever reason I’m unable to continue to fulfill my responsibility, I’ll kindly step down and let someone else grab the reigns.
Leadership on an open source project is weird to be honest. The real world doesn’t usually work this way, but I think it’d be better off if it did sometimes. I like to refer to the Ubuntu leadership code of conduct because I think it makes a lot of sense, even if not everything directly relates. Also, leadership isn’t normally even an issue until it feels like there is no leader. If the leader is a total jerk, then chances are the platform would just die because people didn’t like that person. If there’s no leader at all, well… then you just feel abandoned and weird about it, like you should try to help, but don’t know who to ask or what to do. It’s like getting broken up with out of the blue… You’re unprepared and it sucks and you’re sad and bleh… No good.
1) None of us are worried about the name from a personal view point, it could all could be renamed Bob’s Super Duper Forum for all we care ;-] , only form the perspective of not confusing users.
Then bbPress it is.
2) How are we going to differentiate this to the current “bbPress Plugin” (we already get quite a few support requests for it)?
The goal is that no one will have to. If people want bbPress today, they download the current stable version same as always. When the plugin becomes available, it’s up to us to make a great UX that helps existing bbPress users through the update, and makes sure new users aren’t smacked with tons of legacy overhead. BuddyPress was able to get bbPress installed with a 1 click install; our goal should be the same.
3) How are we going to differentiate this from a “bbPress Plugin” that actually plugs in to bbPress?
A plugin is a plugin, but there is no such thing as a “plugin dependency” like there is for enqueuing CSS and JS in WordPress. The way we tackled that problem in BuddyPress is similar to what I’d like to do with bbPress, but obviously much lighter and built in from the start.
4) Are we confident this is crystal clear to those who aren’t native Engligh speakers?
Since I only speak English, I can’t answer this confidently. I’d like to hope we do a good enough job preparing everyone for this going forward, that anyone that cares enough to contribute does so and stays on top of things.
I’m not looking to back you into a corner with this bro, but an update on the terminology we should “try” and use so we don’t confuse our already dwingling audience would be real helpful at some stage in the future.
No worries
There will be better communication all around going forward to help ease peoples minds.I think alot of us can see and understand this. What would be great though, again at some stage, is if we were allowed some visability on what those advantages and disadvantages were (at a high level).
None of us were involved in nor had any visability of the decision, or conversation even, about bbPress becoming a plugin; so it’s a tad of a shell shock as to how this has come about. You’re a few steps ahead of us because of that, so any resistance you’re feeling isn’t actually against the project or yourself/Pete
bbPress, is always bbPress, and it’s up to the project leaders/managers/grand facilitators to be the guiding light. If that’s Matt, or Automattic, or whomever doesn’t really matter. Again, if it’s a matter of authority, then to me Matt is the authority. But, again, if someone starts ripping through code and contributing tons of patches, there’s plenty of room for advancement if you’re willing to put forth the effort into the core project.
It would be really great to see the requirement gathering, and weighing up of pros/cons etc. Especially after Jane’s famous https://wordpress.org/news/2009/12/setting-scope/ post about how more standard/practical/tangable/visable methodology would be used for these decisions.
That would really help us in terms of seeing where things are going; and help us get behind you and Pete on this project
Can’t speak for Jane, and not sure how famous the blog post is, but this is the beginning of that for bbPress. bbPress just has less eyes on it, so it suffers the same way BuddyPress does; passionate userbase, very little action taking place. bbPress development will start gaining speed in the coming days and weeks, and all of those blanks will start getting slowly filled in. If you or anyone else wants to start talking about how to fill those blanks in, start up dedicated topics in the forums so we can sticky them and go over it all.
You’ve a lot of goodwill from those of us who’ve seen your work and great attitude in these last 2 years mate. Sadly, there’s not alot left in the tank of most folks in regards to bbPress itself after Matt’s “We’ve done this before.” and then bolting for the door.
https://bbpress.org/forums/topic/whats-happening-with-bbpress/page/5#post-64410
This is only compunded by Jane announcing that bbpress would no longer be used for the WordPress forums before telling anyone involved. Not quite as bad as Matt telling people in his KeyNote speech that the community was “rough” and to use “differnt software instead of bbpress”, but not helpful either.
bbPress will still power the forums, just not as a standalone piece of software anymore once this is ready.
The trust is gone. But you’re definately the man to regain it
Cheers mate, much appreciated
As an aside, bbPress has always been the forum software for enthusiasts. It’s edgy, and sleek, and when you tell people what software is powering your forums and say “bbPress” you just kind of feel like a bad ass. I think that’s part of where the apprehension to adapt to it being a plugin comes from, because plugins by their general nature aren’t usually trusted to do what they should, the way they should. Also, because bbPress is such a niche project, we’re all used to living on the latest SVN revision, salivating at the prospect of waking up the next day and seeing all the neat new little things that changed since the night before.
The reality is that most normal people don’t do that, and that’s the person we need to cater to first and foremost.
bbPress (the plugin) should be considered toxic and unstable until we say go. Not unlike WordPressMU, it was forked out of WordPress, honed, and then merged back in. bbPress (the plugin) is a separate branch of code that does not intersect the existing code in anyway. Once it’s fully refactored and stable, we incorporate all the legacy bits that we need back in with a conditional to not require it if you’re not upgrading, and Bob’s your uncle.
At least, that’s the plan.
I want to convert a hundred of my blogs to forum using simplebb. One potential issue is administering those forums. Is there a script/plugin to administer all posts/members from 1 user interface?
Thx
