Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • @inkblots

    Participant

    Although I certainly respect your opinion on the matter, I’m just not exactly sure what the size of a community (after all, every community always starts out with just one individual) has to do with anything at all here concerning basic privacy options, @ubernaut, but, @bphelp, you can certainly implement activity stream privacy for “friends only” and such, there just isn’t any elegant or up-to-date plugin that is current with BuddyPress 1.6/1.7 which works right out of the box, not that I know of anyhow, so you’ll either just have to code it and customize it in yourself or hire someone to do it for you.

    The biggest problem with these types of out-of-core solutions (plugins, custom code, etc.) is that they, generally, have to continually evolve with the core updates for each release, and once you’ve built a community based on certain privacy options, ones that your members have come to expect and rely on, and they then all of a sudden break on you with a new update of core it then puts your entire community at risk, not to mention the immediate loss of respect and alienation of your site’s members, and that’s quite obviously not a good thing to have happen.

    Don’t worry too much about being “negative” or “attacking” anyone here with such a valid question either. I’ve been working with and using BuddyPress since it first came out under Andy Peatling about 4-years ago, and full core privacy options should have definitely been one of the very first items to go in, and right from the start too. No doubt about it. Why haven’t they been implemented yet, especially after all of these years? I haven’t a clue.

    I am betting though that core privacy options for activity, perhaps even full core privacy, will eventually make it into the core code and end everyone’s misery surrounding this entirely worn-out subject, but, again, when that is we just don’t know, but I’m guessing that with the new theme compatibility in BuddyPress 1.7 it is sure to light a bigger fire under it due to more mass adoption, as well as with the unending beat of the privacy advocate drum here.

    @inkblots

    Participant

    @enquirer32, for your first issue you could try a plugin like https://wordpress.org/extend/plugins/wp-external-links/ and this should work exactly as you wish in conjunction with the Activity Plus plugin by opening a link in a new window with the settings properly adjusted within the plugin admin.

    As for the second issue, I’m not sure as I’ve not used any of the widgetized options there before…

    Hope this helps!

    @inkblots

    Participant

    @ubernaut that is correct.

    @inkblots

    Participant

    Good to hear it, @bluellipse!

    And sorry, BuddyPress Mods, and everyone else, for the multiple replies here that I couldn’t get to work properly with the correct code (backticks, , etc.) showing?

    @inkblots

    Participant

    @bluellipse it’s not letting me place the code within the reply for some reason, so just find what I’ve been able to post above (it stripped some of it away, such as; meta name=”viewport” content=”width=device-width, initial-scale=1.0″) and remove that entire line of code that exists between the php statements and you should be good to go.

    @inkblots

    Participant

    Sorry, the code to remove is;
    ?php if ( current_theme_supports( ‘bp-default-responsive’ ) ) : ?><?php endif; ?

    @inkblots

    Participant

    Sorry, the code to remove is;

    @inkblots

    Participant

    Hey @bluellipse don’t worry about reverting or any of that other jazz, just try removing the following code from your header.php file near the top;

    Of course, place the updated header.php file in your child theme so that it’s not overwritten on the next update.

    I can’t recall offhand if we’d also deleted anything else, but I’m pretty sure that this will quickly solve your problem.

    Sorry everyone, but the “responsiveness” does look terrible on mobile, at least concerning the BP-Default/child theme, and we killed it off as soon as it showed up and are currently exploring other options for mobile, which is extremely important these days, no doubt about it, but achieving it by making your site into a jumbled mess is most definitely not the way to go here.

    Hope this helps!

    @inkblots

    Participant

    Sorry @mercime (and, yes, I’ve already read through the ticket in trac, along with the documentation, etc.), but Administrator elevated Moderators from within a community definitely do not belong in there messing around with Group naming structures and descriptions. They are there to merely moderate the internal content and behavior within the Groups/Forums themselves (like I need to tell you that, being that you are yourself a Moderator here on BuddyPress – and a hell of a good one at that if you don’t mind me saying so!), and that’s it.

    With this proposed change, will newly elevated Group Moderators then also be able to delete and/or upload Group avatars once given these new permissions, or even change the Groups privacy settings at will? Not a good “fix” at all if you ask me, no matter what the existing documentation and so forth has to say about it.

    I believe that the real error here occurred at some point in time within the direction of the documentation if anywhere, and that is actually what needs to be fixed here, and not with keeping on going down a road where the sign with the arrow pointing one on where to safely go somehow got turned around at some point and is actually now pointing off over the cliff, right?

    Hugo ( @hnla) has it absolutely right here with his take on this proposed change within the trac ticket located at https://buddypress.trac.wordpress.org/ticket/4737

    If you look at our own Group structure within our currently-being-developed site at https://PhysicalActivity.com (which I’d personally registered all the way back in December 1999) you’ll see that we’ve got over 200 meticulously generated Groups, and with thousands more to come, that we definitely do not want members who have been elevated to Moderators digging in and messing around with when it comes to Group names and descriptions, among other things, and I’m guessing a lot of other folks (site Administrators) would feel the exact same way about it as well. Isn’t it enough that Moderators can already pretty much clear out the entire contents of a Group/Forum?

    We do not allow our members to create their own Groups, and that is definitely by design. It would certainly create havoc and chaos if we then, eventually, had 100’s of Moderators running wild within our set Group naming structures, descriptions and so forth, especially with thousands upon thousands of Groups to have to keep track of in the future.

    When we’re done here, we’re definitely going to be one of the bigger sites making use of the WordPress/Multisite/BuddyPress platform so, needless to say, and like a lot of other folks here too, we’ve got a lot of time, effort and money invested in helping to properly see this whole thing (the ultimate development and direction of BuddyPress) through as well, even if our contributions and/or opinions are just brushed to the side at times.

    We’ll definitely be stripping this update out of the code when (if) it drops with, what looks to be from @djpaul, 1.6.3 in the next several days or so here.

    If anything, this sounds more like an options type of thing (“Allow Moderators to Change Group Name and Description” – “Do Not Allow Moderators to Change Group Name and Description”), or even plugin territory for the few people who would actually get good use out of something as reckless as this.

    All of you guys and gals working on BuddyPress with your time, efforts and skills are absolutely fabulous (and I know, because I’ve been working with and dabbling in BuddyPress since its inception when Andy Peatling was still running the show, and I’ve been working with WordPress since its beginnings as well, even going so far as to register domain names like WordBlog.com, CustomerBlog.com, NoteBlog.com and so forth to use in conjunction with it way back in 2003/2004), so please don’t take this as anything more than me just tossing a little dirt (with a pinch of love) into the gears in the hopes of getting people to stop and take a second, or even third, look into a quick and hastily made change that just shouldn’t be made in the first place.

    You know what they say about fixing something that isn’t broken…

    Thanks for lending an ear or two to me here. Keep up the good work!

    Best regards,

    Kyle

    @inkblots

    Participant

    This new cropping “feature” was introduced with the release of WordPress 3.5, and what you need to do, at least what we’ve found that kind of works, is to drag that little black square with the white outline outside of the avatar entirely and then line up your cursor as close to one of the corners of the avatar as you can and then drag it across. It won’t be perfect, and it will degrade the avatar image quality somewhat (no matter what you do), but it will then work as best as can be expected.

    Oh how we miss the old way, just mere weeks ago, with how the cropping feature worked. It was quick and perfect, but not so anymore. Perhaps it does work perfectly for some folks, but not for us, and obviously not for you either.

    Hope this tip helps!

    @inkblots

    Participant

    We ran into, what I assume here, is the exact same problem that you’re having, but with the BP-Default theme running WordPress 3.5 and BuddyPress 1.6.2, so we tracked down the problem and just implemented the changes from this BuddyPress trac ticket (https://buddypress.trac.wordpress.org/ticket/4510) that is set to fixed/closed and will drop soon here with the release of BuddyPress 1.7, and all is well again with threaded comments and replies, as well as fixing a few other quirky problems that we were having.

    I’m actually a bit surprised that more folks aren’t posting on the support forums here about these same issues directly related to this. I would have to imagine that it’s happening within a lot of other installs, especially considering that it’s definitely occurring within the BP-Default framework.

    I hope that this lead helps you out…

    @inkblots

    Participant

    How about this:

    https://wordpress.org/extend/plugins/restrict-usernames/

    It looks like something that might possibly work for your problem, and would disallow the use of spaces in the username since I believe it’s all handled on the WordPress side of things for BuddyPress anyhow concerning registrations and so forth…

    @inkblots

    Participant

    If you are using the BP-Default theme you just go into your WordPress Admin panel, go to Themes, choose “Editor” and you should then be able to find what you are looking for in BuddyPress Default under;

    Main Index Template
    (groups/index.php)

    This file should be where you can rename those few things, among others, though you really should create a child theme (https://codex.buddypress.org/theme-development/building-a-buddypress-child-theme/) to add any such changes or customizations with in order to future-proof yourself so that when a new version of BuddyPress is released it doesn’t overwrite your own custom changes to the code.

    Don’t forget to save the changes to the file before you proceed, and be extra careful as to what you are making any such changes to when doing so!

    If you mess it up you can always pull a fresh file from another copy of BP-Default and upload it to the correct place on your server and just start over from scratch.

    Good luck!

    @inkblots

    Participant

    This one can drive a person absolutely mad trying to figure out. Depending on what your setup is (Multisite-enabled?), you can try this method;

    1. Create a noreply@yourdomain.com (or whatever you want to call it – you can even use a Gmail address for this, though I’ve not tried that approach myself) email address, if you don’t already have one, with SMTP relays, especially if your ISP has restrictions in place for sending email.
    2. Add and activate the WP-Mail-SMTP plugin; https://wordpress.org/extend/plugins/wp-mail-smtp/
    3. Configure the plugin settings to fit your needs, or as per the plugin instructions suggest, by going to “Settings” -> “Email” in your WordPress admin area.

    At least that’s what I recall from my past experience with BuddyPress enabled and having this issue, and it worked like a charm!

Viewing 14 replies - 1 through 14 (of 14 total)
Skip to toolbar