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

[johnnydoe]

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.

[pastorbobsforum]

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

[_KB_]

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?

[_ck_]

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

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

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

[Satish]

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?

[John James Jacoby]

@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.

[namelesshorseman]

@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

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

[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