BuddyPress.org

@rosyteddy, I found that the quickest, easiest, and most efficient solution was to substitute a different login widget. This one I found really works perfectly for me:

https://wordpress.org/plugins/sidebar-login/

Many thanks, nonetheless, for your ongoing support and advice.

@mcpeanut Thanks, and like I said I’m aware of the issue of too many admins. I’ve been working with WordPress for over 10 years, I know about roles and capabilities. This is a site that I help out with – not my personal site, and there are a lot of moving parts.

I am curious if you can replicate this odd behavior, thanks for investigating.

Sorry … I guess I should have mentioned that I’m using WordPress v.4.1.1 and BuddyPress v.2.2.1
The site URL is: http://mylifeismymuseum.eu/mlimm/activity/ and that I have tested with several different themes.

So asking again … I’ve found that, if a site member clicks the ‘Log In’ button without first entering their username and password, the page redirects to the default WordPress login page (/wp-login.php)

How (and where) might I modify the code so that, instead, it simply fails or, better, displays a an error message to remind the user to fill in their login credentials?

@peter-hamilton

Really cool to see the plugin in action and thanks for the review on wordpress.org! 🙂

This is the Happenstance theme. I believe it is from a production site, but it is available in the WordPress theme download search. I can only add the widgets to a Buddypress page if it is under Single Post Page, but if I do that, then the widget goes to every single post page, which I do not want.

Hey @danbp

Thanks for the feedback. Before I answer your question, I just want to point you to question 4 in the plugin’s FAQ

Why is it that some members don’t have an identicon?
An identicon is used as a member’s avatar only if a profile photo hasn’t been uploaded. After activating the plugin, all new members will be allocated an identicon. Existing members will need to log in to get their identicon.

The reason existing users have to log in to get their identicon is simple. Imagine if a site had 100,000 existing users. At the point the website owner activated the plugin, there’s no way 100,000 fresh identicons could be created. It’d crash their server immediately. I needed a way of staggering the creation of identicons for existing users. The approach I decided on was to create existing user’s identicons on their next login.

Now, to answer your questions 😀

– first time i activated BI, all users showed the mystery man. And plugin works, as i see the border.

Great! That’s expected.

– changed profile photo of admin: custom picture appeared.
– removed the picture: identicon appeared on the admin account.
-tried to do same thing with a dummy user. Nothing happened.

The reason nothing happened for the dummy user is because you’re still logged in as admin. You will need to log in as the dummy user for his/her identicon to be created.

– create a new user from back office, with gmail address, identicon showed up

Great, that’s a new user created. Identicons are created for all new users so that’s expected.

– manually created a identicons folder in /uploads/

There’s no need to manually create folders. The plugin takes care of that for you automatically 🙂

– modified all dummy user mail address. Mystery man still showing.
– applied a custom picture to one, ok, then removed. Mystery man again.

Again, if you’re doing this logged in as admin, then nothing will happen. The actual dummy user will need to log-in in order for their identicon to be created.

– tried global settings to “empty avatar”. Nada ! Reverted to default MM setting and still no identicon.

Global settings aren’t taken into account by design. If you want to disable identicons, simply disable the plugin. Want them back? Re-enable it 🙂

On a dev site, using this plugin would really help to avoid calling an external avatar service.
Would also be true for a prod site, where specially gravatars are mentionned to be optimized as they slow down page speed.

That was one of the driving factors behind creating the plugin. The beauty of it (in my opinion) is there’s no need to make requests to an external service. Everything is stored locally which should improve page load speed.

Hope this info helps to clear up any confusion. If you need any more info then just give me a shout, and feel free to open a support ticket on the plugin’s forum if you find a bug.

– posts are handled by WordPress. BuddyPress speciality are the members, not publication.
When group members want to talk together, they can use the notice editor for brief messages or if you install bbpres they can use the forum.

OK, thank you 🙂

-It exist a buddypress group blog plugin, who allows group members to use a blog, similar to the main blog.

In my case, I have Custom Posts Type.
In my CPT archive, all posts are listed, but I would like to restrict access to certain groups.
So I don”t think the buddypress group blog plugin would help me.

– BuddyPress features are developped if there is a general need, rarely for particular usage.

All right 🙂

I’ve just posted a new ticket in buddypress trac.

Thank you Dan