BuddyPress.org

Hi!

Does anyone have a solution for this problem? Is it possible to be allowed in capital letters in usernames? All the Links on Google and buddypress.org doesn´t help…

I have tryed out a few things… For example, I’ve replaced in the bp-core-signup.php on line 321
preg_match( "/[a-z0-9]+/", $user_name, $maybe );
with
preg_match( "/[a-zA-Z0-9öäüÖÄÜß]+/", $user_name, $maybe );

In line 327 an error message is generated when the user name does not comply with certain criteria.

if ( !validate_username( $user_name, $strict = false ) || in_array( $user_name, (array)$illegal_names ) || $user_name != $maybe[0] )
$errors->add( 'user_name', __( 'Only lowercase letters and numbers allowed', 'buddypress' ) );


When I comment out followed code in Line 327:
!validate_username( $user_name, $strict = false ) ||
my preg_match rule works with the capital letters and special characters, but I think that will later have an impact on the log on and other things.
Capital letters are now being accepted, but no special characters such as “ßöüÖ” … -.-

validate_username() is a WordPress function
https://codex.wordpress.org/Function_Reference/validate_username
and it uses
sanitize_user() which is documented here:
https://codex.wordpress.org/Function_Reference/sanitize_user

Has anyone any idea how to do this without an sql injection or incompatible usernames later?
I would have liked that a user can log in as “SteffanieKönig” …

When we get together at a solution I would like to summarize the whole issue and as a plugin, but I’m at the end of my knowledge! -.-

SickSight

99% of the wordpress themes out there are gpl. snag away.

@alanchrishughes – try contacting the plugin dev and see if they can update the content filters for buddypress. the only profanity filter bp-ready i’ve seen is https://wordpress.org/extend/plugins/webpurifytextreplace/ but that is a pay-for-solution

@grosbouff There is the BP Followers Plugin by @apeatling for your reference

One difference between Friends and Followers is that Friends is in core while Followers feature needs the plugin to be activated.
https://wordpress.org/extend/plugins/buddypress-followers/
https://wordpress.org/extend/plugins/buddypress-private-messages-for-followers-only/

The other difference is Followers is ala Twitter following. The “follower” doesn’t need to be approved by the one he follows. While for “Friends” to connect completely friendship request must be approved by the other party.

Multiple accounts using one email address is more of a WordPress thing, and it’s not natively supported. There’s a WP plugin that did that https://wordpress.org/extend/plugins/allow-multiple-accounts/ in WP 2.9.2 but reported broken for WP 3.0.

wordpress 3, BP. 1.2.5.2, 7000 members
Submitted URLs
216,024
4,975 URLs in web index
bp-sitemap-activity.xml.gz Sitemap Jul 14, 2010 50,000 172
bp-sitemap-groups-f.xml.gz Sitemap Jul 14, 2010 2 1
bp-sitemap-groups.xml.gz Sitemap Jul 14, 2010 10 8
bp-sitemap-members-a.xml.gz Sitemap Jul 14, 2010 43,362 333
bp-sitemap-members-g.xml.gz Sitemap Jul 10, 2010 3 1
bp-sitemap-members-x.xml.gz Sitemap Jul 14, 2010 6,982 430
bp-sitemap-members.xml.gz Sitemap Jul 13, 2010 7,228 1,394
bp-sitemap.xml Index Jul 14, 2010 107,587 2,339

Busy looking into that myself as im newb still Give me a shout if you find something, but should just be simple if else statement.

