[@stwc Participant 16 years, 11 months ago]

I would call ‘Inappropriate content flagging’ totally essential, and am thrilled that it’s going to be in. I wasn’t even aware that is was coming, so that’s a win for me!

[@stwc Participant 16 years, 11 months ago]

I have had total cessation for the last two weeks without using plugins, using the procedure I outlined here.

[@stwc Participant 16 years, 11 months ago]

Yay! Thanks for the new Welcome Pack build, DJPaul. I’ll be installing it right away, and will report back if there are any issues.

[@stwc Participant 16 years, 11 months ago]

#2 is something I’d love to see native to BP and have been investigating 3rd-party ways to get it working, Gigya being the latest I’m messing with. I’d be willing to help if I can on a native toolset, most definitely. I’m completely crap at writing code, though, I must admit.

But I’d *really* like to see new versions of the Welcome Pack and Achievements first, nudge nudge.

[@stwc Participant 16 years, 11 months ago]

Just came in here to suggest changing the permalinks. I had the same problem way back when, and it took forever to figure out!

[@stwc Participant 16 years, 11 months ago]

Cross-posting this here from another thread. It’s now about a week since I’ve had anymore of the firstnamesurname19xx signups.

Well, I don’t know — I seem to have lucked out, or it’s just that my site is too new and so-far untrafficked, but the few very simple, small changes I made last week seem to have stopped the firstnamelastname19xx signups.

1) I changed the some of the text on the /register page.

2) I removed the “powered by” text in footer.php of my child theme (someone mentioned that it was being searched for)

3) I changed the register slug in wp-config.php

4) Added a functions.php file in my custom childtheme with the following code to redirect signups for all blogs to the Buddypress register page

function rk_signup_redirect() {

if (strpos($_SERVER['REQUEST_URI'], 'wp-signup.php') !== false ) {

$url = 'http://mydomain.com/customregisterslug';

wp_redirect($url);

exit;

}

}

add_action('init', 'rk_signup_redirect');

where mydomain.com is, you know, my domain, and customregisterslug is the slug I changed in step 3.

I don’t think I changed anything else — no captchas or anything — and I’ve received zero splog signups in the 5 days since, after getting a few a day before that. Fingers crossed.

[@stwc Participant 16 years, 11 months ago]

well, I actually do not want to explain my users how to use “[ ]” brackets.

I just added a div on the appropriate signup page in my child theme explaining how to do it. Users see it during registration. Well, they will, when I eventually get some.

[@stwc Participant 16 years, 11 months ago]

(I’m going to try to be helpful rather than just telling you to go elsewhere. I want Buddypress to grow, and users helping users ought be part of that. I’d also like the forum here to be a useful resource. So many threads at mu.wordpress.org are just cries for help with zero replies. That sucks.)

wordpressfan, I’d probably approach this using Roles. I’ve never done it, but you could set the Dashboard user default role in Site Options to ‘Inactive’. That would allow you to monitor signups, and approve as necessary, I’d imagine. As long as users know that there is a process in place where they have to wait for approval. There are plugins out there that allow you to create custom roles, too, but I’ve never used them.

In terms of the registration emails sent to you as admin, this is also a WMPU thing, not on the Buddypress end. I’m sure I’ve seen plugins that allow you to edit these, but I can’t find them for the life of me. If you’re comfortable with hacking the WPMU core (and rehacking after updates), you can find the place these emails are generated in

function newblog_notify_siteadmin

in wmpu-functions.php in /wpmu-includes

off the root of your WMPU install.

[@stwc Participant 16 years, 11 months ago]

I have a functions.php (with one custom function for redirects) in my child theme, no issues. I guess you’re doing something wrong!

[@stwc Participant 16 years, 11 months ago]

someday we will have the same auto-update we see in WP…

I’m confused. I just used the WMPU autoupdate to get to 2.8.6!

[@stwc Participant 16 years, 11 months ago]

Without knowing anything about the paid plugin in question, it’s pretty hard to make a guess. You might want to contact the plugin author, since I assume that if they made you pay for it, they offer support.

I note that it’s not one of the ones they explicitly say are Buddypress compatible, though, so you may have issues.

