[_ck_]

The images are hosted elsewhere when using the [img] tag so bandwidth doesn’t matter.

Are you thinking of uploaded attachments which is another plugin entirely?

Unless maybe you mean you only trust certain users to be able to post images at all because you are afraid of content you don’t want from unknowns. That would be possible.

If you want the latter, try replacing the plugin with this:

<?php
/*
Plugin Name: Allow Images (moderators only)
*/
add_filter( 'bb_allowed_tags', 'allow_img_tag' );
function allow_img_tag( $tags ) {
if (bb_current_user_can('moderate')) {
$tags['img'] = array('src' => array(), 'title' => array(), 'alt' => array());
}
return $tags;
}
?>

That will allow moderators or higher to post image tags, everyone else will end up encoded. You could also optionally use the throttle permission which is the checkbox in the user’s profile that allows then to post faster than 30 seconds apart, but use it also as a flag that they can post images (just change moderate to throttle)

[_ck_]

It will take me a little while to find the original post but years ago you said you didn’t like the bbPress name.

If I can’t plead with you for a name change for a completely different forum program (it will likely share 10% or less of the original code) than at least don’t call it 1.2

1.2 has way too many implications that it’s a minor upgrade to 1.1 when in reality it’s a major overhaul (most especially if you aren’t running WordPress or WordPress 3).

All themes, plugins, hacks, advice will be invalidated.

That’s not a x.1 to x.2 update!

[_ck_]

Yeah problem was solved – sometime in the past week the code bug was fixed, I have no idea exactly when or by whom but was going to point it out until I tested it.

Unfortunately it did not clear up existing posts that were already html-entitied by the bug an example or two (but it even happened inside of backticks too)

I kinda don’t want to get into WP politics here (we’ve got enough of our own problems) but you can’t count downloads by existing users anymore who are terrified of being hacked because they didn’t keep up with the newest release.

I was looking into having some reindeer paraded by your door (10 “bucks” get it?) but I was afraid you’d BBQ them and send me a photo or something like that

[_ck_]

Your server must have some fancy virtual host mapping.

By the way I just noticed you said this “I created a file called browsertime.log”

delete that file you made because it may have permissions that PHP cannot modify for some reason depending on your host – let the PHP code make the file

Well we can take the lazy way out:

$browsertimer['log']=dirname(__FILE__).'/browsertimer.log';

That should almost certainly work and be right in the plugin directory.

[_ck_]

You know what, this idea grew on me, I like it and off to apply it.

It could be done a little fancier via the filters on bb_title and bb_get_title ie. the page could be injected between the forum name and the topic name, but this will do for now.

[_ck_]

By the way, your site is using 69 queries on the front page, that is VERY very bad. Something is wrong. It’s probably not loading all your options at once and some other issues that 1.0 has.

You probably should be focusing on bb-benchmark instead of this plugin.

Also make sure you install this mini-plugin to try to reduce the queries:

https://bbpress.org/forums/topic/heres-how-to-fix-some-of-the-10-query-performance-regression

[_ck_]

Ah, you almost have the log location concept but not quite.

I am going to assume you are trying to put the log file in the same directory as the plugin. I really don’t advise this at all for security reasons but if you are just doing short term testing and will delete it later it could be temporarily acceptable.

So, in that case my-plugins/browser-timer/ must be chmod 777

(the sub-directory /browser-timer/ I mean)

Now is the path to the file really

/pastorbob.limewebs.com/my-plugins/browser-timer/browsertimer.log'

Because that doesn’t seem quite right. I see it’s off a subdomain but still, I’ll not certain.

Try changing

dirname($_SERVER['DOCUMENT_ROOT'])

to just plain

$_SERVER['DOCUMENT_ROOT']

(don’t forget leave the dot afterwards)

If that doesn’t work, what’s the full path to my-plugins/browser-timer/ that you see in your FTP program (if it hopefully shows the full path). If not, we can take a peek at phpinfo.

What I’d really rather see is you putting the log in a subdirectory ABOVE your web root (aka Document Root).

But give that a try for now and let me know.

[_ck_]

Hmm, is page number in the title important to SEO?

It is an attempt to avoid duplicate content penalty?

Because Google already understands bbPress forum layout, they are very clever like that.

[_ck_]

Sounds like your keys or cookie paths are out of sync between the two.

Go into your browser’s cookie manager and watch the cookies being created in one, take a look at them, then go into the other and watch the cookies change.

There are several settings that could be out of sync so it’s hard to guess without more info.

You also haven’t stated what versions of each program you are using.

[_ck_]

Well it still looks a bit like a forum, but the concept is solid, keep going!

In fact someone once went as far as changing the whole structure to work like a blog, can’t remember who right now, they were trying to make a whole plugin for it.

Note that you can change the templates even further and put snippets of the post under the title on the front/forum pages – bbPress is very flexible like that since it’s cleanly divided between the backend and front-end.

Believe it or not there is at least one person using bbPress as an advanced image sharing gallery, the possibilities are almost endless.

[_ck_]

honestscott, any update on this?

Even 1.x should not be causing slow queries, something might be misbehaving.

My Super Search plugin DOES do a very heavy non-indexed query, it’s unavoidable. But unless you have a large forum with frequent searches, I am not sure that would get you in trouble.

The good news is if you’ve moved to a VPS (I assume that’s what “semi-dedicated server” means) you have direct control over a few important things you didn’t have before. It means we can make sure your MySQL cache is on (it’s off by default on many setups for some strange reason) and you can install an opcode cache like eAccelerator which will cause a fantastic reduction in load and improve speed.

[_ck_]