meh im being stupid, else {
wp_redirect( get_option(‘siteurl’) . ‘/about’);

instead of redirecting them ( wp_redirect ) you could just hide it in the same statement.

ignore the above, “being stupid”.. Just woke up.

check this out:
http://wpmu.org/how-to-show-or-hide-content-in-wordpress-wpmu-based-on-user-authentication-roles-and-capabilities/

@Anton
https://wordpress.org/extend/plugins/buddypress-restrict-group-creation/ requires PHP 5.2
https://buddypress.org/community/groups/bp-group-management/ for extra controls

“Is BuddyPress the right foundation on which to create this site?”
Yes it is. Some features you mentioned are already covered out of the box. Some features would have to be expanded on by your programmer.
– https://buddypress.org/about/story/
– http://en.wikipedia.org/wiki/BuddyPress
– https://wordpress.org/showcase/flavor/buddypress/

Use Jet QuickPress in main blog – https://wordpress.org/extend/plugins/jet-quickpress/screenshots/
You’ll see that there are areas to input tags, categories and dropdown of which blog/s you want to post to.

“BP seemed to move it into /blog/ subdir.”
BuddyPress did not move anything in your installation, even If you defined BP elsewhere than main blog,

Backup database, deactivate BP and BP-dependent plugins, then go to your database and delete around 15 tables with : yourprefix_bp_componentname

If you need to move WP to root, https://codex.wordpress.org/Moving_WordPress – as always, back up your database before attempting the move

@1stAngel @MrWiblog my bad, the version of the Secure Invites for WordPress MU working in my WP 3.0 installs is Version: 0.9.6. Strange that that version in not in the other versions page of the plugin
In any case, here’s the code of the plugin I am using. http://wordpress.pastebin.com/LD2vL9rY

Yes, 1.2.5.2 is correct.

Trunk (1.3-bleeding) is many months out of date; I’d strongly recommend you switch to the 1.2 branch, trunk is not recommended right now.

It has activity set to front page. Go to dashboard menu General > Reading and there you can change the front page display -select ‘static page’ set ‘Activity’ as front create a new blank page named ‘News’ ? and then select that page to display posts on.

RE: https://trac.mu.wordpress.org/ticket/906

I’d love to know why this doesn’t affect everyone on IIS.

We have to try to get things to work for 80% of our users; if we encouraged people to edit the default theme or any of the core BuddyPress files directly, most of those people are going to come back and complain when we release a new version of BuddyPress because they won’t understand what’s really happened.

Theme developers of course have two options — either as a child theme, of BuddyPress’ bp-default or one of the many other theme frameworks, or as a seperate/existing theme with the BuddyPress template files copied in. Both have their disadvantages and advantages.

Just tried to register on your site and I get a white screen after hitting submit.
Please deactivate any plugins other than BuddyPress (if you haven’t done so already).

Are you able to access your server’s error log? If so, there is most likely a message in there. It would help if you could paste the contents of this log here.

—

Also you say you upgraded to WordPress 3.0. Do you experience the login issue you noted in point #3 with BuddyPress deactivated?

@thekmen I’m just one of the people that think themes should be completely separated from the plugin the same way they are separated from WordPress. Trying to reduce everything to one theme with a bunch of child themes is only going to slow down development and discourage people from appreciating Buddypress. I mean look how few themes there are, one theme with with a couple color alteration child themes and now people are excited just to be able to use the generic WordPress default.

I actually prefer this not being a child theme because I’m not a programmer and don’t know enough to write a theme completely from scratch, and this WordPress default is the most basic sandbox like template to start with.

I think it is an inherent difference between front end and back end developers. You guys don’t care what it looks like as long as the programming is constantly up to date and I don’t mind if I miss some updates as long as its designed well. You guys try to plan for every possible scenario and I design to make things as customized as possible. I have a million ideas of things I want to do designing a theme for a non-profit I work with, but I’m not always certain about writing the php to get the functionality on track so I post on here about it. Instead I get front end advice, suggesting I write an entire plugin for something that can be accomplished with a line or two of html and css, just to keep the plugin pure. Neither extreme is the answer, I’m just saying it is a bit lop sided right now.

1) https://wordpress.org/extend/plugins/wp-email-login/
2) no plugin exists
3) there might be a plugin for this… though I’m not 100% sure.