It can’t be a complicated bit of code, though, so I’d just open it up and see what’s in the code, and hack in the URL necessary. You’ll need to get the currently logged-in user from BP in order to build the URL of their profile, page, though, because their username is part of the URL.

That’s more than I know how to do off the top of my head, but I’m sure someone with more knowledge of BP coding can help you there.

[@stwc Participant 16 years, 11 months ago]

I seem to recall using this with success on an old pre-1.1 install to make that happen : https://wordpress.org/extend/plugins/cosmic-bp-user-signup-password/

[@stwc Participant 16 years, 11 months ago]

Hmmph. Keeps telling me ‘an error occurred’ in the WP dashboard when trying to enter my API key from RPXnow. Ah well, I’ll have a look later.

[@stwc Participant 16 years, 11 months ago]

I remember trying that and not having it work the way it ought to have, but I can’t remember why.

I’ll look at it again, maybe. Care to share any tips on getting it working, socialpreneur, or is it doing everything you want straight out of the box?

[@stwc Participant 16 years, 11 months ago]

Great stuff, thanks! I will definitely be checking it out.

[@stwc Participant 16 years, 11 months ago]

My first thought would be: why ‘instead’?

My second thought would be: geeks and techies and developers know about OpenID (and it confuses me, even, to be honest). Your average normal person doesn’t know OpenID from a hole in the ground, but they sure as heck know how to log in to their Facebook or Twitter account.

[@stwc Participant 16 years, 11 months ago]

I’m always leery of depending on third-party stuff, but this seems pretty nice, and if it’s set up right, even if Gigya goes away (which, looking at their client list, doesn’t seem likely), I reckon it wouldn’t cripple our BP sites in any way.

[@stwc Participant 16 years, 11 months ago]

Thanks!

[@stwc Participant 16 years, 11 months ago]

But keep in mind that unless you make that css change in a child theme which might be otherwise identical to the default, you’ll lose it when BP 1.1.3 is released.

[@stwc Participant 16 years, 11 months ago]

Very nice work. Makes me want to revisit my nearly-bog-standard home page and go to town on it. I think I just might do that today!

Any tips/tuts you care to share on how you did some of the neater stuff (like the modal registrations) would sure be appreciated!

[@stwc Participant 16 years, 11 months ago]

Don’t forget to put the define statements BEFORE the STOP EDITING HERE LINE in the config.php. That had me scratching my head for a while.

[@stwc Participant 16 years, 11 months ago]

It is bad practice to edit the Buddypress Default theme that ships with the plugin itself, because the next time you update, all of your customizations will be lost. That is, obviously, a bad thing.

To make a child theme, just create a new folder with your FTP client at the same level as your bp-default and bp-sn-parent. Call it bp-whateveryoursiteiscalled. Copy the contents of bp-default to it. PRESTO, you have a child theme! Select that theme in your dashboard, and any changes you make will be live right away.

Now you can copy whatever files you want from bp-sn-parent to your new child theme (preserving directory structure, if I’m not wrong) and edit them (ie, in this case, header.php). Any files you do not copy and change will stay ‘stock’. And next time a new version is released, you can upgrade with confidence and any changes you make will persist.

Child themes are a godsend.

[@stwc Participant 16 years, 11 months ago]

Sociable is way less ugly than either of those and does the same thing.

[@stwc Participant 16 years, 11 months ago]

Yep, here.

define ( 'BP_REGISTER_SLUG', 'signup' );

except rather than ‘signup’ I used ‘jointhecommunity’ as I recall.

[@stwc Participant 16 years, 11 months ago]

If I’m not wrong, you can just make the Buddypress Default theme available to users in the Site Admin–>Themes section of the dashboard, and disallow other themes.

I’d probably create a new child theme (blank, basically, so it’s identical to the Default Buddypress child theme) and name it after my site, then make it the only one available.

You can change the default WPMU theme if you want more than one available via a code snippet somewhere here in the forums that I have since lost the link to (check the stickies?) or with this paid plugin (which is in and of itself not worth the signup fee I don’t think).

This free plugin may offer the same functionality but I haven’t tried it.

Alternate: Don’t know if this still works. I haven’t tried it.