This will likely break things. What theme are you using? Link to your site?
- Use a regular old WP_Query()
- Use a widget
- Use bbp_has_forums()
- Use the shortcode mentioned above
There are lots of examples, in the forums, on the codex, and in the bbPress code itself. Also, unclear what you mean by “latest forum.” Do you mean topics, or replies, or something else?
Modifying core files is never the way. There are plenty of filters in place to override any bit of functionality regarding bbPress’s theme compat,
There are, as you’ve already found, numerous vectors depending on exactly what you want to accomplish. Each filter has an intended purpose, and solves a specific problem. The underlying code is identical to WordPress’s own template loader, until a template isn’t found (which is a majority of installations.) In that case, bbPress replaces the_content with template parts using page.php, or whatever is a match in the stack you found already.
Also, don’t forget about the typical WordPress templates: archive-forum.php, and archive-topic.php, etc…
To answer your question about why get_the_ID() doesn’t work on archive pages, why would it? It’s an archive, not a post/page. There is not ID to get.
From your posts here, you’ve basically solved much of what’s already in the codex regarding how some of these things work; also, I’m fuzzy on what problem you’re trying to solve. What is the end goal you’re working towards? I can give you some advice on what I think will work best.
And that table is stored in a folder on the host server, correct?
Where else would it be? 🙂
Exactly like you’d expect:
- Create a page with the slug ‘topics’
- Use the ‘bbp-topic-index’ shortcode in the page content.
- Done.
@sooskriszta – your theme is using query_posts() or is misbehaving in some other way. Maybe creating a WP_Query() that it’s resetting? Either way, I can remove that bit, but bbPress needs to take care to only intercept ‘the_content’ filters when it’s supposed to.
If they are on the same multisite WordPress installation, yes.
* Visit Tools > Export on the site you want to move.
* Export your data.
* Visit Tools > Import on the destination site.
* Import the data.
@mickeyroush – Annoying. Usually bumped automatically. Will fix. Thanks.
@technotip – If there’s only one theme, the option is hidden.
That’s one way to do it, sure. Either way, you’ll need something like that if you want to keep the old style profiles around. Nice work.
@steveatty – Fixed in trunk. Thanks!
It’s most likely bbPress’s fault, being too strict on clearing out the CSS for lists.
I’ll make sure this happens in 2.3.
It’s a bit difficult to wrap your head around at first, but the reason theme compatibility exists, is because you should not modify code/templates that come with plugins or themes. When using a plugin like bbPress, and a theme that isn’t yours, you need some other way to introduce code into WordPress.
You can use either a plugin, or a child theme to do this.
You’ll want to research both methods, and figure out which one suits your situation and needs.
That’s true. Unfortunately before bbPress 2.2, users had to go digging to assign forum moderator capabilities to users with existing WordPress roles, so we indirectly drove users towards that solution already. :/
Put this in mu-plugins, or make a plugin out of it, or put it in your functions.php file of your theme. Probably will want to rename “foo” though.
function foo( $args = array() ) {
$args['teeny'] = false;
return $args;
}
add_filter( 'bbp_after_get_the_content_parse_args', 'foo' );
That’s not a great solution, because you’re missing out on all the other things that hook to the_content otherwise.
Are you using query_posts() anywhere? Are you not using wp_reset_query(); when your WP_Query’s are done?
Use your favorite FTP program.
Can you be more explicit about what broke with what version? If it was 2.2.2, try reinstalling 2.2.2.
The editor here is the basic WordPress editor with some CSS tweaks; something anyone with a spare hour should be able to put together.
Changed to bbp_single_user_details_avatar_size in the branch, will be 2.2.3, which has no date set yet. You can safely modify that code in your file if you’d like, any future update will include it.
Ah; yeah. That was fixed over an hour ago, when the bug crept in. I force-busted the theme-cache again to be safe.
