[namelesshorseman]

hi _ck_,

I’m trying to use your fix https://bbpress.org/forums/topic/https-with-bbpress-login#post-23667 + your code above, but get the following error when I try to activate the plugin:

Fatal error: Cannot redeclare bb_validate_auth_cookie() (previously declared in <path to bbPress>/bb-includes/functions.bb-pluggable.php:142) in <path to bbPress>/my-plugins/https-mode.php on line 22

Any ideas?

Thanks!

Tomek

[_ck_]

Cursing/insulting Matt doesn’t help anything and is silly.

Matt’s actually a really nice guy from what I have read and heard. If he would ever have a vegan meal instead of all that meat, I’d even have lunch with him. He was one of the first and few people to donate towards a replacement monitor when mine failed.

I just disagree, strongly in some cases, with his decisions that seem to be done rather suddenly with little or no input from others, that radically affect a great many people. I disagree heavily with the concept of “code sprints” that he seems to like so much and most especially shoving in “features” into the core that should be plugins.

As far as forking, you have no idea what you are asking. It’s a ton of work and responsibility. Anyone can fork, but we’d run into exactly the same problems, who owns the domain, who owns the project name, who owns/operates the servers, are major decisions done by one person or by the community, etc. You are basically asking someone else to do the work for you, for free. If you want a fork, hire a coder and fork it, you don’t need anyone’s permission.

[willcrain]

I think that it was a cookie issue… after a number of different changes, uninstalls and reinstalls it seems to work fine. Not really sure what was going on but it seems to all work now… hopefully it stays that way…

thanks though for the help… i am sure that i will have some further questions

thanks again

[John James Jacoby]

Again, just too many of the same points to repeat myself, but bbPress standalone isn’t going to be “unsupported”, it just isn’t going to see any additional features, which is exactly what I think most of you want. Correct me if I’m wrong here?

If I wasn’t on my iPad I’d quote myself volunteering personally to commit any bug fixes to the 1.1x branch of code if anything comes up, but again, that went totally unresponded to.

All of the things I’ve offered to do, to help continue the 1.1x branch of standalone code in addition to creating the 1.2 plugin, have gone totally unacknowledged. If you want to be able to do it yourself, you’ll need to have the experience to understand that the code you write is responsible for powering millions of sites around the world, and that you can easily create global chaos with one click of a button. Call me melodramatic, but in environments like WordPress.com, it’s very true. My experience over the past year has had me much more close to that kind of environment, particulalrly with BuddyPress.

A year ago I felt keeping bbPress as a standalone made sense because a year ago I didn’t comprehend what was coming in WordPress, particularly 3.0 where custom post types have made much more possible. I also had less experience with BackPress, and don’t get me wrong; BackPress is awesome, but bbPress won’t reach its full potential until it’s a plugin for 25 million other websites.

Kevinjohn, I’m sorry but you’ve got a knack for twisting words around and quoting things totally out of context. That’s not really fair, and I wouldn’t do it to you or anyone else so I’d appreciate the same.

I don’t get what you all want bbPress to do differently that would even require a new standalone version. I’ve asked that before, and there’s no answer; just frustration.

bbPress has always been an Automattic endorsed project, and considering without Matt it wouldn’t exist, or have a trac, an svn, or core developers thus far, it seems like he’s the one who’s earned the ability to make decisions on the future of the project. If you call me believing that to be true drinking that Kool Aid, I’m happy to do it because I believe Matt and Automattic and bbPress has earned that from me. If Matt wanted to abandon bbPress completely and close up shop, he could, and someone could graciously keep it alive by forking it. None of that stuff, should make anyone this upset.

My employment status or relationship with Automattic aside, I’m happy, blessed, and consider it a great privilege to have the trust of Automattic and the surrounding community to take this on, even if some of you don’t understand why it’s me, or why now, or why a plugin.

