BuddyPress.org

Did you try all the options in this thread: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/email-notification-not-working/?topic_page=2&num=15 ?

Actually I disagree. I would suggest looking at Kaltura for video, and I think there is another media plugin that handles video and images although I haven’t experimented with either, I think that BP-albums is being updated to handle other types of media. If you can wait there is a very interesting plugin being developed as a Google Summer of Code project that will turn a WordPress / Buddypress install into an LMS, it has some interesting features and looks to be very extendable. I expect it will be like Buddypress itself and spawn a series of additional plugins that enhance its features. Have a look at it at:
http://sushkov.wordpress.com/

Existing LMS systems do have a lot of pluses, but many are either difficult to customize and quite rigid (Moodle comes to mind) or very difficult to install and configure (Sakai project for example). That said, it may be easier to get a quick system up and running and your intended audience should reflect your choice of system as well. I find that most systems are aimed at older students (high school or university and beyond) and so do not fit what I hope to do with a learning system.

Hope this helps a little. All the best.

@marianbuchanan

Try this:
Dashboard – Buddypress – General Settings
Hide admin bar for logged out users?: YES

@en0ch, Where is the setting for hiding the admin bar from visitors who are not logged in?

In the meantime, the Visit portion of it can be hidden from display (although not from the source code) by adding
#bp-adminbar-visitrandom-menu { display: none; }
to the stylesheet.

And you can give users the option of hiding as much as they want through the BuddyPress Profile Privacy plugin.

It seems to me, though, that hiding the username itself from Everyone kind of defeats the purpose of being part of an interactive community. I suspect it would only work if it was a site set up for people to connect through off-site invitations to interact on-site as Friends or Group members.

just some thoughts

Marian

The BuddyPress Profile Privacy plugin allows users to set the privacy level of each profile item.

Marian

@wandilly, Did you get your problem resolved yet? If not, I’d be glad to help do detective work on it. I’d need a login though, so if you feel comfortable giving me access, you’d want to share that by private email. You can contact me at marian@heartwoodwebdesign.com.

Marian

@billy1111a, Didn’t receive anything from you yet. Just wanted to let you know my offer still stands.

Marian

@vdfbelial Strange behavior indeed. What browser are you using? What theme? btw, your link to site leads to dead end.

Try this which should work:

/*
Theme Name: TSS
Theme URI: http://www.thescratchingshed.com/themes/tss/
Description: TSS custom
Version: 1.0
Author: TSS
Author URI: http://www.thescratchingshed.com/
Template: bp-default
Tags: buddypress, two-column, blue, white
*/

/* Inherit the default theme styles */

@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );

/* Inherit the default theme adminbar styles */

@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/adminbar.css );

/* Begin custom styles

---

*/
/* change primary sidebar width to 300px */
div#content .padder {margin-right:300px;}
div#sidebar {width:300px;margin-left:-301px;}

That doesn’t sound correct, if you follow the instructions given on the child theme codex page then you will have a stylesheet that references the original default.css you do not want to create a duplicate of it, you make your changes in the new child theme stylesheet, that’s the one that calls default.css with a line that should look like this:

@import url( ../../plugins/buddypress/bp-themes/bp-default/_inc/css/default.css );

Is that ‘Line 4’ custom? I don’t see it in a functions file for a 1.2.5.2 I’ve just test upgraded.

Generally – and it’s not advise necessarily to follow – I have never had an issue with upgrading the WP portion of a site and don’t tend to bother deactivating any plugins; I do though take a backup, ALLWAYS, on production sites prior to proceeding.

If you are making changes to styling you do NOT have to reinstall BP from scratch, it’s simply not necessary.

You should be making changes to a child theme; are you using a child theme? If not follow these instructions here:
https://codex.buddypress.org/how-to-guides/building-a-buddypress-child-theme/

If you are making the changes I described earlier then you enter them in the newly created stylesheet file and they act as an override to the default styles that are pulled in to this stylesheet file.

If you follow this procedure you change nothing about the default styling that can’t be reversed by either simply deleting your new ruleset styles from the child stylesheet file or wrapping them in comments to kill them:
/* #content {these styles cease to be read} */

Give things another go but this time if it doesn’t work don’t reverse things leave it up live if you can and I’ll look and see where you have gone wrong.

If you didn’t disable BuddyPress (and all other plugins) before upgrading WordPress, this might be a weird artifact, though it should usually clear after a page refresh. So… have you disabled the Groups component?

I have the same question as @intimez mentioned above. Is it possible with OQP to submit post to frontpage and before it appears, admin can review the post first?

Thanks.

When you refer to a child theme it refers to the ability to create a new blank folder within the ‘theme’ folder this would be considered a ‘Child theme’ if it simply had a stylesheet residing in it’s root /top level that stated it was using the files from a particular parent theme, what then happens is having selected this theme – which now would appear in your dashboard themes page, – WP examines the stylesheet information at the top of the file and finds that it instructs WP to look for files in a particular theme as being the main theme files to use; however the clever trick is that WP first knows that it must look in your child theme for necessary files FIRST! and if they are not found THEN look for the necessary file in the stated parent theme, thus you do not have to have any files in your child theme as WP will use the parent files, but you can add new CSS rulesets to the stylesheet living in the child theme and these will be read and acted on (that stylesheet references the parent CSS stylesheet files through the @import rule first and then reads on for any additional rules you have added below the @import calls)

If you do not want to make any changes to BP-Default theme then you simply activate that theme as seen in the theme page in the dashboard. When members create a blog then those blogs should use the twentyten theme or whatever other themes you choose to download and make available (Note that you decide what themes are available to members via the ‘Super Admin >Themes’ page only the themes that you select ‘yes’ to are available to member blogs so to avoid them attempting to use the BP-Default on user blogs you ensure BP themes are not selected)

If you decide that you do need to make changes to BP-Default theme then you would create a folder under ‘Themes’ name it ? ‘my-bp-default’
to the folder you add the requisite stylesheet and now you can move files as required from bp-Default original folder to your new folder and edit them as you wish, or simply create new rulesets to style elements which you place in the new stylesheet file. BP/WP now looks at your new child theme for any files that it must use in preference to the same versions that might reside in the original theme folder.

Apologies if the above covers ground you already understand.