[@henrywright-1 Member 13 years, 6 months ago]

Very nice use of BuddyPress’s features plus being responsive you can capture the mobile audience

[@henrywright-1 Member 13 years, 6 months ago]

Thanks shanebpdev, that sounds like a good approach, think it will be quite a big task.

[@henrywright-1 Member 13 years, 6 months ago]

Activity comments currently use ajax. Perhaps you could take a look at how that works and use that as a starting point.

[@henrywright-1 Member 13 years, 6 months ago]

I would have thought you can disable site wide notifications via settings. It seems you can’t. I agree with you, not sure how useful/appropriate this feature is for professional sites.

[@henrywright-1 Member 13 years, 6 months ago]

Thanks for the tip @missnorthking, I did notice the options under settings.

I’ve been looking for a good way of encouraging users to add an avatar. My thoughts so far are these:

Option 1. Add an avatar upload button to the registration page. The problem with this solution is very well pointed out by @djpaul in trac ticket 2741. Images are uploaded to the server by non-registered users – not a very palatable approach for most developers.

Option 2. Break the registration process into steps. The first step is user registration and activation with the second and final step being an avatar upload (optional) screen. This would ensure images are submitted by genuine site users who have already registered with a valid email address.

Option 3. Do nothing. Have lots of mystery men photos display across the site.

I’d welcome alternative ideas from anyone?

[@henrywright-1 Member 13 years, 6 months ago]

Nice site. Just noticed you have ‘persons’ as a nav item. I’d say ‘people’ is a better word to use.

[@henrywright-1 Member 13 years, 6 months ago]

Thanks for the background info @djpaul, appreciated!

[@henrywright-1 Member 13 years, 6 months ago]

@hnla none was taken! :}

[@henrywright-1 Member 13 years, 6 months ago]

But I think we are missing the elephant in the room (except for @shanebp). Why would non-logged in visitors want to see the “This field can be seen by” text on the registration page?

I think this whole area needs some further thought.

[@henrywright-1 Member 13 years, 6 months ago]

@hnla

How this is interpreted depends very much on what you want to achieve. If you are a developer in the process of designing the public member profile page (displaying their profile field values) then you would think of visibility to mean the field values. However if you are in the process of designing the edit profile page (displaying the input form fields) then you would think of visibility to mean the input fields.

As you can probably see, my ‘huge mis-understanding’ was quite easily done :}

[@henrywright-1 Member 13 years, 6 months ago]

Yep, i see it. According to Boone, it refers to the field value. Slightly misleading text i must admit.

[@henrywright-1 Member 13 years, 6 months ago]

Just got clarification from Boone. Visibility doesn’t relate to the actual form input field, it relates to the field’s value. So this issue isn’t a bug.

[@henrywright-1 Member 13 years, 6 months ago]

Thanks for helping test. Bug report here:

https://buddypress.trac.wordpress.org/ticket/4942

[@henrywright-1 Member 13 years, 6 months ago]

No need to answer I can see it does actually use it. Just fixed it in my theme

If anyone comes across this in 3 years time looking for a solution. I resolved the issue by making sure the template tag was wrapped in a div with class ‘message-search’. e.g

bp_message_search_form();

[@henrywright-1 Member 13 years, 6 months ago]

Instead of working backwards, try disabling your theme and using the default to see if the problem exists. If so you know it is your theme. Specifically look at templates members/members-loop.php and members/index.php.

[@henrywright-1 Member 13 years, 6 months ago]

Titles seems to be hard coded into the BP core. Looking at Trac the development team are planning to make labels changeable in 1.8. It was originally planned for 1.7 but seems to have been pushed back

As it stands, your only way to change all labels throughout your site is to hack the core (not recommended).

[@henrywright-1 Member 13 years, 6 months ago]

Put this in your bp-custom.php file

`define ( ‘BP_FRIENDS_SLUG’, ‘colleagues’ );`

[@henrywright-1 Member 13 years, 6 months ago]

Take the standard loop

`if ( bp_has_activities( bp_ajax_querystring( ‘activity’ ) ) ) :
while ( bp_activities() ) : bp_the_activity();

locate_template( array( ‘activity/entry.php’ ), true, false );

endwhile;
endif; `

If you wanted to output only the last 5 entries you would do this

`if ( bp_has_activities( bp_ajax_querystring( ‘activity’ ).’&max=5′ ) ) :
while ( bp_activities() ) : bp_the_activity();

locate_template( array( ‘activity/entry.php’ ), true, false );

endwhile;
endif; `

If you wanted to combine parameters you would use the “&” character. E.g

`if ( bp_has_activities( bp_ajax_querystring( ‘activity’ ).’&max=5&scope=mentions’ ) ) :
while ( bp_activities() ) : bp_the_activity();

locate_template( array( ‘activity/entry.php’ ), true, false );

endwhile;
endif; `

Hope this helps a litte.

[@henrywright-1 Member 13 years, 6 months ago]

Couldn’t you make the To field a hidden input with a value of ‘admin’ with a conditional to check if the user is a member (and not the admin themself)?

e.g in compose.php change the text input to something like:

if ( !is_super_admin() ) {
input type=”hidden” name=”send-to-input” value=”admin”

} else {
input type=”text” name=”send-to-input”
}

[@henrywright-1 Member 13 years, 6 months ago]

https://codex.buddypress.org/developer/developer-docs/loops-reference/the-activity-stream-loop/

This will help. Use “max” to output only the last 5 entries.

[@henrywright-1 Member 13 years, 6 months ago]

The main reason is I am using the Twit Connect plugin which seems to be the only plugin which let’s a member register via Twitter that is compatible with BuddyPress. When a user  signs up their email isn’t captured as Twitter doesn’t make it available via their API. They also don’t have a password given to them but I assume BuddyPress creates one automatically for them. So if the user wants to log in in future they always have to use their Twitter to connect. There is no fall back on a username and password. My idea is to get them to add their email and password via general settings. But there is the problem of the current password requirement.

 

Any ideas how I could best approach the problem?

 

 

[@henrywright-1 Member 13 years, 6 months ago]

Hey Luccame. Good point. Of course the passwords won’t be available as they’ll be only computer readable. Any more suggestions on how I could make the current password field not required on the general settings page?

[@henrywright-1 Member 13 years, 6 months ago]

If you echo it to the value attribute of the hidden input then it would be visible in the source. This of course isn’t much of an issue as it would be the logged-in user only who could see it. Once logged out (or once they move to a different page) the value would be gone from possible view.

Just got to work out how best to echo the password… perhaps @modemlooper can help point me in the right direction with that?

[@henrywright-1 Member 13 years, 6 months ago]

Thanks but wouldn’t the password then be visible in the hidden input’s value attribute (visible via the page source)?

[@henrywright-1 Member 13 years, 6 months ago]

Would this work? Remove this:

&& wp_check_password( $_POST[‘pwd’], $bp->displayed_user->userdata->user_pass, bp_displayed_user_id() )

from bp-settings/bp-settings-actions.php

I don’t really want to hack the core though.