[John James Jacoby]

Yes, but the structure can be filtered/adjusted as needed by a theme or plugin too.

[gunnsean]

I use bbPress to run a trouble-shooting site. So when labeled closed that means the problem is solved.

I want to exclude [closed] topics from latest discussion in the front page. Is there anyway to do so? Sadly my expertise don’t lie in PHP.

[alexchenco]

The default works OK:

http://localhost/taiwantalk/?bbp_forum=technology

But setting the Permalinks to Month and name gives me a no found page.

http://localhost/taiwantalk/forums/forum/technology/

mod_rewrite is working as usual.

Any suggestions?

[Mike]

The same problem . Anyone have any ideas?

[Mike]

The same problem . Anyone have any ideas?

[cclynes]

Hi

I am relatively new to wordpress and bbpress and I am trying to install a forum onto one single page in my wordpress blog.

I installed BBpress but now when I try to visit my sie it takes me to my BBpress log in (please see http://www.the8lossplan.com)

I did not want my whole blog to be a forum, have I put the files in the wrong folder or is there something else I have done wrong?!

Please help – for a university project I absolutely have to finish tonight

Thanks!!

If anyone knows how to set this up for me I’m happy to give them my details to help set up?

I am using GoDaddy as my webhosting.

[mr_pelle]

Shocking news… No official annoucement, no changelog, 1.0.3 milestone (11 months late!!) still open, an installation-blocker bug still open (for MySQL 5.5 users only).. WTF?!

Thank you _ck_ for the sticky! If I were looking at my feeds from TRAC I’d be still thinking 1.0.3 was just a dream…

[mr_pelle]

Shocking news… No official annoucement, no changelog, 1.0.3 milestone (11 months late!!) still open, an installation-blocker bug still open (for MySQL 5.5 users only).. WTF?!

Thank you _ck_ for the sticky! If I were looking at my feeds from TRAC I’d be still thinking 1.0.3 was just a dream…

[tooltrainer]

Well… maybe not the “proper” answer but by hacking together the bits of single-reply that check to see if you’re logged in, with single-topic.php, I was able to get it to do a login check on the actual topics themselves too. So everything appears to be fine. If anyone knows of any nasty surprises I could encounter by this approach, please do let me know.

Jonathan

[_ck_]

Sounds like it’s a bug with the scope of the $user variable.

If it’s not fixed in 1.0.3 maybe they fixed it in 1.1 which will have a release candidate soon.

There’s also a chance it’s a bug with a customized template.

[_ck_]

Sounds like it’s a bug with the scope of the $user variable.

If it’s not fixed in 1.0.3 maybe they fixed it in 1.1 which will have a release candidate soon.

There’s also a chance it’s a bug with a customized template.

[John James Jacoby]

Correct. 1.0.3 contains several security fixes to the existing 1.0 branch of code, which means no new major features or changes happened and it includes fixes to existing bugs.

1.1 will see a release candidate soon.

There was no announcement for 1.0.3 because when I tagged it, it required a new tag of BackPress and BuddyPress needed to be changed too. With 1.1 and the plugin coming soon, it just never got an official announcement.

On a more personal note, my resources and bandwidth are spread between several projects at the moment, so switching contexts quickly is something I’m adjusting more to. An announcement about 1.0.3 will happen when an RC for 1.1 goes out, which should be in the next few days.

[John James Jacoby]

Correct. 1.0.3 contains several security fixes to the existing 1.0 branch of code, which means no new major features or changes happened and it includes fixes to existing bugs.

1.1 will see a release candidate soon.

There was no announcement for 1.0.3 because when I tagged it, it required a new tag of BackPress and BuddyPress needed to be changed too. With 1.1 and the plugin coming soon, it just never got an official announcement.

On a more personal note, my resources and bandwidth are spread between several projects at the moment, so switching contexts quickly is something I’m adjusting more to. An announcement about 1.0.3 will happen when an RC for 1.1 goes out, which should be in the next few days.

[edith g]

Can anyone advise me where exactly to add the code for a paypal donate button if I wan it to show on my main bbpress page? I appreciate it. Thanks.

[bonnie808]

Thx guys, i know how you feel. Hopefully a Dev can reply with a final answer to this seemingly easy fix

[bonnie808]

Thx guys, i know how you feel. Hopefully a Dev can reply with a final answer to this seemingly easy fix

[Ben L.]

In bbpress.php, topics and replies have 'revisions', as one of their features. Comment out those two lines.

[Ben L.]

In bbpress.php, topics and replies have 'revisions', as one of their features. Comment out those two lines.

[_ck_]

These are the changes between 1.0.2 and 1.0.3

https://trac.bbpress.org/changeset/2958/tags/1.0.3?old=2339&old_path=%2Ftags%2F1.0.2

unfortunately the mime property was modified on files that were otherwise unchanged, so the file list looks huge, but most of them are unaffected.

also /jquery/interface.js was added in 1.0.3 but for some wrong reason they are using the packed version which is slower because it has to be unpacked on every page load, it should be the minified only version without packing and just let gzip do the compression work between the server and the browser

I’ve edited down the list and removed the property-only changes

Files changed between bbPress 1.0.2 and 1.0.3

bb-templates/kakumei/style.css (1 diff)

bb-templates/kakumei/favorites.php (1 diff)

bb-templates/kakumei/view.php (2 diffs)

bb-templates/kakumei/forum.php (2 diffs)

bb-templates/kakumei/tag-single.php (1 diff)

bb-templates/kakumei/front-page.php (2 diffs)

bb-templates/kakumei/post-form.php (2 diffs)

bb-templates/kakumei-blue/style.css (1 diff)



bb-includes/functions.bb-users.php (3 diffs)

bb-includes/functions.bb-pluggable.php (3 diffs)

bb-includes/class.bp-options.php (1 diff)

bb-includes/functions.bb-posts.php (1 diff)

bb-includes/functions.bb-template.php (4 diffs)

bb-includes/functions.bb-meta.php (1 diff)

bb-includes/functions.bb-core.php (3 diffs)

bb-includes/functions.bb-deprecated.php (1 diff)



bb-cron.php (3 diffs)

bb-login.php (3 diffs)

rss.php (1 diff)



bb-admin/tools-recount.php (2 diffs)

bb-admin/includes/class.bb-install.php (1 diff)

bb-admin/includes/functions.bb-upgrade.php (3 diffs)

bb-admin/includes/functions.bb-admin.php (4 diffs)

bb-admin/includes/defaults.bb-schema.php (2 diffs)

bb-admin/includes/functions.bb-recount.php (added)

bb-admin/admin.php (2 diffs)

bb-admin/admin-base.php (1 diff)

bb-admin/index.php (2 diffs)

There may be additional backPress changes which are beyond my desire to track/list.

[_ck_]

These are the changes between 1.0.2 and 1.0.3

https://trac.bbpress.org/changeset/2958/tags/1.0.3?old=2339&old_path=%2Ftags%2F1.0.2

unfortunately the mime property was modified on files that were otherwise unchanged, so the file list looks huge, but most of them are unaffected.

also /jquery/interface.js was added in 1.0.3 but for some wrong reason they are using the packed version which is slower because it has to be unpacked on every page load, it should be the minified only version without packing and just let gzip do the compression work between the server and the browser

I’ve edited down the list and removed the property-only changes

Files changed between bbPress 1.0.2 and 1.0.3

bb-templates/kakumei/style.css (1 diff)

bb-templates/kakumei/favorites.php (1 diff)

bb-templates/kakumei/view.php (2 diffs)

bb-templates/kakumei/forum.php (2 diffs)

bb-templates/kakumei/tag-single.php (1 diff)

bb-templates/kakumei/front-page.php (2 diffs)

bb-templates/kakumei/post-form.php (2 diffs)

bb-templates/kakumei-blue/style.css (1 diff)



bb-includes/functions.bb-users.php (3 diffs)

bb-includes/functions.bb-pluggable.php (3 diffs)

bb-includes/class.bp-options.php (1 diff)

bb-includes/functions.bb-posts.php (1 diff)

bb-includes/functions.bb-template.php (4 diffs)

bb-includes/functions.bb-meta.php (1 diff)

bb-includes/functions.bb-core.php (3 diffs)

bb-includes/functions.bb-deprecated.php (1 diff)



bb-cron.php (3 diffs)

bb-login.php (3 diffs)

rss.php (1 diff)



bb-admin/tools-recount.php (2 diffs)

bb-admin/includes/class.bb-install.php (1 diff)

bb-admin/includes/functions.bb-upgrade.php (3 diffs)

bb-admin/includes/functions.bb-admin.php (4 diffs)

bb-admin/includes/defaults.bb-schema.php (2 diffs)

bb-admin/includes/functions.bb-recount.php (added)

bb-admin/admin.php (2 diffs)

bb-admin/admin-base.php (1 diff)

bb-admin/index.php (2 diffs)

There may be additional backPress changes which are beyond my desire to track/list.

[_ck_]

bbPress 0.9 users should install my unofficial “block-long-queries” mini-plugin to avoid the security bug that 1.0.3 fixes and similar unknown attacks in the future.

(it also works in 1.0 and WordPress)

<?php

/*

Plugin Name: Block Long Queries (for bbPress and WordPress)

*/



if (strlen($_SERVER['REQUEST_URI'])>255 ||

preg_match('@(eval|base64|unescape)[^a-zA-Z0-9]@si',$_SERVER['REQUEST_URI']))

{

header('HTTP/1.1 414 Request-URI Too Long');

header('Status: 414 Request-URI Too Long');

header('Connection: Close');

exit;

}

[_ck_]

bbPress 0.9 users should install my unofficial “block-long-queries” mini-plugin to avoid the security bug that 1.0.3 fixes and similar unknown attacks in the future.

(it also works in 1.0 and WordPress)

<?php

/*

Plugin Name: Block Long Queries (for bbPress and WordPress)

*/



if (strlen($_SERVER['REQUEST_URI'])>255 ||

preg_match('@(eval|base64|unescape)[^a-zA-Z0-9]@si',$_SERVER['REQUEST_URI']))

{

header('HTTP/1.1 414 Request-URI Too Long');

header('Status: 414 Request-URI Too Long');

header('Connection: Close');

exit;

}

[Super Artsy]

Alright, well I find a solution to my problem with a bit of SQL language tweaking. Apparently the issue deals with my MySQL version, but all I had to do was make a simple edit changing ‘TYPE’ to ‘ENGINE’.

So the line:

) TYPE = MYISAM DEFAULT CHARACTER SET 'utf8';

becomes:

) ENGINE = MYISAM DEFAULT CHARACTER SET 'utf8';

I hope this helps those who encounter the same problem.

Cheers.

[Super Artsy]

Alright, well I find a solution to my problem with a bit of SQL language tweaking. Apparently the issue deals with my MySQL version, but all I had to do was make a simple edit changing ‘TYPE’ to ‘ENGINE’.

So the line:

) TYPE = MYISAM DEFAULT CHARACTER SET 'utf8';

becomes:

) ENGINE = MYISAM DEFAULT CHARACTER SET 'utf8';

I hope this helps those who encounter the same problem.

Cheers.

[John James Jacoby]

This used to work but is was accidentally broken in a recent commit. Will be working soon.