I think this is worth discussing since it seems to be a core philosophical issue that comes up a bunch, with people citing text I wrote for the about page!
The general rule we’ve followed in WordPress, which has been successful for user adoption, has been that something is “core” functionality of it is something the vast majority (80%+) will appreciate, or if it something that makes WP more robust even if they don’t care about it (revisions), or if it’s something we want to promote because we think it will make WP or the web an intrinsically better place (oembed).
Something might be a hugely popular plugin but not perfect for core because: it ties in a commercial service (Akismet), it needs to update more frequently than core does (faster dev cycle), or it adds more overhead than is worth it. For the last, we can often bring in the bare minimum or framework into core and leave the rest as a plugin (podcasting support in WP, and PodPress, or SEO improvements we make).
A bonus of core is that (in theory) the code gets better reviewed, can be relied on by new plugins to be there and build on, and maintained as part of the overall package. It also often brings new folks who may have just worked on plugins before into improving core which increases exponentially the impact of their work.
Of course there is lots of common sense along the way, this is just meant as a general framework for approaching the problem.
Okay let’s assume the host is doing something weird.
Make a temporary file in the same directory that you want the log to be.
ie. test.php
put this in the file
<?php echo __FILE__; ?>
Then access it from the web, ie. example.com/my-plugins/browser-timer/test.php
Whatever it shows you, change the ending test.php part to browsertimer.log
and then put it inside
$browsertimer['log']='full line here';
Now that has to work, as long as the my-plugins/browser-timer/ directory is chmod 777.
I have deleted the .log file. I’ve made the modifications in browser-timer.php
$browsertimer=dirname(__FILE__).'/browsertimer.log';
The weird thing is that I can no longer see the .log file being created and I get the same log open error
My permissions on the folder are 777, as I said before.
Another thing is that I am getting a 550 Permission Denied in Filezilla when I try chmod, but it’s ok in their filemanager. Even Filezilla tells me that I have 777.
Any other ideas?
Bob
LOL. 
Security is an excellent reason to upgrade (whether terrified or not) but it should be noted that 3.0 contains no security fixes, so it’s no more secure than 2.9.2. (Yes, it’s been that long since a security release. This doesn’t mean there isn’t anything hiding in the code, but we don’t know about it yet and the frequency between issues being brought up is going down even as our popularity is growing, which I hope means we’re becoming more intrinsically secure.)
I was able to easily solve my issue by finding one careless mistake. In my wp-config.php file I simply copied the authentication keys (4 of them) and pasted them into my bbpress’s config.php file. What I did not notice is that in wp-config.php they keys are prefixed like this:
define(‘AUTH_KEY’,’my unique key is here’);
While in the bbpress config.php, the keys are prefix like this:
define( ‘BB_AUTH_KEY’,’my unique key is here’ );
The only difference is AUTH_KEY versus BB_AUTH_KEY, but that made the difference. Hope this helps technotip…
thanks _ck_ for emphasizing the auth keys
I just had a suggestion – when the plugin would be public and this site’s posts converted, we could have an if statement above the topic like
if ( topic_date is before bla bla date || one of the topic_tags == 'bb_old' ) { /* load a message which says that this is for bb 1.1 and below, this doesn't apply to the new plugin */ }
But I’m also not against changing its name or having its version as 2.0.
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)
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!
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 
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.
hey kevin,
thank you for stepping in with a helping hand, i appreciate that a lot.
but i had sadly though luck with your code so far.
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.
Hello again.
I cannot get it to work yet. Jolly well!
So, my Filezilla path is: /pastorbob.limewebs.com/my-plugins/browser-timer/
But my FTP is ftp://ftp001101.limedomains.com/pastorbob.limewebs.com/my-plugins/browser-timer/
I have changed this to what you’ve told me: $browsertimer['log']=$_SERVER['DOCUMENT_ROOT'].'/pastorbob.limewebs.com/my-plugins/browser-timer/browsertimer.log'
Then I’ve tried the other option as well: $browsertimer['log']=$_SERVER['DOCUMENT_ROOT'].'/ftp001101.limedomains.com/pastorbob.limewebs.com/my-plugins/browser-timer/browsertimer.log'
I thought that I might have been on to something. But I wasn’t.
Thank you for your help, again!
Regards,
Bob
Hi Johnny,
You need to pass the user id into the avatar function.
I’m not near my code righ tnow, but you’re looking at something like this:
get_avatar(poster->id);
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.
a killer theme guys, respect!
anyway, i’m curious on how you was able to get it work with the last poster and last topic avatar for front-page.php.
i’ve already tried it months ago with <?php post_author_avatar(); ?> between td’s but for some reason i get the same static gravatar for all users.
thank’s in advance.
Hello.
I have an account on limedomains.com
My home directory is pastorbob.limewebs.com
So, I figured that this should be my setting in browser-timer.php
$browsertimer['log']=dirname($_SERVER['DOCUMENT_ROOT']).'/pastorbob.limewebs.com/my-plugins/browser-timer/browsertimer.log';
I set the permission for browser-timer to 777.
I created a file called browsertime.log
But when I go to http://pastorbob.limewebs.com/?browsertimer , I get log open error
Is it just me?
Regards,
Bob
WOW, Welcome Back Matt, Its nice to see you .
I’ll be very happy if you can reply for my post.
Should I Stop Using bbpres Standalone Version Right Now?
Can you please?
I’ve just tested bbPress 0.9 with WP 3.0’s cookies and the Freshly Baked Cookies plugin DOES work properly.
Just make sure your cookie paths for WordPress and bbPress are pointing the same place (ie. /) which was always required for proper integration anyway and is not done by the plugin but inside wp-config and bb-config – see the numerous integration guides around bbpress.org
Make certain you are using version 0.0.4 of the plugin or higher which supports the newer kind of WordPress cookies in use since WP 2.8
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.
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
I have the same problem on my blog, and I was thinking its just me
Thanks jmharrington for taking time to write here.
Can anyone help us?
@gswaim If it comes down to name calling or aggression, that’s always an option, but usually the last one if we can all help it. Fortunately the moderation team over here is fantastic, so no worries there.
The decision to allow Pete and myself the opportunity to do the bbPress plugin conversion wasn’t only Matt’s to make, and was agreed on by a committee of all of our peers running the 3.org initiatives, in #wordpress-dev on freenode, and on the WordPress development blog.
The reason it’s bbPress 1.2 rather than bbPress 2.0 (at least as it stands today) is because part of the coding standards we adhere to is not inflating version numbers. Could always see if everyone agrees to inflate based on the amount of new code going in, but I don’t think that’s my decision to make, and I would wager that it’s unlikely to happen? Been wrong before though.
@chrishajer yep, I honestly didn’t think it would be a problem. Guess I learned my lesson ! Thanks for those links, that’s much easier than searching.
I’ll look to see if a similar bug has been filed first.
Tomek
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
