I’m having the same problem as Anointed. Plugin is activated, but the panel that should be in the Buddypress area of the dashboard doesn’t appear. I’m running WPMU 2.9.2 and BP 1.2.3. Not sure what’s changed. It used to be there.
You need to create a page first, before you are able to do this.
Go to pages.
Create New.
Give it a name.
Then you can go into Settings, reading and you will be able to select the activity stream as your main (static) page, and that new page you created as the Blog post page.
You an download a LAMP stack that will install Apache, MySQL and PHP quite easily (Linux is the L of that acronmym). Bitnami.org offers this. I’m sure there are probably others.
@m In reply to your statement above: “Plus I don’t see any reason not to give the user total control over their profile since it’s their info (thus no need for a setting to “Let user decide” )” I thought I might be able to provide a good reason…
As an elementary teacher using BP in the classroom, privacy is incredibly important, and a trigger that allows me to force the privacy of my users should not be discounted.
Teaching kids how to navigate and manage their digital footprint is easier if admins can ensure that mistakes the users make can be contained in the privacy of the “digital classroom”
Plugin looks interesting, but would love the added security of knowing that my kids’ profiles are private.
I’ve got this in the #header too. Can’t remember now if you need that as well. Sorry. I’m suddenly second guessing myself. One of the two options will do it for you. For me, both of these padding settings are the last lines in the CSS text identifying the font, line, width etc.
Are you looking for a field that would take a month day year input and spit out a number? If not, why not just add an Age field in the Profile Field Setup area under Buddypress on you Admin Dashboard page. Make it a required field so users have to fill it out.
I’m using transmit on a mac, and I can right click on the .jpg to see the properties and copy the path. Not really sure about this, I’m knee deep in creating my first child theme myself, but it’s worth a shot.
<b>Warning</b>: require_once(/usr/home/litcirc/public_html/bb-config.php) [function.require-once]: failed to open stream: No such file or directory in <b>/usr/home/litcirc/public_html/wp-content/plugins/buddypress-rate-forum-posts/rate.php</b> on line <b>5</b>
Line 5 in rate.php is “require_once ABSPATH . ‘bb-config.php’;”
I’m out of my element here. Is the plugin looking for bb-config.php and cannot find it? according to the dashboard bbpress is configured correctly.
Are you trying to keep Group A from reading the Posts from Group B? If not, what about just using the P2 theme http://p2theme.wordpress.com/ on a Group Blog using this plugin https://wordpress.org/extend/plugins/bp-groupblog/ and then instruct users to categorize or tag appropriately. P2 makes it easy for the community to post without having to go into the dashboard.
Well isn’t that inconvenient. Something in the forum has obliterated the ampersand, number sign, and the number 039; that made the I’m a reader Profile Group Name problem a problem. Making my post look a bit confused; eliminating the / that is causing all the trouble in the first place.
Ok. Now I’ve really screwed things up. I thought I could take the advice of Meerblickzimmer and go in to the Plugins folder and rename the buddypress folder (even though it was deactivated already, I thought I could install fresh again and see if that helped.
Now I get this error on an otherwise white screen sitewide:
Fatal error: Class ‘BP_Groups_Group’ not found in /home/litcirc/public_html/wp-content/plugins/bp-group-calendar/bp-group-calendar.php on line 129
Even thought that calendar plugin wasn’t active in the first place. I tried to backtrack by renaming the buddypress folder back to what it was, but the damage is done somehow.
Same error as gsmith above. Very new WPMU / Buddypress install, so BP was the only active plugin. Deactivated it. Upgraded Automatically. Got the error.
Then when in an manually updated, overwriting the still deactivated plugin with 1.1.3. Same error again.
Can someone break down this sledgehammer method in a bit more detail?
Viewing 23 replies - 226 through 248 (of 248 total)