I should probably submit this as a real plugin.

It’s so small though I guess I’ll keep it in my bb-tweaks collection.

[_ck_]

Is it possible to copy over the “stats” code from the WP plugin section to bbpress.org, or is it more complex than that?

ie. https://wordpress.org/extend/plugins/wp-e-commerce/stats/

vs. https://bbpress.org/plugins/topic/bbpress-signatures/stats/

Even without the fancy graph, just the little History section would be handy.

I’m debating doing another full survey of active bbPress installations by the end of this year despite it’s replacement, but it’s still easy to believe it’s well over 10,000 – might even be 20,000 or higher if the growth has become exponential.

ps. somewhat related: the tag import (from readme.txt) in the plugin section has been broken since the bbpress.org 2.0 upgrade

[_ck_]

Actually 3.0.1 is long overdue, either hiding the bugs or just ignoring them, I’ll be polite and not assume the motivation. I just hope people aren’t being made to suffer just to win the bet:

https://core.trac.wordpress.org/query?groupdesc=1&group=severity&milestone=3.0.1&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&row=description

https://core.trac.wordpress.org/query?groupdesc=1&group=severity&max=1000&milestone=Awaiting+Review&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&row=description

https://core.trac.wordpress.org/query?groupdesc=1&group=severity&max=1000&milestone=3.1&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&row=description

https://core.trac.wordpress.org/query?groupdesc=1&group=severity&max=1000&milestone=Future+Release&order=priority&col=id&col=summary&col=owner&col=type&col=priority&col=component&col=version&row=description

[_ck_]

Here is a version I super modified for maximum performance and compatibility.

http://pastebin.com/embed_iframe.php?i=N4bxcqpZ

It avoids the extra queries the original version does (when it looks for page-topics plugin/option) and caches a few expensive variables.

It uses pure css with an inline stylesheet so there are no externals to load or check timestamps.

(basically in plain english it puts as little impact as possible on the page)

If someone REALLY wanted the page image it could be easily modified to support that again.

This version only shows the ending page, or if over 5 pages the last two pages, which I think is plenty. (clicking the topic title is always page one anyway)

[_ck_]

That’s strange because pluggable functions should step out of the way if they are already defined before it gets to it.

For some reason the plugin is loading AFTER the pluggable loads, instead of before. I can’t quite explain that.

Try renaming the plugin by putting an underscore in front of the name, ie.

_https-mode.php

and make sure it’s directly under my-plugins/ and not in a sub-directory under it.

That’s the only idea that pops into my head right at the moment.

ps. make sure you are using the newest one so far here:

http://pastebin.com/embed_iframe.php?i=wSYPsdjT

[_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.

[_ck_]

_ck_… you’d rather let bbPress die than let it be reborn and successful as a plugin?

To clarify, I’d rather see the name “bbPress” be retired than recycle the name for another purpose when there are years of development and history already in existence.

I have no problem with you/automattic/whomever making a new forum program, zero problem with it and I honestly wish you the best.

My problem is calling it “bbPress” when it has virtually nothing to do with the original bbPress project. Even worse, it’s being called bbPress 1.2 which is downright weird. 1.2 implies updates to 1.1 – but this is a complete rewrite into something else.

The only reasons I can conclude why it’s being called bbPress is because Automattic/Matt already owns the name, and y’all can’t think of another name or simply don’t want to bother.

Like I said before, and feel it’s worthy of explaining again: What if the WordPress core was suddenly completely re-invented on a whim, breaking all compatibility, and it was simply called “WordPress 3.1”. Wouldn’t that be really dumbfounding and confusing to the community?

@gswaim – the reason why this topic isn’t being closed, is because this is the most conversation we’ve EVER had about bbPress’s future/politics. Even during the backPress changeover we had nothing really like this, just bits and pieces. Matt would make a decision and we’d hear about it a month later during an interview or speech.

I believe this talk/venting is good and healthy as long as it’s not done by attacking individuals personally.

And I’d rather see it all focused here in this topic than a dozen topics eventually created on the subject, (especially since after all these years we still do not have a topic merge function in the api).

But if you want it closed in the hopes it will end people’s feelings on the subject, that’s not really how people behave/think is it?

[_ck_]

This utility has been delayed a bit as a few things came up this weekend but I fully intend to finish it soon.

Thanks for volunteering citizenkeith, I’ll keep you posted.

[_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.

[_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)

[_ck_]

Well actually I am typically fairly quiet about the back end stuff and community politics.

But I’ve regretted over the past year or two not voicing enough concern at the start over backPress so now I simply do not want to see another big mistake, the bbPress name hijacked for a third, completely different forum program.

My request is quite simple: do whatever else you’d like but please do not call it bbPress when it has no relationship with any previous version of bbPress.

If bbPress truly is an open source community project and not exclusively owned/managed by Automattic, well then here’s the chance to prove that.

If Matt suddenly announced that WordPress would radically change from 3.0 to 3.1 and out of the blue use a newly developed core that completely invalidated all existing themes, plugins, utilities and knowledgebase – wouldn’t you be just a little bit concerned and upset? Would you speak up or “go with the flow” ?

In the above scenario, if you were new to WP 3.1, you wouldn’t care and would wonder why people were complaining so much. But if you had a few years invested, maybe you’d feel a little differently. Maybe you’d ask them to leave the old version alone and call it something else.

[_ck_]

By the way, Matt owns talkPress.org and it’s not being used.

So there’s a solution. With a new name, it’s clearly a different product and there are no expectations and no conflict.

I’d promise not to join or comment on it in any way and you can start with fresh faces ignorant of any legacy baggage.

[_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.