You are now logged out.
Forum Replies Created
-
That’s a good point daveshine. This might help:
Bugs/inconsistencies:
- “Assign topic to” appears on all forums. That’s okay I guess, but should be an option, not mandatory.
- If a “Resolved” or “Urgent” topic is moved to a non-support forum, the prefix will stay, but there’s no way of removing it as the extra controls don’t exist in this forum. When moving support topics to non-support forums, I would suggest stripping away all extra features entirely.
I seem to remember the first time I did it the process was clean, but in all my last attempts I’ve received this error when moving a topic out of the troubleshooting board:
( ! ) Fatal error: Call to a member function get() on a non-object in C:wampwwwwordpress-singlewp-includesquery.php on line 27
Call Stack
# Time Memory Function Location
1 0.0019 676480 {main}( ) ..index.php:0
2 0.0030 681376 require( ‘C:wampwwwwordpress-singlewp-blog-header.php’ ) ..index.php:17
3 0.0043 702424 require_once( ‘C:wampwwwwordpress-singlewp-load.php’ ) ..wp-blog-header.php:12
4 0.0059 720680 require_once( ‘C:wampwwwwordpress-singlewp-config.php’ ) ..wp-load.php:29
5 0.0083 848040 require_once( ‘C:wampwwwwordpress-singlewp-settings.php’ ) ..wp-config.php:90
6 0.2526 29401072 do_action( ) ..wp-settings.php:206
7 0.2567 30235488 call_user_func_array ( ) ..plugin.php:405
8 0.2567 30235520 bbps_setup( ) ..plugin.php:0
9 0.2571 30236240 bbps_includes( ) ..bbps-premium-support.php:43
10 0.2593 30455272 include_once( ‘C:wampwwwwordpress-singlewp-contentpluginsbbpress-vip-support-pluginincludesbbps-support-functions.php’ ) ..bbps-premium-support.php:94
11 0.2594 30460320 bbps_move_topic( ) ..bbps-support-functions.php:405
12 0.3092 30240600 bbp_update_forum( ) ..bbps-support-functions.php:155
13 0.3092 30243984 bbp_update_forum_last_topic_id( ) ..bbp-forum-functions.php:778
14 0.3171 30283584 bbp_is_topic_published( ) ..bbp-forum-functions.php:426
15 0.3171 30283584 bbp_get_topic_id( ) ..bbp-topic-template.php:963
16 0.3171 30283584 bbp_is_single_topic( ) ..bbp-topic-template.php:361
17 0.3171 30283872 bbp_is_query_name( ) ..bbp-common-template.php:169
18 0.3172 30283872 bbp_get_query_name( ) ..bbp-common-template.php:1322
19 0.3172 30283952 get_query_var( ) ..bbp-common-template.php:1338
I took it for a spin, and here’s my feedback thus far:
A lot of functionality should be in its own plugins.
- Move forum:
I’m surprised this isn’t in core already; I thought it was. In any case, this would make much more sense as a stand-alone plugin, as its useful for all topics, not just support topics.
- Forum Ranks:
As far as I can tell, it doesn’t tie directly in with support topics; it’s a completely separate feature. Maybe you have plans for it, but if that’s the case I still think you should just have two plugins communicate, as this is something many support forums won’t need. I personally dislike forum ranks. I consider it unwarranted labeling. On the jMonkeyEngine forum we frequently see first time posters with 10+ years of Java experience, which is the type of experience that holds weight in our community, not # of forum posts.
- Please separate your settings from bbPress’ options page. Your plugin offers so many options (which by itself is great) that it ends up bloating the options page.
- I think the default setting should reflect the one in this screenshot:
http://s.wordpress.org/extend/plugins/bbpress-vip-support-plugin/screenshot-3.png?r=448946
That part slipped by me in the settings screen, and when I tested the plugin I was puzzled by how I couldn’t change my test support topic to “resolved”.
- What about a widget for the resolved/not resolved drop-down? (Same goes for Assign topic, and possibly some others I haven’t noticed yet). This would make it easier to fit it in with custom themes. This also means admin should have the option to turn off the in-built drop-down.
Oh and as recommended, add the bbpress tag to your plugin. It’s the default bbPress plugin tag, and currently the most convenient way of keeping up with the latest bbPress 2 plugins.
Oh, and I guess I might as well throw this in here:
http://bbpress.org/forums/topic/feature-request-for-importer-group-to-tag
Yeeah, exactly what we needed! Yet another definitive nail in BuddyPress’ legacy forum’s coffin. Can’t wait to make the conversion now. Will start testing this and give you some feedback first chance I get.
Our php limit is 2048M, our mysql key_buffer_size is 512M, and we’re on linux 64-bit.
When we tried to do some testing with bbConverter we ran into memory issues. We’re running on a dedicated server so there’s a good chance the problem lies on our end.
Seeing as you’ve successfully converted a 2-million-posts forum without issues, I’d be very interested in knowing more about any server settings that might have been pertinent to your success.
A basic runthrough of best practice server setup relevant to a major forum conversion would be great. Things like php-limit, caching, Apache modules and so forth. Not looking for anything in depth, just some DOs and DON’Ts.
You’ve got a point there tgiokdi. BuddyPress 1.5 does a good job of helping the user create the necessary pages for the plugin to use.
@noerman your questions are not actually related to shortcodes. You’d be better off starting new individual threads for your different questions.
Getting back on the topic of shortcodes: Just to reiterate what I brought up in the DevPress discussion about embedding forums in pages, I’d be very happy to have something like [bbp-reply-form id=$forum_id].
Fantastic, will start testing right away. A couple questions & suggestions right off the bat:
- Some very simple step-by-step tutorials for the different kinds of set-ups would go a long way. I’m assuming bbPress 1.x also includes BuddyPress, but it’d be nice to know if there’s any kind of distinction where the conversion is concerned.
- In the bbConverter settings you ask for a Table Prefix. Which one do you want, the WordPress prefix (commonly wp_ ) or the forum prefix (e.g. bb_ , wp_bb_ , etc.)?
- In the case of a BuddyPress forum migration, do we really need to keep bbConverter activated for passwords? They should all be compatible already.
@kriskl a poll of sorts has been done already. You just have to look at a plugin’s rating & comments (can we see # of downloads anywhere?) to get an idea of how many people are invested in it.
Would be interested to know what solutions you come up with for this tntc1978.
@Justin given the fact that this version of bbPress has practically nothing in common with bbPress 1.x and previous versions, you can’t really argue that 2.0 will work on high traffic sites because previous versions could. Version 1 and 2 also has completely different authors.
That said, the information anointed just shared sounds very promising indeed. While following the development of bbPress 2.0 from the start, I can safely say that performance has been one of the biggest concerns throughout. The developers were honest, and I was prepared to trade off some performance in favor of cleaner, seamless integration with WordPress.
With anointed successfully hosting 300k posts and 40k users on bbPress 2, I’m beyond pleased. Knowing it will only get better from here, the future is looking mighty bright.
Try follow these steps. Also a moderator should probably close this thread as it’s a bit of a double post.
Just do it exactly as Justin Mason said. If you want to use bbPress 2.0, don’t install bbPress through BuddyPress.
When you’ve installed BuddyPress and started the wizard, don’t enable the bundled forum component. Instead proceed install the bbPress 2.0 plugin from the standard WP plugin installer. It should automatically recognize that BuddyPress has been installed and will tap into the activity feed.
Some of the more BP-specific features of the old forum, most notably the group integration, are not in bbPress 2 yet. I’m guessing as soon as we’ve reached feature parity between the two forums, the legacy forum component can be permanently deprecated and there would be a whole lot less confusion about this set-up.
Also, as far as import process goes, it’s definitely subject to change.
I think you misunderstand. Just search for ‘bbpress’ in plugins. You should find bbPress 2.0 there, the brand new bbPress plugin. It’s a straight forward install and should work straight out of the box with your default 2010/2011 theme, or with minimal tweaks in any other theme.
You really don’t want to do it this way. The whole point of bbPress is to have an easy way to integrate your forum software with your main WordPress install’s theme and userbase.
Thanks for confirming. I’d be happy to add it to the docs somewhere, but it doesn’t seem to be set up for contributions at the moment. Hopefully that’ll eventually come along with the other site improvements bound to happen when bbpress.org is updated to bbPress 2.
This is now possible:
http://testbp.org/2011/08/forum-shortcode-as-comments/
Though it’s still unclear to me whether or not this relies on BuddyPress 1.5, the environment in which this functionality is showcased. It would be a very odd dependency though, so I’m hoping this would also be possible with WP + BBP alone.
Could also tap into Jetpack’s way of embedding videos I suppose?
@Buslawekee, @tntc1978 and @Mike1233, please don’t make this into another bbPress 2.0 Updates thread. We’ve been given specific topics to which John wanted additional feedback. Anything not related to those clearly defined topics belong in their own threads, or a new ticket on Trac if it’s a valid bug report.
Separate as in users, or just not an inherent part of WordPress?
I highly recommend Vanilla:
That’ll give you a tight integration with WordPress, but through a “bridge”, so CMS and Forum remain two distinct systems.
Another argument for this plugin would be multisite friendliness. I think it would be anyhow.
Since the “integration” is simply a matter of the plugin copying the contents of a comment and re-posting it on a forum, it shouldn’t matter whether that’s in example.com/forums (default), forums.example.com (a secondary site) or example.com/secondarysite/forums, so long as that’s specified in the settings.
So if I have a main site for blogging, example.com, and a secondary site for forum discussion (i.e. with bbPress 2 installed on it), forums.example.com, this approach could still work just fine.
Am I correct in this assumption?
Thing about that is you wouldn`t be taking advantage of the lightweight nature of comments, which is ideal for simple reactions but not so much extended discussions. Actually I really like the term ‘reactions’, as that’s where I draw the line between a comment and a conversation. I’ve updated my mockup to reflect that. Here’s the updated image:
You’d also be confined to a single thread of discussion, which is the key limitation this plugin would resolve. Look at the linked TED page and you’ll see pretty much the exact setup I’m looking for.
Another reason to use comments is that if you’re using a P2-like theme you can enable near real-time comments on your article. This is only possible with WP comments, not posts.
Oh, and then there’s the many types of plugins that facilitate unregistered commenting. Besides anonymous comments, there are plugins to enable posting with a Facebook/Twitter/Google account without actually registering to the site, but just to avoid spam.
Finally, I actually think this “comment conversion” approach would be less of a hack than using bbPress in place of comments. It’s a one way conversion, from one standard data format to another. Removing the plugin only removes the conversion method; what’s left is perfectly standard data, ready for export etc.
In the end it comes down to what you need for your website. Check out “use bbPress in place of wordpress comments” if you want to continue discussing the setup you have in mind.
(much delayed) Update:
After some talk with Patrick Daly at DevPress I realized it’d probably be for the best that only moderators get to “promote” comment trees to forum threads. Having a choice between the two might confuse the average user.