Regarding TalkPress, the main reason it’s named differently is to avoid the confusion people have with WordPress.org and WordPress.com. bbPress is the opensource forum software of choice for WordPress users. If any of you want to help the plugin work on top of backpress, patches welcome and I’m open to the idea. Otherwise, I’d wager 60% or more of the support questions regarding bbPress are incorporating it with WordPress. It’s been said in this topic already, but making it a plugin alleviates those issues, and still allows everyone to keep loving bbPress.

In all honesty, all this back and forth is tiring, and all it’s doing is taking the team of people that are here to help keep bbPress alive, and make us the enemy to the people that are just happy to see life again. That, and it’s taken our ability to communicate news to the bbPress community away from us, and instead forced us to try and put out this fire for the past 4 days.

Quite frankly, it all kinda sucks.

I get that the reality (for some of you) of switching bbPress to rely on WordPress instead of BackPress doesn’t sit well or even make sense, but I promise you it does. I might even have a trick that will help make the admin area a little more familiar. But 1.2 isn’t going to use BackPress anymore. Instead it’s going to use WordPress. bbPress itself is getting lighter, and we inherit all the eyes and updates that WordPress has had that BackPress hasn’t. That alone, if you ask me, is more than enough reason to be thankful for this move. If you need it super optimized, we’ll inherit all the caching plugins for WordPress. If you need bells and whistles, we get WP plugins. There is too much to gain, to not have bbPress be a WP plugin.

The existing standalone committers, are doing a great job already. There are very few trac tickets to work through in terms of bug fixes, and most of the enhancements would naturally get fixed by making it a plugin.

So… I want to say again, your passion and enthusiasm is something I want, and appreciate. If any of you are going to WordCamp Savannah, I’ll gladly discuss this over drinks and dinner. Whatever you need, I want to make it happen for you, but the name isn’t changing, Myself and the team are going to support the standalone with security updates as needed. Since I have commit access, I’m happy to commit fixes as needed because I’ve been trusted with that ability and I want everyone happy with a safe and functional piece of software, plugin or standalone.

I also, typed this out entirely on my iPad over the course of an hours worth of “leisure time.” if that doesn’t say you have my attention and commitment, I dunno what does.

[citizenkeith]

I’d love to help out. I’m capable of backing up my database and restoring it. :

[johnnydoe]

has anyone already figured out how to show the excerpt with livibetters code of the topic (main post) instead of the last comment?

thx

[_ck_]

This will probably be low on the priority list but tags are no longer being imported from the readme.txt in the plugin section, so any updated plugin since the bbpress.org 2.0 upgrade has lost it’s tags.

[zaerl]

The micro-plugin (I have written for you) activate the s HTML tag (as you requested) <s>your text here</s> but zaerl Editor 0.3.2 does handle only standard tags plus the img tag as I said here: https://bbpress.org/forums/topic/latest-on-better-editor#post-71194

[john010117]

My two cents (if it’s worth anything): Keep bbPress 1.1 and continue to maintain it. However, get a new dedicated group of developers to actively code and maintain a wordpress forum plugin (named differently like talkpress for example). And on both website’s front pages, specifically list the differences between bbPress and “talkPress” so people won’t get confused.

[_ck_]

Currently there are only four settings and all but the first are optional.

Edit the top of the plugin to see them:

$browsertimer['log']='/browsertimer/browsertimer.log';

That is where the log is kept.

Obviously the directory must be chmod 777 on your server.

For that reason I STRONGLY recommend you put it ABOVE the web root.

The default setting will do that:

dirname($_SERVER['DOCUMENT_ROOT']).'/browsertimer/browsertimer.log'

but since it may confuse people, adjust it as you will.

ie. /home/username/public_html/

is the webroot on many servers but not all by any means

you could in theory make

/home/username/browsertimer/

and chmod 777 that directory, and it will work with the default setting.

$browsertimer['filter']=true;

This setting just throws away entries longer than 20 seconds or less than 100ms which are typically bogus. For example Google has a nasty habit now of parsing javascript no matter how obfuscated it may be to extract URLs, and sure enough it will follow the browser timer, giving you really high, weird numbers.

