[@boonebgorges Keymaster 15 years ago]

Make sure the pages being pointed to are actually published. (Seems silly I know, but worth checking.)

[@boonebgorges Keymaster 15 years ago]

Not much we can do for additional plugins, but we should probably have better support for ``. Could you open a bug ticket at http://trac.buddypress.org with steps to reproduce, please?

[@boonebgorges Keymaster 15 years ago]

Still can’t reproduce it. I believe you that it happens, but it’s not happening on my install, no matter what image I use. Can you give more specific details about what you’re filling in for image metadata?

[@boonebgorges Keymaster 15 years ago]

I’m unable to reproduce the caption issue. Publishing and republishing posts with captions does not show anything unusual in the activity stream. In fact, I’m a bit confused why you would ever be seeing the caption shortcode, since that should be fully processed into HTML by the time it hits the activity stream.

The only thing I can think of is that you’ve somehow removed the opening shortcode for so that WP is no longer rendering it properly.

> Would there be a way to stop the bump on new posts?

The easiest thing to do would be to remove the bp_blogs_record_post hook from the save_post action, and provide your own version of it instead, using $post->post_date_gmt for recorded_time instead of $post->post_modified_gmt

[@boonebgorges Keymaster 15 years ago]

> Any luck replicating it yourself?

Gee whiz, give me a little time

[@boonebgorges Keymaster 15 years ago]

> rant/opinion

Yeah. You could have just asked “Why can’t I delete the ‘name’ field?” and been done with it. There is an argument for why the field is required, which has to do with the fact that BP uses display names all over the site to identify users, but the ad hominem nature of your rant/opinion makes it less pleasant to offer up the explanation.

> Why release 1.5 and not make it compatible with bb 2.0?

The 1.5 release had been held up for too long already. bbPress 2.0 integration is not trivial.

> And again, when setting up the forums why the whole endless loop of “install bbpress but it’s already installed” it’s rather confusing.

Not sure I understand the question. Once you have set up bbPress, you don’t have to install it again. You have an option to reinstall it, but only if something has gone wrong.

> Why does it keep asking for a valid “activation key” even if people click on the validation key received by the system?

This usually means that the user has already activated his account. Use a plugin like https://wordpress.org/extend/plugins/unconfirmed/ to do some more research.

[@boonebgorges Keymaster 15 years ago]

Probably at least some custom SQL is needed. Something along the lines of:
(1) doing an additional query to get a list of the user’s groups and the forum_ids for those groups
(2) limiting the main forum topic query WHERE ( forum_id IN ( {$user_forums} ) OR group_status = ‘public’ ) (not sure if group_status is available here, I would have to look)

> is it still that hard to implement the bugfix
It’s not very difficult technically, but it will introduce at least one or two more queries on what can already be a database-intensive page load. If you can provide a workable patch, I’m sure it would be happily considered.

[@boonebgorges Keymaster 15 years ago]

Don’t use `do_action()`. Use `add_action()`

[@boonebgorges Keymaster 15 years ago]

Re (2): The “bump” is by design. See https://buddypress.trac.wordpress.org/ticket/2546 Can’t reproduce the ‘caption’ issue.

New blog posts and comments are working fine for me.

[@boonebgorges Keymaster 15 years ago]

Also, can you be more specific about “does not work”? You get a 404?

[@boonebgorges Keymaster 15 years ago]

Hm. Working fine for me on my local installation. Have you tried `?page_id=` ? Both should work.

[@boonebgorges Keymaster 15 years ago]

Setting up a true development environment may take some time up front, but it saves enormous amounts of time in the long run. The simple fact that you can work locally instead of remotely is in itself an enormous time-saver. Add on top of that the fact that you will be avoiding unexpected site crashes, because everything will be tested ahead of time, and it’s a far more sane way to work

[@boonebgorges Keymaster 15 years ago]

https://core.trac.wordpress.org/ticket/18971 (with a patch)

[@boonebgorges Keymaster 15 years ago]

