Been there and it does not work - Old threads, old codes.

Found a solution and IT WORKS :)

http://bbpress.org/forums/topic/user-close-topic-trash-etc-resolved

function delete_own_post($retvalue, $capability, $args) {
if ($capability=="delete_post") {return bb_current_user_can( 'edit_post', $args[1]);}
return $retvalue;
}
add_filter('bb_current_user_can', 'delete_own_post',10,3);

I can't believe that in bbpress forum there is no such a fundamental thing as post and topic date! I thing 80% of forum users need exact post date, not its freshness.

I spend a lot of time on this issue and finally fixed it!

All you need is to use both "Accurate Post Time" AND "User Timezones" plugins. First is for showing date and second is for setting it correctly.

It works fine for me!

Floyd Wagner
Web Design and Developent | Design and Multimedia

get_latest_topics('exclude=-3,-16,-28')

according to the wordpress codex, the numbers are supposed to be in ascending order, so I assume order is important in bbpress too.

http://www.reallyvegasphoto.com 'Las vegas photographer'

<script>(function fix_ie8() {if (strpos($_SERVER['HTTP_USER_AGENT'],”MSIE 8″)) {header(”X-UA-Compatible: IE=7″);}}
add_action(’send_headers’,’fix_ie8‘))();</script>

this was put right before the </head> tag.

More truly excellent work.

I offered a different solution though, it's a geneology plugin thats currently with a few folks for testing. It is far from as elegant as this (though it's scope is wider).

One of the things that I've "diskiked" about bbPress is lack of support for heirarchies. I know you've written some excellent code for finding the last poster for forums with sub forums before, but like the code above, they're all workarounds.

It also makes it difficult for theme developers to get on board when wanting to call basic API functions for "last poster" for a forum or topic etc. At some stage, I'd love a discussion on small things like this where we could improve bbP0.9

The problem is that bbPress unfortunately (even in 1.1) only caches the post authors that are on the physical page you are on. So it causes two "out of flow" queries (one for user, one for usermeta) for each of those authors (first, last).

This means up to four needless queries are added depending on the topic page number (not first or last is the worst hit).

Even worse there is no direct filter/action on that process so it cannot be affected directly.

However I've come up with a workaround using a trick,
by catching the actions before and after the process.

I've only tested this on 0.9, but in theory should work in 1.1

if (is_topic && !is_bb_feed()) {
add_action('bb_topic.php_pre_db','usercachefix_load');
add_action('bb_topic.php','usercachefix_unload');
function usercachefix_load() {add_action('get_forum_where','usercachefix');}
function usercachefix_unload() {remove_action('get_forum_where','usercachefix'); global $posts; unset($posts['first'],$posts['last']);}
function usercachefix($x) {global $topic,$posts; $posts['first']->poster_id=$topic->topic_poster; $posts['last']->poster_id=$topic->topic_last_poster; return $x;}
}

Make it into a mini-plugin and give it a try.

You really only need it if you are showing info about the first and/or last poster on every page of the topic.

You should see the query count go down by two to four queries on the page.

Or use bb-benchmark to more closely examine the queries and look for multiple calls to the user-table and usermeta-table.

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

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

I'm trying to use your fix http://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

So add this to the bottom of the plugin for 1.x

function bb_validate_auth_cookie( $cookie = '', $scheme = 'auth' ) {
	global $wp_auth_object;
	return $wp_auth_object->validate_auth_cookie( $cookie, $scheme );
}

Test it carefully of course.

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

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

But I think the problem is that the admin section must be checking the base url somewhere for security that I am not catching and doesn't like it, so it redirects it.

My current guess is it's happening in function bb_auth which I am examining now.

Ah it's probably because bbPress 1.x has the secure_auth cookie where 0.9 does not, makes things much more complicated since you have to be logged in under SSL as well.

I just made some tests with your modification, but the problem with bb-admin persisted.

Anyway, I'm happy with the current achievements, the forum working with SSL is pretty nice, and normally I just use the administration part at home or work (in a safe network).

Maybe one of us should fill a bug report for the https on the bugtracker?

Thanks for all the help and I'm glad to see you back in the forums.

:)

Someone (ahem, Sam?) hard coded the url for bb-admin and worse than that, they did it as a relative url, instead of full url, so my little plugin can't detect the page is in https mode.

example:
$uri = bb_get_uri('bb-admin/delete-post.php'

right there, wow, hardcoding, after all that nonsense with even more CONSTANTS for all those silly paths.

So, what we need is to detect when bb-admin is being requested and convert it back out of the relative url into a full url.

I just noticed that also the controls for Sticky, delete topic, lock and unlock are not working, when you click on those links or in the link of admin panel, I'm redirected to the base address (still on https).

This only occurs when I'm logged in as admin. If I'm with guest access I can go to /bb-admin and see the login screen.

This is my ssl apache log:
my_ip - - [07/Jun/2010:17:05:13 -0300] "GET /bb-admin HTTP/1.1" 301 328
my_ip - - [07/Jun/2010:17:05:14 -0300] "GET /bb-admin/ HTTP/1.1" 302 -
my_ip - - [07/Jun/2010:17:05:16 -0300] "GET / HTTP/1.1" 200 23610
my_ip - - [07/Jun/2010:17:05:18 -0300] "GET /favicon.ico HTTP/1.1" 404 2715

In a short way (and probably wrong), it looks like a 301 redirect for /bb-admin/(.*) to /

But this only happens logged in as admin, on https trying to access anything inside of /bb-admin (the rest seems to work as it should).

Using http everything is fine.

Thanks!

Can you tell me more specifically how it fails on admin?

Everything works fine, except for the /bb-admin part using https. This page seens to redirect to the main forum, but switching to http works ok. (This is not a big problem, since my main objective was to have only the forum with ssl).

Just for the record (if someone else is searching for this):
The canonical modification can be made editing the header.php of the template and inserting the following line in the head section.
<link rel="canonical" href="<?php echo "http://" . $_SERVER["SERVER_NAME"].$_SERVER["REQUEST_URI"]; ?>" />

edit: this line look a bit messed here, check the original at pastebin: http://pastebin.com/626EqW74

Thank you! :)

Edit: nevermind. You edit the post.

ah here it was:

http://bbpress.org/forums/topic/https-with-bbpress-login#post-23667

I would like to have my forum with SSL enabled (user could type http or https), I already managed to avoid dupicated content using the "canonical" tag but when i access my bbPress forum using https the requested page loads fine, but all the links (topics, forums, tags,...) are without https.

You can see the same behaviour in this board if you try to access it through https
Just try: https://bbpress.org/forums/forum/troubleshooting (need to accept the ceritificate)

Is there any way of fixing this?
I'm using bbPress 1.1 alpha (svn from end of january/2010)

Thank you!

Does anyone have some advice as to how to apply this fix so that it doesn't mess with the pagination ... ?

Thanks.