$browsertimer['pages']=false;

This allows you to control what pages are timed.

I’d leave it alone for now but someone may have specific interest in mind.

$browsertimer['geoip']=false;

This is where the geo-location magic happens, it’s optional, and will tell you what country the visitor is in with about 90% accuracy.

false = country lookup off

or set it to ='ip2c';

and download this program called IP2C

http://admin.firestats.cc/ccount/click.php?id=74

extract these two files and put them in the same directory:

ip2c.php

ip-to-country.bin

(ip-to-country.bin is very large, it’s one big database)

[_ck_]

Once properly configured and running, administrators can get easy access to the log by just adding ?browsertimer to the forum url.

The view right now is very basic and looks like this:

https://bbpress.org/plugins/topic/browser-timer/screenshots/screenshot-1.png

I’ve done some fancy parsing of the user-agent to attempt to strip it down to the useful bits. (in the example the IP addresses are partially obscured for visitor privacy)

[Joe Gibson]

Z –

I copied the code to a PHP file and it activated from the bbPress ‘Plugins’ panel, but I can’t figure out how to make it work in the editor. I tried both angled brackets and backticks. Thoughts?

And the next big challenge would be to have it open links in a new window. Is that possible?

Thanks,

Joe

[kevinjohngallagher]

Yutt,

Like everyone else, you’re entitled to your opinion; and i am truly sorry if i’ve left you with an overly negative one – though I apprecaite I am a tad less forgiving of people who can’t even get my name right

[willcrain]

sorry about that. I did have it set up like that. (my spaces didnt show up in the post)

