Forum Replies Created
-
It will do_(any)_action you tell it to do
`function cc_awesome_activity_meta_shortcodes() {
echo do_shortcode(‘SexyButton’);
}add_action(‘bp_activity_entry_meta’, ‘cc_awesome_activity_meta_shortcodes’);
`Or, activity/entry.php
`function cc_admin_bar_links() {
global $wp_admin_bar;
//BE GONE DEMON!
$wp_admin_bar->remove_menu(‘bp-register’);//AbraCaDabra! Once i wave my wand, you will become an Elephant!
$wp_admin_bar->add_menu( array(
‘id’ => ‘bp-login’,
‘title’ => __( ‘Log in and register’, ‘buddypress’ ),
‘href’ => wp_login_url()
) );
}
//Wave Wand.
add_action( ‘wp_before_admin_bar_render’, ‘cc_admin_bar_links’ );`SORRY! Don’t mind my lame humor within comments. Just remove them
If this doesn’t work, you will need to contact wpmudev as they are probably doing something really weird
“there is a plugin out there that tells you what template is being parsed”
I’m assuming your talking about ‘Reveal templates’ or is their another one?“but it does not seem to work on buddypress.”
Yeah, BuddyPress does templating really weirdly. BuddyPress never talks to WordPress’ template loading functions which is why most of thoes types of plugins don’t work. The plugin should work after ‘theme compatibility’ comes, https://buddypress.org/2012/04/the-default-theme/@helpme2012 Are you referring to the blog comments or the Activity stream Comments?
For Blog comments, just recreate the bp_dtheme_comment_form() function (located inside bp-defaults functions.php) inside your child theme and it should override the default.
If your talking about the Stream Comments, then – i have no idea. Never had a problem with the comments post form appearing to logged out members
“If they match BP 1.5.6 with WP 3.4, that means we’ll have to wait at least 3 months for it. And 6-9 months for 1.6”
Not necessarily. 3.4 is in beta which means it’s just clean up time and could be released at any moment (whenever their confident all the bugs are squashed). Both BuddyPress 1.6 and BBpress 2.1 is still in active development – think, first come (first in beta), first serve (first to come out)
Their’s afew changes and depreciated code in 3.4 so they can’t wait too long for a 3.4 compatibility release.
Plus, it’s not like they HAVE to wait months after a release for another one… i’d rather have deprecated notices squashed and then have a major release two days later than have to put up with annoying “you have old code on your site” notices everywhere for two days
lol
