[pedagog]

Hello zaerl

Thank you for responding. At the moment I am unable to test your plugin. However, I think I may be able to test it in a few days.

Could you provide me with code so I could code it directly without using a plugin? I would prefer to use coding myself if possible to give me a better understanding of what I am doing.

Many thanks

[pedagog]

Once again, thank you Mr Pelle. That worked fine. I will have to try zaerl-visibility when I get my production online for testing.

Thanks for all your very useful input

[Ivaylo Draganov]

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 using bb_head in functions.php of 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!

[John James Jacoby]

They will if they came here for a stand alone software (or if they don’t use the latest version of WordPress).

If they’ve never used bbPress before, then they will come here not knowing it was ever standalone, and won’t have any issues installing a plugin, and turning it on.

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.

This entire support forum and plugin section for bbPress will have ZERO meaning for the plugin and will only serve to confuse people.

All the years of advice here for the two major versions of the standalone version will be useless for the plugin version.

It will have meaning for supporting legacy code, which happens all the time when something gets refactored in WordPress. Get it working in it’s current incarnation, then ensure backwards compatibility with existing installations that are already integrated with WordPress.

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?

The *plan* is for everything to stay how it is, with no loss of data on bbPress.org, or anywhere else.

The bbPress extend section doesn’t include half of the things the WordPress.org section does now, in terms of compatibility checks, etc… By having bbPress as a plugin, we inherit that too.

I know that there’s broken spirits, and I don’t want it to be this way, but I can’t say anything any more clear to ease anyone’s anxiety about it.

Btw, the first commit is in. As you can all see, there’s plenty of work to do, so you’ll have nothing to worry about for a while.

[kevinjohngallagher]

Ah, see this is the issue mate, and I hate that I look pedantic.

My point is that 99% of people won’t know the difference.

They will if they came here for a stand alone software (or if they don’t use the latest version of WordPress).

The ability to be standalone software is being removed, without anyone actually saying so. I know it’s not underhanded or Machevelian in any way; but it’s difficult when people skirt around an issue (unintentionally).

This is the end of the line for the current implementation of bbPress.

Thats not me being all doom and gloom, your plug-in will rock, but lets manage expectations a little and tell people who use bbPress as a standalone that their days are up (btw, that covers roughly 60-70% of our support queries).

[John James Jacoby]

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.

From a Project Management viewpoint

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.

[kevinjohngallagher]

Profiles are no longer showing posts in the Recent Replies in the corect order. Or actually in any order. Do people actually test this before /after they push it live?

[Rich Pedley]

Kevin has a point about naming. bbPress as a standalone sounds fine, but using the same name for a WP plugin – which will be a totally different entity – is perhaps wrong and confusing. Don’t get me wrong, because I for one am looking forward to testing and using it.

So should we be suggesting new names for the WP plugin version?

[kevinjohngallagher]

Hi Scott,

Just been through this with my WorldCup Fansite Forum after the final on Sunday night, so I’ve a few things to throw your way. I’m sorry about the slow and pedantic manner of this post too; but if it’s this or close yoru forum, we’ll just get through it!

My gut feeling is that this is a plugin and/or host issue. So lets see what we can do here:

First, lots of boring questions I’m afraid:

Is your website using WordPress at all?

If so, have you set up “deep integration”?

Did you do the installing/setup yourself?

Second, ask your host if they’re intentionally throttling you or if it’s automatic?

If it’s happening, ask them what the issue is (I doubt they’ll give you a huge run down but might find a specific issue you didn’t know was the ‘biggie’)

Third, Make backups

Copy a back up of every plugin and your theme on your hardrive somewhere, then log into bbpress and deactivate them all (apart from akismet) and change to the normal default theme.

Fourth, delete all of the plugins and themes.

Fifth, Tell your users

Write a post (then sticky to font) about how your website is going through an “upgrade” and in order to get the latest most secure most awesome software installed you’re having to accept the default theme for half a day.

Sixth, Lets have a look at those SQL queries.

Open up your bb-config.php file and add the following line before the database connection stuff (at around line 33):

define('SAVEQUERIES', true);

Seventh, edit your footer

open up your footer.php in (my-templates/kakumei/) and add this to the very bottom:

if (bb_current_user_can('administrate'))

{

global $bbdb;

print_r($bbdb->queries);

}

Apologies for this, but that last line is going to have something that looks like “->” in it. Please, make this into “-” and then a right arrow (usually shift+period). It’s a bug here on this forum – should be fixed soon.

