Search Results for 'profile fields'
-
AuthorSearch Results
-
April 18, 2013 at 11:48 pm #162111
Renato Alves
Moderator@jancbeck Maybe with a few coding that would be possible…
April 18, 2013 at 8:19 pm #162091operapreneur
ParticipantStill looking for some guidance.
I’m not sure why an x_profile field is not treated exactly like meta data. It seems to me, this maybe specific to my project, that this would be very valuable. The Xprofile Custom Fields Type Plugin is very useful and is helping extend the functionality.
Alas, videos are still not embedding via bp_profile_field_data()
Any suggestions are welcome.
April 18, 2013 at 8:11 pm #162090jancbeck
Participant@maddogmcewan great tip – thanks! Unfortunately though, it allows neither file uploads nor are these fields searchable. I’m investigating using ACFs repeater field in combination with a front end form but this is also far from being perfect.
April 18, 2013 at 7:06 pm #162082Renato Alves
ModeratorAwesome @maddogmcewan! Thank you for sharing! =)
April 18, 2013 at 7:00 pm #162079maddogmcewan
ParticipantApril 18, 2013 at 3:08 pm #162057shanebp
ModeratorBingo re elephant.
While it’s easy to change by editing the register template, the why-is-it-there question seems worthy of a trac ticket.
April 18, 2013 at 2:57 pm #162056April 18, 2013 at 2:56 pm #162055Henry
MemberBut 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.
April 18, 2013 at 2:56 pm #162054Hugo Ashmore
Participant@henrywright-1 As you can probably see, my ‘huge mis-understanding’ was quite easily done :} yep and I meant no offence in the phrase ‘huge mis-understanding’ 🙂
April 18, 2013 at 2:52 pm #162053Henry
MemberHow 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 :}
April 18, 2013 at 2:21 pm #162051Hugo Ashmore
Participant@henrywright-1 ah you were labouring under a huge mis-understanding of what this meant, as Boone says it’s pseudo privacy for display of users details on their profile – if admin allows users to configure that given field – it’s NOT anything to do with whether the field is hidden on registration view.
However there are still issue with how this works with reg form or it needs a good review.
April 18, 2013 at 2:16 pm #162050Hugo Ashmore
ParticipantThis has definitely come up, the text label jogs my memory.
It may make sense that one had change link on pre-registration if the value selected was being passed along with the registration and setup of the user_meta and if the admin setting allowed users to change the field value but as I doubt that’s in fact possible and fact Boone has said it’s simply meant to impart the status of that given profile field visibility then the change select needs to be removed.
April 18, 2013 at 2:02 pm #162046shanebp
ModeratorRegardless of what it refers to, why would
“This field can be seen by: etc. ” under each Base field on the register page
and a ‘change’ link be visible on a register page to a non-logged-in visitor?That’s what I meant by it failing the bp_current_user_can() check.
April 18, 2013 at 1:50 pm #162044Henry
MemberYep, i see it. According to Boone, it refers to the field value. Slightly misleading text i must admit.
April 18, 2013 at 1:34 pm #162043shanebp
ModeratorDo you see “This field can be seen by: etc. ” under each Base field on the register page?
And a ‘change’ link?Per the image above ?
April 18, 2013 at 12:16 pm #162033Henry
MemberJust 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.
April 18, 2013 at 11:06 am #162027Hugo Ashmore
ParticipantThis rings a bell, think it may have been discussed ( I certainly have a recollection of looking at this aspect of profile visibility and registration processes) before in some respect or another and there may already be a ticket raised.
April 18, 2013 at 7:07 am #162017Henry
MemberThanks for helping test. Bug report here:
April 18, 2013 at 1:53 am #162008shanebp
ModeratorI believe you’ve found a bug.
The Base group allows an admin to set default visibility levels.
I was going to suggest you set each field to “logged-in users” and allow users to change their visibility.But those settings are not honored on the register form.
You can submit a bug here.
https://buddypress.trac.wordpress.org/
Log in with the same user / pw you use for these forums.Also – do you also see “This field can be seen by: etc. ” under each Base field on the register page?
And a ‘change’ link?There is a check in register.php, but it apparently fails by returning true for logged out users.
`if ( bp_current_user_can( ‘bp_xprofile_change_field_visibility’ ) ) `
Like this image taken while logged out on a vanilla install of WP 3.5.1, BP 1.7, 2012 theme
April 17, 2013 at 8:00 pm #161988Renato Alves
ModeratorI’m sorry @jancbeck, I wasn’t understanding what you wanted. Now I do and can’t think of a way, but if I come across of something, make sure I will let you know.
April 17, 2013 at 7:54 pm #161987jancbeck
ParticipantThanks your for your answer. I guess I did not make myself clear enough.
Each user should be able to add as many of these fields as he or she likes. If one had done many jobs in his career one would require a lot of the aforementioned fields. If I’m a young grad student there are probably not gonna be too much. That’s why each user should be able to duplicate the initial field group to have as many as he wants.
I don’t think Buddypress can do this out of the box. I looked at database structure and it seems each user can only have one field assigned to field of a group (1:n relationship).
April 17, 2013 at 4:19 pm #161958Renato Alves
ModeratorYou can add as much as fields as you want. The students would fill them according in their seetings page (here you could change the name for one more appealing) and those fields are searchable by default so you would not have a problem with it.
Bu BuddyPress does all you want out of the box.
April 15, 2013 at 6:11 am #161673In reply to: Terms of Agreement checkbox for registration?
bp-help
Participant@tux-kapono
This can be done out of the box. In the dashboard/users/profile fields create a new profile field under base because this is the fields in registration and under “Is this field required” make it required. In “field type” choose checkboxes. Under “please enter options for this Field:” just leave sort as is and in the text field below it type “I Agree To The Sites Terms Of Service” (This can be what you want really just a suggestion). Under “Default Visibility” check Default value. And That wraps it up really.
@mahdiar
Suggesting as a trac ticket is not necessary. Its already there if you just do the follow the instructions given!April 14, 2013 at 5:42 pm #161628In reply to: Make Profile Name field visible by admin only?
meg@info
ParticipantHi @gsj,
Add this code to functions.php file of the current theme.
`
add_filter(‘bp_xprofile_get_hidden_fields_for_user’,’bp_define_hidden_fields’, 10 ,3 );
function bp_define_hidden_fields( $hidden_fields, $displayed_user_id, $current_user_id ) {
//if not admin or if not the the profile of the current user
if ( !is_super_admin( $current_user_id) && ($displayed_user_id != $current_user_id) ) {
//add name field ( id = 1 ) to the hidden fields
$hidden_fields[] = 1;
}
return $hidden_fields;
}
`April 13, 2013 at 8:07 pm #161566In reply to: Profile Data Deleting
Zachary DuBois
ParticipantI am running WordPress Multisite 3.5.1 in the root directory. When I had everything setup correctly after installing BuddyPress it broke some of the profile fields on some users. I am running BuddyPress 1.7. I have the following latest versions of plugins and none of them from trial and error did anything:
- Bad Behavior
- bbPress
- Blubrry PowerPress
- BuddyPress
- Flowplayer 5 for WordPress
- Jetpack by WordPress.com
- SI CAPTCHA Anti-Spam
- Wordfence Security
- WordPress MU Domain Mapping
- WP Maintenance Mode
I was upgrading from BP Beta 2 and had no problems before. I am hosted on Linode and web server is Apache.
-
AuthorSearch Results

