Forum Replies Created
-
It looks like you are trying to use this plugin – https://buddypress.org/community/groups/buddypress-activity-tags/ – because `Bp_Activity_Tags_Widget` is not in BuddyPress itself.
Try deactivating the plugin or, if you’re unable to log in to the admin, remove `bp-activity-tags` folder from the `wp-content/plugins` directory.
And maybe remove the short-code or widget corresponding to this plugin from your theme as well.
Where you allow people to post comments around your site is entirely up to you and depends on how you implement BuddyPress.
Head over to http://testbp.org/ and join/login to see an example of a default BuddyPress install or check out some of the sites here – https://buddypress.org/showcase/
The next thing I’d do is deactivate BuddyPress to see if you’re still not getting new user notifications. If you can’t do this on your live site maybe create a test install in a subdirectory. This would help isolate whether it’s a BP or WP thing. You might want to check out the WordPress forums, too – https://wordpress.org/search/new+user+notification?forums=1
Did you ever get these new user notifications? Or is it something that just started happening recently? Maybe it’s a plugin or customization issue specific to your setup.
I’d double-check that the admin email is correct at yourdomain.com/wp-admin/options-general.php
Then, make sure that the emails aren’t being zapped by your SPAM filter.
Do you get regular BuddyPress notifications (friend requests, private messages, etc.) to the admin email?
Is your email hosted on the same server as your site? You might try switching the admin email to gmail or whatever to see if the emails go to that other account. Because if your email account is the same as your website domain but you host your email elsewhere (ex. Rackspace, Google Apps), your server might be trying to send the message locally.
`bp_is_active()` checks if a BP $component is active – not whether members are registered but not activated. The `bp_account_was_activated` function is used in the activate.php template but isn’t appropriate here I don’t think.
In addition to the BuddyPress Conditional Tags – https://codex.buddypress.org/developer-docs/conditional-template-tags/ – you might also look at WordPress Conditional Tags – https://codex.wordpress.org/Conditional_Tags – to see if there are any that will work for you.
P.S. I just saw your other post.
`
This occurs due to my BuddyPress Auto Group Join plugin. How can I hide the not-yet-activated members from appearing on the Group Members page?
`It seems like it would be better to modify the plugin(s) causing the issue instead of modifying the BP code. Maybe the plugin developers can assist.
You could create the illusion through customizing your navigation and theme.
Or maybe give this method a try – https://codex.buddypress.org/getting-started/install-buddypress-on-a-secondary-blog/
And here’s a link to the original thread which is worth reading through.
https://buddypress.org/community/groups/creating-extending/forum/topic/securing-components-from-non-logged-in-users/I haven’t tested this with the latest version of WP/BP but I’ve used a similar method up to WP 2.9.1 and BP 1.2 without issue.
Here’s a couple links about improving BuddyPress and WordPress performance.
https://codex.buddypress.org/buddypress-site-administration/improving-performance/
http://www.prelovac.com/vladimir/wordpress-optimization-guideI would test some of the tips in those docs before setting up multiple databases.
But see also:
http://wpmututorials.com/plugins/shardb/
https://wordpress.org/extend/plugins/shardb/To hide the forum tag cloud from users, you could add the following to your stylesheet:
`
#forum-directory-tags { display: none; }
`One other note.
`
“I copied the bp-default containing the members directory and its files.”`
You should not copy over the entire bp-default directory and its contents. Only copy over the individual file (and possibly directory) that you are trying to override.
If you copy over the entire bp-default directory into your child theme, your child theme would essentially be a standalone theme and you won’t benefit from using the bp-default theme when you upgrade. The parent theme would be ignored. Copying over only the specific files you are changing will also help you to see exactly what you’ve changed when it comes time to upgrade.
This link should help you get your child theme ready to go – https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/
It sounds like the child theme you created might not be activated yet. Once you activate the theme you should see the changes straight away when you modify the child theme.
On a related note, I’d highly recommend using the stylesheet of your custom child theme wherever possible to manipulate the presentation of your content. If you wanted to change the style of the members directory, start your selector with body.directory.members like this:
`
body.directory.members a { color: #000; }
`In the example above, I’ve just chained together the two body classes (directory and members) that are used in the default BP theme when viewing the members directory.
Source: Class selectors
No courseware. The site was launched March 2009 on WordPress MU/BuddyPress. Slight modifications based on snippets/plugins posted by Burt Adsit, Paul G., Boone G., JJJ and Andy.
The content is mostly pre-recorded video and audio – not a formal educational program with assignments etc. So the setup is pretty straightforward and most of the customization is just theming. Main site has different content for logged out and logged in users. “Classrooms” are private sub-domain blogs (soon-to-be sub-domain sites) with a classroom theme. The main site and classroom sites are both using custom child themes powered by the BuddyPress default theme.
I’m in the process of upgrading the site so I’ll be around here more often if you have questions.
Works for me using WP 3.0 on a local install.
Updated to BP 1.2.5 automatically, clicked the activate button after upgrade, and it was activated across the network.
You might try adding the following to your stylesheet first:
ul#nav li a[title="Groups"], ul#nav li a[title="Blogs"], ul#nav li a[title="Forums"] {display: none; }Reference: Taming Advanced CSS Selectors and Attribute selectors at w3.org
Try replacing “template_url” with “stylesheet_directory”.
bloginfo(‘stylesheet_directory’); should call your child theme address dynamically.
Try adding this to your stylesheet.
#container { width: 630px; float: left; }There’s no width declared for the container in your stylesheet so it’s taking the full width of the page.
The BuddyPress Default theme is not meant to be used for user blogs.
You can disable it sitewide from the dashboard – Site Admin > Themes
Did you test BuddyPress before with just the default theme and no plugins? Did you have it working with the default (bp-default) theme before you switched to your theme?
Either way, the first thing I would do now is disable all plugins except BuddyPress.
Next, I would switch the theme to back to the default (bp-default) within Appearance > Themes in your dashboard.
Once you disable all plugins (except BuddyPress) and switch to the bp-default theme, you should confirm that the theme is working similarly to testbp.org.
Assuming that everything is working and you are not seeing any error messages, switch the theme back to your custom theme before you re-activate any of the other plugins. Check to see if you are still seeing an error message.
If you are, double-check steps 1,2,3 at https://codex.buddypress.org/how-to-guides/wordpress-to-buddypress-theme/. (1) Make sure you’ve put the theme extension pack in your custom theme. (2) Make sure you’ve added the following line to the top of the functions.php file for your custom theme:
include( TEMPLATEPATH . '/bp/bp-functions.php' );(3) And make sure you’ve added the “Tags” line to your custom theme’s CSS header.
Do you still see the error message? If so, try replacing the code you added to the top of your theme’s functions.php with the code as Andy suggested:
include( STYLESHEETPATH . '/bp/bp-functions.php' );Check for the error message again.
Once you have BuddyPress functioning using your custom theme without any error messages, then you can try activating plugins one-by-one to ensure you can identify any conflicts.
P.S. You mentioned in #10 above that you had modified the core files by adding the functions line of code to the functions.php file. Just to make sure, the core files are in wp-content/plugins/buddypress/. You should not be modifying any files or folders within the core files. All of the customizations you need to make to adapt your custom theme should be within /wp-content/themes/your-theme/ which I believe for you is /wp-content/themes/wp-clear-basic/. So you are adding the theme extension pack within your theme’s folder at /wp-content/themes/wp-clear-basic/. And you are modifying functions.php and style.css within your custom theme’s folder only.
Double-check your theme’s functions file at /wp-content/themes/wp-clear-basic/functions.php to make sure you added
include( TEMPLATEPATH . '/bp/bp-functions.php' );right at the top after the opening php tag.If it’s there, try disabling other plugins one-by-one to see if they might be interfering. The Coming Soon plugin in particular.
And if disabling plugins doesn’t work, try providing some more information because it will make it easier for others to help. https://buddypress.org/forums/topic/when-asking-for-support
Delete the default theme from your themes directory and then rename the folder with your theme to ‘default’.
If you want to make your sub-blogs look exactly like your primary blog *and* you are using BuddyPress 1.2 Beta, then you’ll want to check out the how-to called “Building a BuddyPress Child Theme.
Make sure you are entereing the full address (http://example.com/) rather than just example.com.
If available, a link to the actual profile page would be helpful to diagnose.
bp_is_my_profile()should work if you are only trying to show a widget on a user’s own profile.Erich73, The notifications tab alerts users to more than the latest private messages. But it’s up to you whether you want to remove it or not.
FYI – I just checked the Inbox Widget plugin into the repository –
https://wordpress.org/extend/plugins/inbox-widget/
Screenshot –
https://wordpress.org/extend/plugins/inbox-widget/screenshots/
This is not a stable version and it will only work on sites running the latest trunk version of BP (2243+) with the bp-default theme enabled. It’s just something to build on and I’m hoping to add improvements soon.
