@kreestal: I'm happy to know you found out what was causing the problem!
Regarding the new issue, what do you mean with "bbPress latest version"? 1.0.2 or trunk? Also, did you update my plugin to its latest version?
Version: 5.0.7
Last Updated: 2011-4-3
Requires bbPress Version: 1.0 or higher
Compatible up to: 1.1-alpha





@kreestal: I'm happy to know you found out what was causing the problem!
Regarding the new issue, what do you mean with "bbPress latest version"? 1.0.2 or trunk? Also, did you update my plugin to its latest version?
I'm using bbPress 1.0.2, and Nicer Permalinks version 5.0.1 :)
@kreestal: ok, I'll check out the plugin on a 1.0.2 installation during the next days. I'll keep you updated.
@kreestal: it turned out it was our old friend bb-post.php, which I hoped not to have to edit anymore... Unfortunately, you still have to (on bbPress 1.0.2 or lower):
If your bbPress version is 1.0.2 or lower, open
bb-post.phpand switch lines 46 and 48. They must look like this:$topic = get_topic( $topic_id, false ); $link = get_post_link( $post_id );
I've updated the readme on version 5.0.2.
Indeed it works smoothly now. Is there any chance bb-post.php will be corrected by the dev team during the next bbpress update ?
Thank you very much for your help and quick feedback, I wish all plugin developers would do the same :-)
hi
this plugin is great , i'm using it on my website
but the is a conflict with the "bbPM" plugin .
is there a way to force your plugin to ignore adress like that : http://mysite/PM/...........
help me :p
@blank4rt: hi! What version of bbPress are you on? I'll take a look at the conflict immediately!
Bug fixed, in a weird way, but fixed. =)
Uploading new version!
hi
i've found a way to make it work > edit the bbpm plugin > make the plugin open a "xxxx/index.php" & not a "xxxx/" directory path.
but
your modded plugin is greater than my trick!!
thanks for your reactivity !!
see you , & sorry for my bad english...
'm using bbpress 1.0.2, it works great now ;)
hmm, I have the exact same bbPM issue. I tried upgrading to your new version but still seem to be having a conflict with bbPM. It won't let me view threads, and instead, kicks me out to the 1st topic in the database. I'm also using bb 1.0.2
My bad - I think I deleted the old version of the plugin wrongly.
It works now. THANK you for making bbpress a better place!!
@mr_pelle - there is still a conflict with nicer permalinks.
If you have more than two pages of PMs, the redirect fails. It looks like this:
http://mysite.com/bbpress//page/2/
And the typical error:
BBPRESS FORUM ยป PAGE NOT FOUND!
Page not found!
I'm sorry, but there is nothing at this URL.
@guly: I'm currently testing bbPM 1.0.1 on bbPress 1.0.2 <b>with no permalinks activated</b> and bbPM pagination does not work either: does it work for you? I'm getting all PMs on one single page with pagination links on the bottom, but those link to empty bbPM pages...
Works great except that indexed example.com/forum/sample URL's are not redirecting to example.com/sample/. I was able to fix this by adding this above the #forum and #topics rewrite rules in .htaccess:
# redirect /forum directories indexed as /forum/sample
RewriteRule ^forum/(.*)$ /$1/ [R=301,NC,L]
Also, it would be nice to have the option of simply removing the /topic/ slug, as opposed to replacing it with a category name.
@cwdnow: I don't think it's a real problem...
As for the latter question, it's actually impossible: how would bbPress know if you're requesting either a forum or a topic?
@mr_pelle: Thanks for your quick reply. The former question isn't an issue unless your forum directories are already indexed by search engines, as is the case with mine. If they've gained any PageRank, it will be lost without this redirect.
With my latter question, I mean topics would show up as example.com/topic-name, and forums as example.com/forum-name/. By default, bbPress differentiates between the two as example.com/topic/topic-name, and example.com/forum/forum-name/. The differentiator is the backslash, indicating a directory.
The advantage of this is that user created topics that go into the wrong category, and are subsequently indexed by search engines, don't need to be 301 redirected when they're moved.
@cwdnow: ok, now I got it! =) I'll consider your suggestion for a future release of the plugin!
@mr_pelle: Thanks so much! And thanks for all your hard work on this plugin. It's an SEO life saver :)
You must log in to post.