Forum Replies Created
-
Exactly the same problem for me.
New install / site, WPMU, BP1.2
Main blog is missing from My Blogs on site admin bar, and from Blog Directory listing (although the listing count shows 1).
Like @david, I’m sure mine was working then ‘just disappeared’.
Did this get entered as a bug?
Just a quick thought (I don’t know the answer):
Is it an order of ‘inclusion’ issue with the functions.php files?
i.e. does the parent (bp-default) functions.php get included after the child theme functions.php? So, the remove_action is occurring before the add_action?
@bpinspire – Hi, no I haven’t tried upgrading that theme to 1.2, so not sure whether the activities loop is now working. We are building a new site at the moment, but that will aggregate its forum content from an RSS feed from ‘external’ forums implemented using SimplePress
Further update:
I’ve tried adding the remove_action line to my functions.php in the child theme, but it makes no difference… the custom header / inline CSS is still being inserted.
Any suggestions?
Update: I’ve just seen the comment in the functions.php, advising how to remove the custom header:
/****
* Custom header image support. You can remove this entirely in a child theme by adding this line
* to your functions.php: remove_action( ‘init’, ‘bp_dtheme_add_custom_header_support’ );
*/
Thanks!
@Andy – I’m having the same issues as @Mike and @designodyssey:
I want to use bp-default as the parent, but don’t want the custom header, and other inline css settings.
Unfortunately, functions.php in bp-default is adding inline css, which is therefore difficult / cumbersome to override in the child theme.
As a quick fix, I suspect I’ll remove functions.php from bp-default theme, and just copy over the functions I want into a functions.php in my child theme. Obviously this is not ideal.
Is there a better way to solve this? Perhaps a hook to remove the offending functions?
Note: As of BuddyPress 1.2, this is less of an issue, as the default theme (similarly to most WordPress themes) only comes with a single sidebar
Guten Tag Thomas,
Thanks for the really thorough description of the project, and great to see you (alongside our Hello Eco Living site) in WPMU.org’s list:
10 of the Latest and Greatest Inspirational BuddyPress sites
@Xevo: your hint on login is handy to know!
Cheers,
Roger
@sven. I had this problem in the past, because my mods in bp-custom.php were being overwritten when bp loaded itself.
The details on how to get them to occur after bp has loaded, are in this thread:
https://buddypress.org/forums/topic/remove-menu-from-admin-bar#post-22856
or, as John points out above, they can go in functions.php which is called afterwards.
Thanks for the feedback guys.
I adopted David’s function and it worked.
Hi Paul,
yes… we are on 1.1.3
Andy’s post was 3 months ago, so I assume the code loop / bp_has_activities call was for a 1.1.x version, rather than the forthcoming 1.2.
Any other thoughts?
Cheers, Roger
Andy,
I’ve tried using the code loop you’ve given above on my front page, but it doesn’t filter to just show the forum activity.
It’s showing all the site activity, i.e. the action filter doesn’t seem to be having any effect.
Any thoughts?
Any progress on this?
I want to display latest forum topics on the front page of my site.
I tried including the forums-loop.php file (used to display the topics on the forum directory page), but it doesn’t work on the home page…
… the group field is not populated, and the link to the topic does not work.
Any thoughts?
Note: unregister_sidebars() doesn’t appear to work.
Therefore, is there anyway to remove the sidebars registered in bp-sn-parent, without hacking the functions.php file in bp-sn-parent?
I’m also getting the white page… is my child functions.php read in addition to the parent functions.php (rather than simply replacing it), hence causing duplicate functions?
You could look in file bp-core-templatetags.php, but I’m not sure there is anything direct.
Have you looked at the profile-loop.php file (in member-theme/profile in 1.0.x installations)? You could put OTHER member conditional code in there, using !bp_is_home().
You can make use of bp_current_user_id(), and the parameterised versions of functions such as bp_has_blogs() to obtain other member details.
Hello Eco Living is a brand new site focused on Eco / Green / Sustainable living.
With a magazine, social network, and blog platform (all WP / BuddyPress powered of course).
The site officially launches this month, initially with a UK focus.
We developed the site with a lot of love; there are finishing touches on the graphics (best viewed on a Mac at the moment) that we are really proud of.
The client has the site out in Beta at the moment… please let us have your thoughts.
Roger
Ok, dug a little further, the remove_action needed to be called after the bp plugins had loaded.
So, the solution is:
function modify_adminbar(){
remove_action( ‘bp_adminbar_menus’, ‘bp_adminbar_random_menu’, 100 );
}
add_action(‘plugins_loaded’,’modify_adminbar’,99);
A simple fix for you, might be from site admin… options:
Set ‘allow new registrations’ to ‘only user accounts can be created’.
That should remove all the blog stuff.
Getting out of a fix:
If you’ve tried updating Buddypress, but forgotten to update WordPressMU first of all… you are now facing the “Fatal error: Class ‘WP_Widget’ not found”.
You’ll also find, you can’t rewind your buddypress upgrade, and can’t update wordpress from the dashboard. You are stuck!
You could reach for your backup, but if like me, you got lazy and didn’t backup… you’ll be really pleased to know this link to a manual update process works, and you won’t lose any of your lovely data:
https://codex.wordpress.org/Upgrading_WPMU#2.7.1_to_2.8.3
The steps for 2.8.3 also work for 2.8.4a
@Korhan… thanks, much appreciated
@jeff: I’m building the site for a client (that’s already gone out in Beta), so need to work with a fixed release (1.0.3 in this case) rather than continually updating from the trunk.
Is there a ‘roadmap’ anywhere that outlines the key features the developers are working towards for 1.1?
@R-A-Y: thanks. Yes, I could see how to do it with a hack, but didn’t want to have to mess with the core code.
@mariusooms: thanks, we’ll probably hold off until 1.1. Incidentally, where do you get the information on 1.1 from? I’ve had a quick look, but couldn’t find anything.
@gerikg: yes, mariusooms is right about those options, there’s nothing that simply turns blogs off at registration, but allows you to create them later.
The 4th option (Only logged in users can create new blogs) implies it might be the solution. But, with that enabled, users can’t even complete a new account registration.. . has anyone else encountered that problem?
@r-a-y: thanks for the pointer… have left Mark a comment, will see if he’s willing to ‘spill the beans’ on this one.
And giving the second part a bump: Anyone spot a hook that allows the registration form to be modified, without hacking the core code?
