BuddyPress.org

“I wanted a messageboard potentially with subjects divided into specific groups”

Sounds like you need a traditional forum script, perhaps with a bit of customization. Why do you use Buddypress?

I am getting all of these errors. Any idea what’s wrong?

PHP Warning: Cannot modify header information – headers already sent in wp-content/plugins/forum-attachments-for-buddypress/image.php on line 69

WordPress database error Table ‘xxxxx.bb-attachments’ doesn’t exist for query SELECT * FROM `bb-attachments` made by require_once, require, do_action, call_user_func_array, bp_forum_attachments_check_installed

“… just because buddypress or wordpress or whoever develop new features for an application doesn’t mean you are forced to use the new features. You don’t have to install the forums …”

The topic of this thread was about removing groups from forum. Groups imho are a natural part of a social networking architecture. Forums not so much. Most of the questions on this board these days are about forums/bbpress. That seems also where most of the developers attention is going, while there is almost no progress on what should be the core of a social network script for WordPress; member management, privacy/security, making BP WordPress 3.0-ready, etc.

Talk about “dropping rigidity and opening up to an amazing new flexibility and power” is pure nonsense. I’m not a programmer myself, but have you looked under the hood? Have you looked into the database? Do you know how BP is structured? Software can’t be all things to all people. It will never make you ice cream sundaes. Sure it’s nice to have built-in features, but there is always a trade-off. In Buddypress’ case it is growing structural confusion. Where would you draw the line?

I’d prefer a leaner core, a script that only adds social networking to WordPress and does it well. Integration with bbpress should go via WordPress, not as bolt-on to BP. Ideally WordPress would have an API that would make the members database just as easy to integrate with PunBB or phpBB if I wanted to.

Just want to thank everyone for their hard work getting 1.2.5 out.

https://trac.buddypress.org/ticket/2479

I do however see these bits of goodness in the trunk which is indicative of my current structure and leads me to believe that the fault is as @rebootnow called it. It’s still asking for get_current_site() when displaying avatars on a secondary blog with multisite enabled.

+ if ( bp_core_is_multisite() )
+ $path = ABSPATH . get_blog_option( BP_ROOT_BLOG, 'upload_path' );
+ else {
+ if ( !$path = get_option( 'upload_path' ) )
+ $path = WP_CONTENT_DIR . '/uploads';
+ else
+ $path = ABSPATH . $path;
+ }


and


if ( bp_core_is_multisite() && BP_ROOT_BLOG != $current_blog->blog_id )
- $upload_dir = str_replace( $current_blog->blog_id, BP_ROOT_BLOG, BLOGUPLOADDIR );
-
- return apply_filters( 'bp_core_avatar_upload_path', $upload_dir );


thanks @johnjamesjacoby for the follow up and @rebootnow for the additional insight on this. I believe that tickets #2451 and #2469 are related because with multiblog enabled it’s still kicking an avatar path and upload relative to the wp_upload_dir(). I tested the 1.2 branch but I just svn sw’ed up to 1.2.5 and I see the that the trunk merge didn’t quite make it regarding avatar_upload_path(). There are no differences between the bp-core-avatar.php in the 1.2.5 tag and 1.2 branch? This one is outsmarting me thus far, I’m afraid to filter the core_avatar_upload_path with custom functions for future compatibility and the filters don’t exactly account for the structure of the avatar uploads if the upload path for the site settings is modified – as in something like such http://gzet.net/wp-content/uploads/avatars/ ~ when the rest of the sites adhere to the /blogs.dir/#/ protocol.

I would also like to have an age verification on my BuddyPress site. I have added a “birthday” field as a requirement in the user profile, but this does not prevent minors from completing the registration process. How would I go about implementing something like this?

edit

That guide is pretty much what I have used, haven’t really had to consult a guide though in quite a while for this sort of thing. The point of jQuery and cross browser issues is that the library silently resolves them thus using :nth-child as a straight CSS3 pseudo class will not work for IE but using it within the selector group in a jQuery object and the library corrects for the IE deficiency, or at least thats the way I understood it and one of the reasons amongst many I started to use the library over plain vanilla JavaScript?.

