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.
Left over from the old templates. Should probably be something else, yeah.
I don’t get this I can’t read the replies on here?
Can you be more specific? I don’t understand what that means.
It’s not that crazy. bbPress has used this pattern for almost 9 years now.
- /forums/ is your root
- /forums/forum/slug/ is a single forum
- /forums/topic/slug/ is a single topic
- /forums/users/slug/ is a single user
Regarding your theme, a quick read through some topics here will help you. Try with a default theme, refresh your permalinks, etc…
Redownload/reinstall 2.2.2; was another hiccup in the zip and was quickly fixed.
Sorry about that. These things are difficult to catch.
It’s most likely not because of this. Even here at bbPress.org, the header, sidebar, and footer all create new WP_Query objects without any issues.
bbPress 2.2 even adds additional checks for is_main_query() and in_the_loop() to make sure this doesn’t happen.
Partially. The roles and capabilities in 2.2 have all the filters and hooks in place to allow for this to happen in future versions, though there’s no UI for it currently.
Forum VS Role VS User permissions are going to be tricky to handle in WordPress. We’ll most likely need to get creative with where the relationship data is stored, using the taxonomy table or something similar.
Since I can’t see your forums at all, it’s impossible to be helpful. Private forums are for registered users only.