Eight, load your forum.

At the bottom of your homepage you should see a big list of stuff, which will have lots of SQL commands.

This is a list of all the SQL commands that load, in order, along with the time taken to execute.

Do any of them look to be taking longer than the others?

Copy and paste this list into a text file and save on your desktop (there will be about 15 SQL commands with a few lines around them).

Nine, recount.

Log into your admin area and go to Tools.

Select ONE checkbox at a time and hit “RECOUNT ITEMS”.

Do this for all checkboxes going down the list.

Ten, load your forum (again).

Repeat Step 8.

Compare the results betwen the two text files.

Have any of the “times” come down?

Are any of them above 0.1 seconds?

Are any of them betwen 0.5 and 1 second?

[Sunnichka]

Yeah, I know that this topic is old, a pity it’s not very busy here Well, I wanted to use bbPress registration because there are more fields in it and i dnt want to mess up installing extra-plugins to WP to get all necessary datas from users when I could get all needed from bbPress.

All changes i was trying to do in class.mailer.php is to put registered email to $Sender end played with $Host because it’s not localhost at godaddy hosting.

It didnt work with WordPress before I started to change anything anyway.

Sorry, I’m not a hardcoder and this bloody thing causes me headache already a week. Didnt happen on testhosting

But thank you for reply!!!

[kevinjohngallagher]

That makes sense.

You shouldn’t really need to change anything, thats the joy of the default mail() function. I’m not sure what drove you to make the changes in the first place (this 3+ year old thread isn’t the best place to get data, alot has changed since 2006).

I’d get rid of whatever changes you made, and then test on WordPress.

If that fails, then it’s off to the WordPress support forum for some help.

host said that it’s a script error and they can’t help

Did they happen to give you the error? that will help the WordPress folks sort it quicker

[kevinjohngallagher]

Hi Sunnie,

The first thing to check is if WordPress can send registration emails.

If it can, then we have a bbPress issue.

If it can’t then it’s a server issue, and the quickest resolution is to contact your hosts and use the WordPress support forum (as there are more people on there).

Test and let us know

[honestscott]

Hi,

My bbpress 1.0.2 forum is causing a lot of slow queries, and I had to shut it down because my host Monster Host was Throttling my account big time.

Is there a fix for this, I am not running many plug-ins that would use the database except for bbpm, but I tried disabling this plug-in, and I still get clobbered with slow queries and CPU throttling.

I hate to have to shut the forum down, but I am not a php coder or a database administrator.

I tried moving my sites to a semi-dedicated server (to get more server resources) but their Myphp interface clashed somehow with all my WP databases.

I was on NTC hosting and their support team told me it was a problem with my WP sites, although I did get one blog to work half way decent, but my bbpress forum would not.

I was using Blue Host when I created my sites, so I went to Monster Host (their sister company) and loaded my files and DB’s and they came up just fine, but I am back to the DB strangulation with slow queries.

I check the slow queries log on my server and I see a lot of forum queries in there, but the logs don’t really pin-point a cause (plug-in or script).

Here’s a list of the plugins I have on my forum:

ajaxed quote

adsense for bbpress

bbcode buttons

bbcumulus

bbpm

bbpress signatures

bb-smiles

check for updates (not activated)

delete all bozos

mass delete users

members online

php4bb

super search

approve registration

bb-avatars

bbcode lite

bb twitter (not active)

google analytics

human test

moderator notification

new user notification

restrict registration

I would appreciate any, and all ideas so I could save my forum from the trash bin.

Thanks for your time,

Scott

[kevinjohngallagher]

If you’re running bbPress1.0.1, bbPress1.0.2 is a very minor upgrade (less than 100 lines of code) and include some bug fixes.

bbPress1.0.3 / bbPress1.1 shouldn’t break that many plugins. My last trunk download caused some theme issues (minor), but up until the end of April there it was stable and looking might fine.

I strongly suggest you make a local copy of your current forum, and install the latest version from the trunk; and test against your plugins. Given the list that you have, there’s a good chance some may fail; and others like “Subscribe to Topic” won’t really be needed.

When/if this new bbpress plugin comes out, will there be a way to convert my bbpress installation into teh plugin or otherwise make it compatable?

None of us have any idea. Matt announced that the bbPress plugin was going to happen in January, then left the project. Any other information you can garnish from the WordPress blogs updates will give you more information than people involved with this project have been given.