Awesome. Thanks for taking the initiative, @foxly.

[@boonebgorges Keymaster 15 years ago]

Good thinking

[@boonebgorges Keymaster 15 years ago]

Hm. Network activation doesn’t work for me at all with WP 3.3 trunk, with any plugin (not just BP). That doesn’t seem good.

[@boonebgorges Keymaster 15 years ago]

Very strange.

Your scenario (1) is working fine for me, at least with bp-default.

Not sure I understand what the pagination in (3) is supposed to do. What would show on page two of an *individual* group? The second page of activity? I’m pretty sure that the /page/x rewrite has never done this for groups.

[@boonebgorges Keymaster 15 years ago]

> What are the differences and similarities as to how the buddybar and the WP adminbar are configured? What will be lost and what will be gained and how configurable will it be?

The BuddyBar will still be there, though it will be turned off by default in favor of the WP Admin Bar. (In BP 1.5, that’s reversed – you can enable the WP admin bar manually with
`define( ‘BP_USE_WP_ADMIN_BAR’, true );`
in wp-config.php.)

BP’s WP Admin Bar implementation has:
– a logged-in user dropdown menu (links to logged-in user’s groups, activity, etc
– admin links for current group
– admin links for currently displayed user
– Notifications

There is ‘Visit Random’ button in the current implementation, though it’s worth an enhancement request on http://trac.buddypress.org

In any case, it will be completely customizable. The BuddyBar is mostly hardcoded HTML. The WP Admin Bar is built using an easy-to-use API, making it far easier to customize to your liking. If you don’t like the search, it’s easy to remove. If you don’t like the appearance, it’s easy to modify with CSS.

> Does anyone know yet if BP 1.5 will run on WP 3.3?

It’s mostly fine. The WP Admin Bar, which changes a lot between 3.2 and 3.3, does not work all that well.

> Is there any way to create one nice big CSS for the whole BuddyPress shebang, so it won’t be so difficult to figure out the where, how, and why of formatting?

Most of bp-default’s CSS is in bp-themes/bp-default/_inc/css/default.css.

[@boonebgorges Keymaster 15 years ago]

This is expected behavior. The logic that would be required to show private forums to logged-in members of those groups is complex, and has not yet been implemented. There is a ticket in Trac to discuss this enhancement: https://buddypress.trac.wordpress.org/ticket/2576

[@boonebgorges Keymaster 15 years ago]

Awesome, so glad it’s working!

[@boonebgorges Keymaster 15 years ago]

I’m guessing that jQuery or jCrop is being loaded twice on your page, and only Chrome is being smart enough to clear up conflicts. I know you’re not a programmer, but at least you might consider viewing the source of your page (right click and View Source or View Page Source) and then search the page to see how many times you find `jquery.js`. If you see it more than once, then that’s probably your problem, and you’ll have to comb through your theme files to figure out the issue.

[@boonebgorges Keymaster 15 years ago]

the almost full lack of support around b-press is not exactely the best thing about this otherwise brilliant plugin

The people who build the software and man these support forums are strictly volunteers. Please be patient.

It’s hard to tell the problem without seeing your site, but it’s likely that it’s a problem with your theme. Either that, or one of your themes is deregistering jQuery. Have you tried with bp-default to see if the problem persists? Or tried deactivating some other plugins to find a conflict? At least that would narrow down the issue.

[@boonebgorges Keymaster 15 years ago]

Glad to hear it’s working

[@boonebgorges Keymaster 15 years ago]

bp-default should not be in wp-content/themes. It is loaded directly from wp-content/plugins/buddypress/bp-themes.

It sounds like BuddyPress is not fully loading. Check a few things:
– Make sure it’s activated
– Make sure it’s not waiting for you to walk through an upgrade wizard. Try clicking on the BuddyPress menu item on the Dashboard or on Dashboard > Network Admin (multisite)

[@boonebgorges Keymaster 15 years ago]

Um, did you deactivate BuddyPress itself? Sounds like it’s not being loaded correctly.