wordpress-instance ( http://www.examplesite.com )

---

>files with wp instance (ie wp-config.php, index.php, etc)

---

>[folder] wp-admin/

---

>[folder] wp-content/

---

>[folder] plugins/

---

>[folder] themes/

---

>[folder] myCustomTheme/

---

>[folder] index.php

---

>[folder] wp-includes

---

>[folder] bbpress instance (which i call ‘discussion-center’)

in this case in order to access my bbpress site i use:

http://www.examplesite.com/discussion-center

and that works, i can see it all and interact with both…but, once logged in however i can not access the wordpress admin panel, http://www.examplesite.com/wp-admin … just a white page… as well as http://www.exaplesite.com/wp-login.php… even if i remove the [folder] bbpress instance from my wordpress instance it still doesnt offer access for wordpress… i would try uninstalling it and reinstalling it but what else would i have to remove other than the instance folder?

thanks again for any help

[kevinjohngallagher]

Pete’s status, isn’t any different than the way you all feel about things. If you can vent your frustrations, so can he.

I’d never like to step on Pete’s rights or freedoms. He can say what he wants when he wants. But it’s just shame he didn’t have the common decency or manners to tell us… before bitching to the world.

If Pete’s not happy about some of the things in this thread, and we’re the people he’s going to have to (or wants to) live with as we move forward “together”, then he should have commented here.

JJJ your comments and Q/A attempts have helped a great deal. Of course there is still some polorisation and discontent, this is heavy (and for some peole horrible) news; people aren’t going ot be ok with it as soon as somone says “everything’s going to be A-okay”. Even if thats true, and I think it is and eventually things will be ok, there’s still loads that needs to be talked out before people can make an informed decision.

But y’know, talk it out, address the issues here, and win people over. Making snidey remarks on Twitter in the hope that no-one from bbpress will see it is just… poor/childish/cowardly. Feel free to pick one, I pick all 3.

I’m vocal, and according to Sam Bauers I use “combative” wording (which is rarely my intention). I’ve agreed and disagreed with the same people here over the years; and I’m sure to many they hate to see my name appear in that last poster column But on the left hand side here where it says my name it links to my website, where my email/phone is listed. Many people here use it, and I am more than happy for them and others to do so – even if they disagree/like/dislike with me. If i have something to say about bbPress, i say it here. I say it to the people that are giving up their time for bbPress, and earned my respect by doing so, and JJJ that includes you

I suppose it comes down to this:

• When, in life, are people ok about being talked about behind their backs, instead of to their face?
• How on earth do you think this would help pull the community together?

1. bbPress 1.1 (standalone) – Still in active development

2. bbPress 1.2 (plugin) – Months before anyone should consider it stable, but you’re welcome to jump on the bandwagon early and help make it exactly the way you want it, side by side with Pete and myself, and anyone else that’s along for the ride.

1. But you’ve told us that, with 1 trac ticket to go, this would be the last to be supported and or maintained. You also told us that it wont be supported once the plugin comes out. Thats freaking people out.

I can understand your entusiasm at the newst version, but surely you can at least see this viewpoint (even if you odn’t agree with it).

2. Here’s the scenario: http://www.dilbert.com/fast/2003-10-12/

You’re the manager, we’re dilbert, our clients/users are the client.

Even if that wasn’t the intention, thats where we are bro.

[mr_pelle]

Love you, _ck_! Here we’re suggesting 1.x users that they will be able to upgrade to 1.2, which is absolutely false!

Ironically I would have far more easily accepted another forum project being started by Matt and unfortunately letting bbPress slowly die over what is being done now.

Me too. I just hope, hope, hope we’ll close the missing tickets and release the next standalone version asap!

[mr_pelle]

bbPress 2.0 milestone was removed when “1.2” was set, now it is merged into Future Release…

Anyway, we’d need someone to actually take a look and submit those patches: I’ve already opened tickets about bbPress.org bugs in the past weeks but a lot of them are still there…

[_ck_]

Holy cow, there is some serious kool-aid drinking going on.

You can’t just up-end a community and then ask everyone to be positive about it.

Zero consultation was done with the community/contributors, exactly the same amount that was done with backPress. Let’s be CRYSTAL CLEAR about that right from the start.

For the people showing up out of the blue and jumping into the bbpress project suddenly this year, having NEVER contributed in the past few years, and in effect telling us to “shut up and go along with it” – I am seriously not going to take that nonsense, even if you say “please”.

You don’t just take a project and completely re-write it into something else and take it’s name. It’s not yours, it belongs to the community who adopted the existing program and worked many hours to install it, figure out bugs and improve it. It’s not yours to show up late and completely re-invent after that.

You don’t wash away the years of forum questions and answers by intermingling them with a different, incompatible version.

You don’t just call it 1.2 when it will have nearly zero code/layout/theme/compatibility with 0.9/1.0/1.1 – I mean sheesh, even calling it 2.0 would have been a minimal effort to note it’s something different but no, 1.2 is to confuse as many as possible either on purpose or out of apathy.

You don’t insist it has nothing to with Automattic when the SVN/TRAC slots were decided and made by Automattic people on Automattic servers at Matt’s directive as a plugin for another Automattic managed product.

The main developer of bbPress 0.8/0.9 was an Automattic employee (Michael) under Matt’s directive, the main developer of 1.0 was an Automattic employee (Sam) under Matt’s directive. It’s an Automattic product, always will be. Matt has been trying to figure out how to monetize it for years which is why it keeps getting messed with, so he can make a wordpress.com equivalent for forums.

Even JJJ admitted a YEAR AGO, that it’s a good thing bbPress is separate from WordPress because of how blogs and forums are different even though they share similar data structures. But now it’s a 180 turn in the opposite direction because of Matt’s whim.

If you want me and the other people who have a problem with this to shut up, it is SUPER SIMPLE to end this problem:

1. don’t call it bbPress
2. start another Automattic site to build your forum plugin

   (or attach it to a wordpress.org subdomain which probably would have been more appropriate)

3. finish what was started: it’s too late for 0.9 to be properly finished as it should have been into 1.0 before the 180 with backPress but it’s not too late for 1.1 to be released and then matured into 1.2

Don’t just march into an existing community, take it over and change it’s course into another 180 turn for the second time in three years and expect anyone to just smile and go along with it.

What you aren’t seeing are the 10,000+ sites that don’t post here and have successfully adopted it, even with virtually no advertising or support from the WordPress community.

Ironically I would have far more easily accepted another forum project being started by Matt and unfortunately letting bbPress slowly die over what is being done now.

[chrishajer]

If your WordPress site is at http://www.example.com, and that corresponds to “wordpress-instance”, then you want the folder “bbpress-instance” accessible at http://www.example.com/bbpress-instance.

It’s hard to tell the hierarchy of your folders from your post, but basically, you want a folder (with bbPress files in it) at the same level as wp-config.php. The name of the folder matters, since it will be visible in the URL (bbpress-instance in the above example.)

You should end up with this folder setup when you are done.

wordpress-instance/

----bbpress-instance/

bb-config.php

bb-templates/

----wp-config.php

----wp-content/

plugins/

themes/

Make sense?

[John James Jacoby]

Too much to address, but I’ll pick some points.

WordPress + BuddyPress + W3 Total Cache = less than 10 queries on a complete social network. If optimization is your cup of tea, there’s lots of ways you can achieve that. Core issues with WP should be directed over to those folks.

If you have a method to make it better, submit a patch. Then you can work your way up to being one of ‘those people’ that are making the decisions that you don’t agree with.

Pete’s status, isn’t any different than the way you all feel about things. If you can vent your frustrations, so can he.

Help me understand why we’re upset again.

1. bbPress 1.1 (standalone) – Still in active development

2. bbPress 1.2 (plugin) – Months before anyone should consider it stable, but you’re welcome to jump on the bandwagon early and help make it exactly the way you want it, side by side with Pete and myself, and anyone else that’s along for the ride.

Regarding # 1, what MORE do you want your lightweight standalone software to do? If you want it to be more efficient, spend some time walking through queries and making it that way. If you want something in the UI changed, do it; patch it; make it go, and I will review it, and commit it.

Regarding # 2, our goal is to have this usable ASAP as part of the 3.org initiatives, but I wouldn’t want anyone outside of that initiative using it for production until it’s released. I know we all like to live on the bleeding edge (I’ve always been that guy too) so now’s your time to start helping us weld things in from the very get-go. If you think the way we’ve doing it now is completely wrong, let us know and provide us a better way; I am happy to listen and make it right, because I want what you want; the best bbPress possible.

I think all this talk about Matt, and Automattic, should be redirected back towards Automattic the company, and not bbPress the open source software. I understand the two are perceived to be tightly integrated because mixing money and open source is mixing business with pleasure, and it’s always hard to explain or understand the difference.

I think the general negativism has taken its toll already, and it’s time to try to look at this glass as half full going forward. Please? Kindly?

Not trying to be a jerk here, but man… there is no end in sight here, and it just isn’t productive or helpful anymore. We need to tighten this ship up before it sinks itself. I say this, not from a “looking down” perspective, but from a “‘we’re in this together so let’s make the best of it” perspective.

[zaerl]

In bbPress if you put something between backtick it shows up in fixed-width, not-transformed style.

And, for that matter, why isn’t this site using it?

bbpress.org and bbPress in general uses the backtick notation. It’s hard to remove it. I have answered to a topic some times ago showing a little hack to erase it.

So, is there a way to turn it on?

<?php

/*

Plugin Name: I love strike-through

Plugin URI: http://www.bbpress.org

Description: <s> tag

Author: zeal

Author URI: http://www.zaerl.com

Version: trunk

*/



function strike_it($tags)

{

$tags['s'] = array();

return $tags;

}



add_filter('bb_allowed_tags', 'strike_it');



?>

[Joe Gibson]

Z –

“It doesn’t understand strikethrough cause that tag (the obsolete ‘s’) isn’t enabled by default on bbPress.”

So, is there a way to turn it on?

And I understood that the ‘Code’ button was for generating backticks, but what are backticks used for since the buttons cover pretty much everything?

And, for that matter, why isn’t this site using it?

Thanks,

Joe

[Techpad1]

Thanks Kev, that’s a big help. I understand everything in that bit of code except the line

“$topic_slug = bb_sanitize_with_dashes($row,200);”

Would you care to enlighten me on how that would add dashes? I was thinking that I’d have to parse the topic_title field with regexp somehow (not great at regexp yet, just learning)then create the string. Is that what this represents?

Regards,

Dan White

[doobadabba]

I’m excited to hear that bbPress as a WordPress plugin is getting spirited attention and development!

I can also feel for all the contributors to current and past iterations of bbPress, who may have felt left in the dark, or unappreciated. Well, I appreciate you!

I’ve got a little niche community site right now. The site has a blog, and a classifieds section, and a bbPress forum. I’ve got integrated login working, but would love to have even more integration between bbPress and WordPress (especially shared header and footer, and it would be good to have just a single “profile” associated with members of my site).

As digging into code is not my most favorite thing, I’m hoping that bbPress-as-WP-plugin can simplify all of my WordPress projects.

I’m aware that some people may want to keep a standalone bbPress project going, even if only the maintenance of current and former iterations of bbPress.

And I can see that using the same name “bbPress” for both the upcoming bbPress-as-WP-plugin, and the current-and-former-standalone-bbPress-iterations that may be continually maintained, is potentially a source of confusion.

But, I don’t think it has to be confusing.

If a central location, such as this website, clearly presents and describes the differences between using the upcoming bbPress-as-WP-plugin and current-and-former-standalone-bbPress-iterations, then I think people will be able to decide what is best for them.

If I understand correctly, Matt was the original coder (and I’m guessing namer) of bbPress. And it seems that he is the top caller of shots for how bbPress goes forward. As such, I don’t think he should need to rename bbPress-as-WP-plugin to anything other than bbPress, even tho so many other people have been making bbPress what it is today.

But if he did rename it to something like pbPress (plugin-board-press), it might simplify things. How about ccPress (community-creation-press)?

That’s my though-gasm in this moment anyway. Thanks to all of you who have gotten bbPress to where it is today, and to all of you who are moving bbPress forward, and also to all who are mindful of moving forward in a fashion that is not unduly regressive

[Josh Stauffer]

I found several posts about converting SMF to bbPress. Since I just got done with the conversion and it is still fresh on my mind, I figured I would share my notes on the process.

To convert SMF to bbPress, I had to:

-Convert SMF 1.1.11 to phpBB3 (3.0.7)

-Convert phpBB3 (3.0.7) to bbPress 1.0.2

I had SMF setup on a subdomain: forums.mysite.com

• I created a NEW database separate from the SMF database.
• In the root of forums.mysite.com, I created two directories “bbpress” and “phpbb”.
• I uploaded the uncompressed files of phpBB3 to the “phpbb” directory.
• I uploaded the SMF 1.1.x to phpBB3 converter script. It can be found here: http://www.phpbb.com/customise/db/converter/smf_1.1.x_to_phpbb3/
• When you install phpBB3, I installed it using the NEW database that I created. I followed the “phpBB Convert How To” guide which can be found here: http://www.phpbb.com/community/viewtopic.php?f=65&t=1213555
• At this point, your SMF forum should now be converted to phpBB3.

• Next, I uploaded the uncompressed files of bbPress to the “bbpress” directory and installed bbPress using the same NEW database as phpBB3.
• I used the phpbb3-to-bbpress1-converter which is hosted on Google Code. The script is super easy to install and comes with instructions. It can be found here: http://code.google.com/p/phpbb3-to-bbpress1-converter/
• Optional: I logged into phpMyAdmin and deleted the tables prefixed with phpbb_ in the NEW database.
• Success. It is finished.

Honestly, after reading all the posts out there this whole process seemed rather daunting. Let me assure you that it is easier than it sounds.

Thanks to everyone’s notes that got me on my way and to the awesome folks out there that took the time to write these scripts to make it even possible.