Search Results for 'profile fields'
-
AuthorSearch Results
-
April 22, 2013 at 3:35 am #162307
In reply to: Profile Data Deleting
Zachary DuBois
ParticipantThis is mainly happening when I put a URL in the text boxes. It will remove the field from the user and it is getting quite annoying. Could someone please help?
EDIT: I just left a whole group blank and clicked save, now the entire group of fields are missing.April 21, 2013 at 11:49 pm #162299In reply to: Avatar upload during registration
missnorthking
ParticipantOption 2 sounds viable, depending on your audience I hear there are “points” type plug ins where members gain points if they do things like upload an avatar, follow you on twitter etc…there is also a plug in I saw that gives a profile completed status type bar, as you complete the different profile fields, the bar fills up…does that make sense?
April 19, 2013 at 7:22 pm #162176modemlooper
ModeratorTo use it elsewhere you would need to get the value of the field and pass it to wp_oembed_get. This is not tested:
$val = bp_member_profile_data('field=youtube'); // in members loop $val = xprofile_get_field_data( 'youtube' , $user_id ); // outside members loop $embed = wp_oembed_get( $val, array( 'width' => 400 ) ); echo $embedIn my previous example I have a provider array. These are the names of your profile fields not the actual service.
April 19, 2013 at 2:08 am #162118operapreneur
ParticipantSorry, I’m going to need a little more guidance. I have more than two fields that need to use the oEmbed. I assumed that the filter you created were for specific field IDs but that doesn’t seem to be the case at all. At this point only one of the fields is embedded the rest are just links.
Also, is this suppose to work with the bp_profile_field_data()? My main purpose on this support thread is to get the profile field to embed outside of the profile page. It’s awesome that it’s embedded in it now but it seems I’m missing something.
Thanks for your help! Looking forward to getting this figured out.
April 19, 2013 at 12:35 am #162112April 18, 2013 at 11:48 pm #162111Renato 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.
-
AuthorSearch Results