Either way, i’m not panicing. Just irked by the lack of communication, as you’re not alone in asking, and i feel for the bbPress users who are in a form of limbo.

[chrishajer]

Friday 9th July:

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

matt states that bbPress has been upgraded to latest trunk version

Where did that come from? I didn’t see that posted online.

The code running here is certainly not updated to the latest trunk. From the source of the page:

[meta name="generator" content="bbPress 1.1-alpha-2453" /]

When it’s updated, the BackPress fix will be in.

[kevinjohngallagher]

Sorry, posting quickly on phone.

Thursday 1st July:

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

Westi states that the 3 months old bug has been fixed. And will be applied to bbPress at the next patch.

Wednesday 7th July:

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

Matt states bbPress powered forums at WordPress.org has been upgraded to the latest version of bbPress and BackPress.

$this->shitty->bug() is not present. yay.

https://wordpress.org/support/topic/422478

Friday 9th July:

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

matt states that bbPress has been upgraded to latest trunk version

$this->shitty->bug() is still present and in it’s 3rd month. booo.

Might it just be miscommunication? Yes, I agree it is.

Is this bug fixed somewhere out there? Yes, I agree it is.

Is it close to commical that it’s been where for 3 months? Yes, it is.

Is something wrong with at least one of the statemetns from Matt? Given that one contradicts the other? Yes, it is.

Honestly, is it so damn hard for an Automattic employee to also update our BackPress version as well as the bbPress version? I mean, do they not know that bbPress is dependant on BackPress (definately possible)? Is it an issue of shame or embaressment at a bad decision thats coming back to haunt them, or just a mistake that gets made constantly over the last 6 months?

[chrishajer]

Sorry, very latest trunk is r2461. mdawaffe checked in a few revisions, probably after updating the wordpress.org support forums.

The last svn log is for r2460, but when I checked out the latest, it says revision r2461. But there is no log entry for r2461.

I’m glad they’re using it at the wordpress.org forums. With many users the problems will become apparent and will have resources devoted to fixing them.

[chrishajer]

Where did Matt say he fixed the code/encoding issue?

We are still running r2453 here, not the latest version r2458. The BackPress fix didn’t happen until BackPress r312 on Jul 1 2010 by Westi. When the code is updated here the problem will be fixed. If you check out a new revision, the problem will be fixed in your installation.

Here is an example forum using r2458 with the BackPress fix and you can see that the code is formatted properly.

http://bbpress.chrishajer.com/trunk/topic.php?id=3#post-7

[kevinjohngallagher]

It’s part of the core.

Have you tested it?

[kevinjohngallagher]

http://wpdevel.wordpress.com/2010/07/09/last-night-two-big-changes-happened-on-w/

I love, truly love, that it was tested.

Otherwise, people might just think he’s making this shit up as he goes along…

[chrishajer]

To check out via subversion:

svn co http://svn.automattic.com/bbpress/trunk/ ./testdirectory

[chrishajer]

I think the best thing to do in your case would be a test installation of the latest trunk release of bbPress (not the packaged 1.0.2 release.) There’s no way to know if all that is going to work on the latest version of bbPress, but I suspect most of it will.

I would copy over your database, then install bbPress with subversion. Then copy over your template and plugins. Then test. If it all works, then go ahead and upgrade your 1.0.1 installation.

Regarding when bbPress becomes a WordPress plugin, it doesn’t really matter. Use what works for you (right now, that’s a standalone installation, as you have here.) That code you have installed is never going away. If a time comes in the future where you can move to bbPress as a WordPress plugin, then go ahead and do it. But use what works for now and don’t wait for any version coming in the future.

[Marius-]

So does the bb-nospamuser have any advantages compared to human test ?

[sureshdrim]

Hello all..

In my case I am testing this plugin on localhost.Server software Value & PHP version are as expected.I followed the installation steps correctly,but still couldn’t get this plugin working from a longtime.

I get following error:

Oops! This link appears to be broken.

Please help !

[chrishajer]

I think the toolbar button is designed to let you insert a link to an image in your post, but the image already has to be online somewhere. The BB WYSIWYG plugin doesn’t handle uploading or storing images. It just modifies your post.

So, they work in different ways. If you used the BB WYSIWYG editor and the Allow Images plugin together, AND the image was online somewhere already ( like this http://www.google.com/images/nav_logo8.png )then you would be able to use the toolbar button. But if the image is not online yet and you want to store images for your users, then I think bbPress Attachments is the way to go.

bbpress (testing for the filter)