N.B of course I may have got that badly wrong as those of us that have had to struggle through years of IE 5.5 / 6 and the workarounds have tended to avoid CSS3 advanced selectors; would have to test this really.

Tried a few test in IE6 and can’t get any class tokens added, scripting is running but IE refusing to play ball with even basic add class to some other element, the hover function works, so at a loss for the moment.

Edit/ was writing this to the ticket but couldn’t post it ? see you have covered my initial point about jQuery and it’s usefulness where advanced selectors are concerned.

@jeffsayre; I’m too cheesed off and tired to bother right now. Installing the latest BP locked me out of WP somehow, and even creating a new MD5 password and resetting it via phpMyAdmin isn’t getting me back in. Disabling BP by removing the folder gives me the white screen of death. I swear, I’m close to saying to people, “You want to talk online? Go use blogger.com and leave me be!”

@DJPaul,

I do prefer CSS only as well as even dumb guys like myself are able to change CSS.

Make sure BP is activated sitewide.

Then use a forums loop:
https://codex.buddypress.org/developer-docs/custom-buddypress-loops/the-forum-topics-loop/

@lincme –

I would suggest starting a new thread as your issue will more than likely get lost in this too-long-of-a thread. This thread was really a call to test the pre-release branch version of BP 1.2.5.

@DJPaul –

Because, as you state in the Trac ticket thread, IE 7/8 does not support the :nth-child selector in CSS. But it will work when it’s used in JQuery. It is a simple, single line fix — at least for the alternate table row highlighting.

@johnjamesjacoby et al; OMG NO! I just very carefully installed BP 1.2.5 locally on xampp; perfect. I did the same, very carefully, on my server. Now the site works, but ALL of my log-ins are dead, and it won’t send me an emergency log-in by email because it doesn’t recognise a darned thing!

Okay, see my most recent post in that Trac ticket. I’ve discovered that :nth-child selector is not recognized by IE 7/8 when used in CSS but it does work in those IE versions when used via JQuery. So, my proposed fix should work like a charm.

@peterverkooijen; I don’t think mixing in anonymous users defeats the point at all. Why should it? Don’t you talk to people you don’t know almost every day? Don’t people comment in passing about things, often making people smile? If software systems model the real world of human interactions, then I’d say that anonymity is quite normal. Perhaps you may still be stuck within the limitations of the terms you’re using? It’s not about “cramming everything in”, it’s about opening up to wider possibilities, and much, much easier ways of doing things which mean more to ordinary people rather than just those excited by technology (ie., us!)

Edit: In fact, you’ve just hit the nail right on the head. Rigid definitions lead to rigid mappings between rigidly defined data sources and the rigidly defined interface used to show their content. The future of CMS/Blog/Forum/Networking software is to drop the rigidity and open up to an amazing new flexibility and power. Not yet. But soon.

Again, why are we using that JQuery selector with CSS to implement stripes… rather than just using the CSS?

“Personally, I see nothing wrong with a social network which allows unregistered users to comment with CAPTCHA …”

I’m sorry, but the whole point of a social network is that it is not anonymous. You can’t have unregistered users on a social network. The point of a social network is to allow members to interact with eachother in a trusted environment like they would in the offline world; you introduce yourself, it has your picture and some basic personal information, you can make friends, etc. Mixing in anonymous “users” destroys that purpose.

Anonymous comments are fine on a forum, which is about topics. I go to forum to find answers to PHP questions; I don’t care who posts a coding solution.

“I really like the idea of them all being mixed together, if nothing else just to see what can be done, breaking down boundaries …”

Sure there will be many use cases where you would like to mix social network with a forum, with Twitter-like microblogging, with event management, with galleries, etc. But why cram everything into Buddypress?

I needed a simple, flexible social networking script with a solid reliable core that I could combine with other PHP scripts for whatever else I might need. Since bbpress forums started taking over Buddypress has become useless to me.

See the two new screenshots uploaded to https://trac.buddypress.org/ticket/2465#comment:15

@hnla — I agree. Unfortunately, IE 7 and 8 do not support the simple JQuery fix. However, IE 9 is finally with the program on this issue. But, there are other ways to strip a skunk.