Search Results for 'profile fields'
-
AuthorSearch Results
-
August 31, 2014 at 8:52 am #188803
In reply to: Undisplay some Fields required in Reg.Process
danbp
ParticipantAugust 28, 2014 at 12:26 am #188607In reply to: display email in member directory
rthomasTechnology
ParticipantThat’s not it. I’m in members-loop.php. That (as I understand it) is the file that controls what people see when they go to the default members directory in BuddyPress (the page that shows you everyones icon, their name and when they were last active). I want to add the users email addresses to this screen. At one point I found a line of code and pasted it between:
<div class=”item”>
<div class=”item-title”>
“><?php bp_member_name(); ?><?php if ( bp_get_member_latest_update() ) : ?>
<span class=”update”> <?php bp_displayed_user_email(); ?></span>
<?php endif; ?>
</div>
and
<?php do_action( ‘bp_directory_members_item’ ); ?>
<?php
/***
* If you want to show specific profile fields here you can,
* but it’ll add an extra query for each member in the loop
* (only one regardless of the number of fields you show):
*
* bp_member_profile_data( ‘field=email email’ );
*/?>
</div>which made the email addresses show directly under the names of the site members. I can’t find that code again.
Thanks
RandyAugust 26, 2014 at 1:13 pm #188504In reply to: [Resolved] Nobody visibility
danbp
ParticipantAnother snippet, more accurate with the suggested way above. Snippet goes into bp-custom or functions.php
The field/field group is only shown to site admins. A small bug in the current BP version(.0 -> 2.0.2) prevent of completely remove the group tab from the edit screen. Bug is fixed and this will work with BP 2.1.
function bpfr_hide_profile_field_group( $retval ) { if ( bp_is_active( 'xprofile' ) ) : // hide profile group/field to all except admin if ( !is_super_admin() ) { //exlude fields, separated by comma $retval['exclude_fields'] = '60'; //exlude groups, separated by comma - this may work with BP 2.1 $retval['exclude_groups'] = '7'; } return $retval; endif; } add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_field_group' );August 26, 2014 at 11:44 am #188500In reply to: [Resolved] Nobody visibility
danbp
Participantoh crossposting ! haven’t seen henry’s answer.
nobody visibility doesn’t exist. This setting is called “only me“. This means that only the member can see this field – and the site admins. Such fields are not for site admins, but for the members !
I don’t really understand what is not working for you, as what you’re looking for doesn’t exist in BuddyPress. Sorry if i’m misunderstanding you.
When you create such a field visibility, you should also set “Enforce the default visibility for all members“, so the member cannot modify it later on his profile settings.
Little weird side effect, when a “only me” field is used and member A wrote hello, this word becames clickabke, by default. When member B write also hello, it becames also clickable. And if A or B clcik on Hello, it shows a list of all members who wrote the same word. In this case A and B !
Not really confidential, isn’t it ? The solution is to remove the clickable link.
Here’s a snippet which let you do that selectively.function my_xprofile_filter_link_profile_data( $field_value, $field_type = 'textbox' ) { // Access the field you are going to display value. global $field; // In this array you write the ids of the fields you want to hide the link. $excluded_field_ids = array(2,9,54); // field ID separated by comma // If the id of this $field is in the array, we return the value only and not the link. if (in_array($field->id, $excluded_field_ids)) return $field_value; if ( 'datebox' == $field_type ) return $field_value; if ( !strpos( $field_value, ',' ) && ( count( explode( ' ', $field_value ) ) > 5 ) ) return $field_value; $values = explode( ',', $field_value ); if ( !empty( $values ) ) { foreach ( (array) $values as $value ) { $value = trim( $value ); // If the value is a URL, skip it and just make it clickable. if ( preg_match( '@(https?://([-\w\.]+)+(:\d+)?(/([\w/_\.]*(\?\S+)?)?)?)@', $value ) ) { $new_values[] = make_clickable( $value ); // Is not clickable } else { // More than 5 spaces if ( count( explode( ' ', $value ) ) > 5 ) { $new_values[] = $value; // Less than 5 spaces } else { $search_url = add_query_arg( array( 's' => urlencode( $value ) ), bp_get_members_directory_permalink() ); $new_values[] = '<a href="' . $search_url . '" rel="nofollow">' . $value . '</a>'; } } } $values = implode( ', ', $new_values ); } return $values; } /** * We remove the buddypress filter and add our custom filter. */ function remove_xprofile_links() { // Remove the old filter. remove_filter( 'bp_get_the_profile_field_value', 'xprofile_filter_link_profile_data', 9, 2 ); // Add your custom filter. add_filter( 'bp_get_the_profile_field_value', 'my_xprofile_filter_link_profile_data', 9, 2); } add_action('bp_setup_globals', 'remove_xprofile_links');August 26, 2014 at 11:12 am #188499In reply to: [Resolved] Nobody visibility
Henry Wright
ModeratorI think the field visibility settings are applicable to the member who is performing the setting.
The suggested way to do what you want would be to make your notes profile field hidden to all non-admin members.
The first step would be to create /wp-content/themes/your-theme/buddypress/members/single/profile/edit.php inside your theme.
You can copy the contents of edit.php from:
bp-templates/bp-legacy/buddypress/members/single/profile/edit.php
Then you need to modify edit.php. In edit.php, find
<?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?>and add the following immediately after it:if ( ! current_user_can( 'manage_options' ) && ( bp_get_the_profile_field_name() === 'notes' ) ) continue;Note: I’m assuming your field name is notes
August 24, 2014 at 12:42 pm #188358Jencina
ParticipantSorry, not all is well.
I edit in my custom “register.php” , but I can’t see anything. This is the code of my register custom page:
<?php global $bp; if(empty($bp->signup->step)) $bp->signup->step=’request-details’; ?> <form action="” name=”signup_form” id=”signup_form” class=”standard-form” method=”post” enctype=”multipart/form-data”> <?php if ( 'registration-disabled' == bp_get_current_signup_step() ) : ?> <?php do_action( 'template_notices' ); ?> <?php do_action( 'bp_before_registration_disabled' ); ?> <p><?php _e( 'User registration is currently not allowed.', 'buddypress' ); ?></p> <?php do_action( 'bp_after_registration_disabled' ); ?> <?php endif; // registration-disabled signup setp ?> <?php if ( 'request-details' == bp_get_current_signup_step() ) : ?> <?php do_action( 'template_notices' ); ?> <p><?php _e( 'Registering for this site is easy. Just fill in the fields below, and we\'ll get a new account set up for you in no time.', 'buddypress' ); ?></p> <?php do_action( 'bp_before_account_details_fields' ); ?> <div class="register-section" id="basic-details-section"> <?php /***** Basic Account Details ******/ ?> <h4><?php _e( 'PRUEBA', 'buddypress' ); ?></h4> <label for="signup_username"><?php _e( 'Username', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label> <?php do_action( 'bp_signup_username_errors' ); ?> <input type="text" name="signup_username" id="signup_username" value="<?php bp_signup_username_value(); ?>" /> <label for="signup_email"><?php _e( 'Email Address', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label> <?php do_action( 'bp_signup_email_errors' ); ?> <input type="text" name="signup_email" id="signup_email" value="<?php bp_signup_email_value(); ?>" /> <label for="signup_password"><?php _e( 'Choose a Password', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label> <?php do_action( 'bp_signup_password_errors' ); ?> <input type="password" name="signup_password" id="signup_password" value="" /> <label for="signup_password_confirm"><?php _e( 'Confirm Password', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label> <?php do_action( 'bp_signup_password_confirm_errors' ); ?> <input type="password" name="signup_password_confirm" id="signup_password_confirm" value="" /> <?php do_action( 'bp_account_details_fields' ); ?> </div><!-- #basic-details-section --> <?php do_action( 'bp_after_account_details_fields' ); ?> <?php /***** Extra Profile Details ******/ ?> <?php if ( bp_is_active( 'xprofile' ) ) : ?> <?php do_action( 'bp_before_signup_profile_fields' ); ?> <div class="register-section" id="profile-details-section"> <h4><?php _e( 'Profile Details', 'buddypress' ); ?></h4> <?php /* Use the profile field loop to render input fields for the 'base' profile field group */ ?> <?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?> <?php while ( bp_profile_fields() ) : bp_the_profile_field(); ?> <div class="editfield"> <?php $field_type = bp_xprofile_create_field_type( bp_get_the_profile_field_type() ); $field_type->edit_field_html(); do_action( 'bp_custom_profile_edit_fields_pre_visibility' ); if ( bp_current_user_can( 'bp_xprofile_change_field_visibility' ) ) : ?> <p class="field-visibility-settings-toggle" id="field-visibility-settings-toggle-<?php bp_the_profile_field_id() ?>"> <?php printf( __( 'This field can be seen by: <span class="current-visibility-level">%s</span>', 'buddypress' ), bp_get_the_profile_field_visibility_level_label() ) ?> <a href="#" class="visibility-toggle-link"><?php _ex( 'Change', 'Change profile field visibility level', 'buddypress' ); ?></a> </p> <div class="field-visibility-settings" id="field-visibility-settings-<?php bp_the_profile_field_id() ?>"> <fieldset> <legend><?php _e( 'Who can see this field?', 'buddypress' ) ?></legend> <?php bp_profile_visibility_radio_buttons() ?> </fieldset> <a class="field-visibility-settings-close" href="#"><?php _e( 'Close', 'buddypress' ) ?></a> </div> <?php else : ?> <p class="field-visibility-settings-notoggle" id="field-visibility-settings-toggle-<?php bp_the_profile_field_id() ?>"> <?php printf( __( 'This field can be seen by: <span class="current-visibility-level">%s</span>', 'buddypress' ), bp_get_the_profile_field_visibility_level_label() ) ?> </p> <?php endif ?> <?php do_action( 'bp_custom_profile_edit_fields' ); ?> <p class="description"><?php bp_the_profile_field_description(); ?></p> </div> <?php endwhile; ?> <input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php bp_the_profile_group_field_ids(); ?>" /> <?php endwhile; endif; endif; ?> <?php do_action( 'bp_signup_profile_fields' ); ?> </div><!-- #profile-details-section --> <?php do_action( 'bp_after_signup_profile_fields' ); ?> <?php endif; ?> <?php if ( bp_get_blog_signup_allowed() ) : ?> <?php do_action( 'bp_before_blog_details_fields' ); ?> <?php /***** Blog Creation Details ******/ ?> <div class="register-section" id="blog-details-section"> <h4><?php _e( 'Blog Details', 'buddypress' ); ?></h4> <p><input type="checkbox" name="signup_with_blog" id="signup_with_blog" value="1"<?php if ( (int) bp_get_signup_with_blog_value() ) : ?> checked="checked"<?php endif; ?> /> <?php _e( 'Yes, I\'d like to create a new site', 'buddypress' ); ?></p> <div id="blog-details"<?php if ( (int) bp_get_signup_with_blog_value() ) : ?>class="show"<?php endif; ?>> <label for="signup_blog_url"><?php _e( 'Blog URL', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label> <?php do_action( 'bp_signup_blog_url_errors' ); ?> <?php if ( is_subdomain_install() ) : ?> http:// <input type="text" name="signup_blog_url" id="signup_blog_url" value="<?php bp_signup_blog_url_value(); ?>" /> .<?php bp_blogs_subdomain_base(); ?> <?php else : ?> <?php echo home_url( '/' ); ?> <input type="text" name="signup_blog_url" id="signup_blog_url" value="<?php bp_signup_blog_url_value(); ?>" /> <?php endif; ?> <label for="signup_blog_title"><?php _e( 'Site Title', 'buddypress' ); ?> <?php _e( '(required)', 'buddypress' ); ?></label> <?php do_action( 'bp_signup_blog_title_errors' ); ?> <input type="text" name="signup_blog_title" id="signup_blog_title" value="<?php bp_signup_blog_title_value(); ?>" /> <span class="label"><?php _e( 'I would like my site to appear in search engines, and in public listings around this network.', 'buddypress' ); ?>:</span> <?php do_action( 'bp_signup_blog_privacy_errors' ); ?> <label><input type="radio" name="signup_blog_privacy" id="signup_blog_privacy_public" value="public"<?php if ( 'public' == bp_get_signup_blog_privacy_value() || !bp_get_signup_blog_privacy_value() ) : ?> checked="checked"<?php endif; ?> /> <?php _e( 'Yes', 'buddypress' ); ?></label> <label><input type="radio" name="signup_blog_privacy" id="signup_blog_privacy_private" value="private"<?php if ( 'private' == bp_get_signup_blog_privacy_value() ) : ?> checked="checked"<?php endif; ?> /> <?php _e( 'No', 'buddypress' ); ?></label> <?php do_action( 'bp_blog_details_fields' ); ?> </div> </div><!-- #blog-details-section --> <?php do_action( 'bp_after_blog_details_fields' ); ?> <?php endif; ?> <?php do_action( 'bp_before_registration_submit_buttons' ); ?> <div class="submit"> <input type="submit" name="signup_submit" id="signup_submit" value="<?php esc_attr_e( 'Complete Sign Up', 'buddypress' ); ?>" /> </div> <?php do_action( 'bp_after_registration_submit_buttons' ); ?> <?php wp_nonce_field( 'bp_new_signup' ); ?> <?php endif; // request-details signup step ?> <?php if ( 'completed-confirmation' == bp_get_current_signup_step() ) : ?> <?php do_action( 'template_notices' ); ?> <?php do_action( 'bp_before_registration_confirmed' ); ?> <?php if ( bp_registration_needs_activation() ) : ?> <p><?php _e( 'You have successfully created your account! To begin using this site you will need to activate your account via the email we have just sent to your address.', 'buddypress' ); ?></p> <?php else : ?> <p><?php _e( 'You have successfully created your account! Please log in using the username and password you have just created.', 'buddypress' ); ?></p> <?php endif; ?> <?php do_action( 'bp_after_registration_confirmed' ); ?> <?php endif; // completed-confirmation signup step ?> <?php do_action( 'bp_custom_signup_steps' ); ?> </form> </div> <?php do_action( 'bp_after_register_page' ); ?> </div><!-- #buddypress -->August 24, 2014 at 8:07 am #188351danbp
ParticipantHi @hardeepasrani,
xProfile field manipulation is a such common question on this forum. 🙄 Did you searched before asking ?
But codex first !
Here a topic where you can find how this works and can be done.
https://buddypress.org/support/topic/how-to-add-fields-from-xprofile-fields-groups-created-by-me/August 23, 2014 at 9:07 pm #188338r-a-y
KeymasterYou shouldn’t be loading your field_xprofile_twitter() function on ‘bp_init’. Doing this creates your field on every page load.
Why don’t you just create your field once in the WP admin dashboard under “Users > Profile Fields”?
August 23, 2014 at 12:30 pm #188324Bajdh
ParticipantHi,
Again thanks for your quick reply.
Yes, I used the snippet ‘as is’, and then tried to use the field name instead of the ID.
Field name obviously didn’t work, although you could use it too, according to this page:
https://codex.buddypress.org/getting-started/guides/displaying-extended-profile-fields-on-member-profiles/But I found the profile field ID, and now it works!
Thank you so much :D.
(Yes, KLEO has premium support. But they are very, very slow. I opened a few tickets 1-2 weeks ago, still no replies. Found the answer in the meantime though 😛 ).
August 23, 2014 at 12:16 pm #188323danbp
ParticipantI use the KLEO theme (BuddyPress is integrated), could it be because of that?
Normally, no.But as you use a premium theme, don’t except much help here. You also payed for support. If the snippet doesn’t work for you ( i tested it successfully with Twentythirteen before publishing), you have to get in contact with the theme author or read his doc about customization (if exist).
To get the field ID, see it from where the field is created, in xprofile admin. If you hover the delete button, you can see it at the bottom left corner of your browser.
You can also go into the DB and check for it in the bp_xprofile_fields table.
NOTE:
When you get a snippet, the first thing to do is to use it “as is” to test it – this means also “understanding how it works”, not to apply what you think is better. 🙄And only when the test is ok, you can modify it or try to do so. 😉
August 23, 2014 at 11:48 am #188321Bajdh
ParticipantHey,
Thank you for your quick reply! 🙂
I added the code to my theme’s functions.php, and replaced ’54’ with the name of the field (I can’t find the ID number anywhere), but that specific field still shows up in profiles/edit fields.
I use the KLEO theme (BuddyPress is integrated), could it be because of that?
Or is there a different way to find the field’s ID number? 🙂I really appreciate your help, I didn’t expect such a fast and detailed reply! 😀
August 23, 2014 at 8:49 am #188312danbp
ParticipantHi @ww2boy,
Yes ! 😉 Give this a try. Add it to child theme’s functions.php or bp-custom.php
function bpfr_hide_profile_edit( $retval ) { // remove field from edit tab if( bp_is_profile_edit() ) { $retval['exclude_fields'] = '54'; // ID's separated by comma } // allow field on registration page if ( bp_is_register_page() ) { $retval['include_fields'] = '54'; // ID's separated by comma } // hide the filed on profile view tab if ( $data = bp_get_profile_field_data( 'field=54' ) ) : $retval['exclude_fields'] = '54'; // ID's separated by comma endif; return $retval; } add_filter( 'bp_after_has_profile_parse_args', 'bpfr_hide_profile_edit' );Codex reference:
https://codex.buddypress.org/plugindev/using-bp_parse_args-to-filter-buddypress-template-loops/August 22, 2014 at 2:31 pm #188267In reply to: using placeholder attribute instead of label
mmadden
ParticipantYes, I’ve already edited the input fields within the basic-details-section div. I want to edit the input field in the profile-details-section div to match, but there is no input field in the register.php for that section. Instead there’s this:
<div class="register-section" id="profile-details-section"> <h4><?php _e( 'Profile Details', 'buddypress' ); ?></h4> <?php /* Use the profile field loop to render input fields for the 'base' profile field group */ ?> <?php if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>Is there any way to get at the input tag that gets output to the profile-details-section?
August 22, 2014 at 7:30 am #188236In reply to: Xprofile fields – Per Member Visibility
danbp
Participantyou will find some usefull posts about this on the codex.
Add custom filters to loops and enjoy them within your plugin
https://codex.buddypress.org/plugindev/playing-with-the-users-id-in-different-contexts/
https://codex.buddypress.org/plugindev/using-bp_parse_args-to-filter-buddypress-template-loops/Searching on the forum can also help.
https://buddypress.org/support/search/xprofile+conditionnal+fields/August 21, 2014 at 9:09 pm #187770In reply to: using placeholder attribute instead of label
danbp
ParticipantHi @mmadden,
not sure i understand what you want to achieve. Are you creating a register page from scratch ?
Anyway….
Open the original BP register file (/buddypress/bp-templates/bp-legacy/buddypress/members/register.php). It contains many placeholders and conditionnalsSo, for the mandatory NAME xprofile group (the only one you use), you have line 65
if ( bp_is_active( 'xprofile' ) ) : if ( bp_has_profile( array( 'profile_group_id' => 1, 'fetch_field_data' => false ) ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); --- blah---Line 75 sit this placeholder
do_action( 'bp_custom_profile_edit_fields_pre_visibility' );where you can hook your additionnal information.Line 98 there’s another one:
do_action( 'bp_custom_profile_edit_fields' );just above this function:<p class="description"><?php bp_the_profile_field_description(); ?></p>In register.php, the section you speak about goes from line 50 to 112
From/***** Extra Profile Details ******/to</div><!-- #profile-details-section -->Of course, you can also add your own placeholder to your register template.
Sorry if i’m wrong.
August 21, 2014 at 3:02 pm #187708aces
ParticipantUsing firefox on http://animalsfunnypictures.com/members/sanaa/ I can see
entry-content img {which has awidth: 510pxif i disable it in firefox it becomes the ‘normal’ size.This is coming from Marla theme’s style.css on line 1464 – see for yourself…
August 19, 2014 at 8:01 am #187192Saurabh Jain
ParticipantThanks @1a-spielwiese,
Is there any way to search users using xprofile fields.
E.g. In my xprofile field i have named “Skills” i want to search all user having the Skill = I.T.
I made Skills as checkbox.August 19, 2014 at 4:31 am #187185Saurabh Jain
ParticipantThanks @1a-spielwiese and @danbp,
I created new fields and didn’t updated profile that was the reason of not showing.Is there any way i can access the data in the fields. I created field named Skill i want to access the data in that field and use in other pages/post.
August 18, 2014 at 9:35 pm #187166mrapino
ParticipantOkay, this is my first piece: http://pastebin.com/pyz8XaaP
This first link is some code findings that might continue the conversation toward an elegant solution.
And then I came up with another possible solution here, which is actually partially working, but might be a bit clunky: http://pastebin.com/3JBCuZrx
Basically, the first link is not working, but may give us more food for thought. The second link is working, but there are a few caveats. What I am doing in the second link is finding out what user role the logged in user is attached to. Then I create a conditional that states that if the user is under a certain role, it hides the profile group tabs from being seen, which essentially prevent them from adding content to them, and if there is no content for any of the fields in the group, it won’t show on the front end.
CAVEAT: if you go directly to the profile group URL, you can still edit. I need to figure out how to actually prevent the URL from working, as opposed to/ or in addition to hiding it.
Either way, I think there’s a bunch of good stuff to talk about here.
Let me know what you think.
NOTE: I am using some code found on this post:
https://buddypress.org/support/topic/conditional-exclusion-of-a-xprofile-fields-group-from-editing/August 18, 2014 at 4:58 pm #187141mrapino
ParticipantThanks for the links.
Defining a role doesn’t necessarily require previous input from the people using your site … you simply define the roles of your users based on what you want those users to be. Custom user roles allow you to have more granular control over what your users can do and see when registered on your site. Regarding Buddypress … I think that having a way to pre-define user types/roles and assigning custom profiles to those various user types is something to be desired.
I am using Gravity Forms to create a custom registration form that allows a registrant to pick the type of user they are and when the user type is chosen, I am conditionally displaying custom fields that are associated to the specific user type.
The problem is that after the user registers, and the fields are filled out, if they go to their profile to edit the information, they see ALL FIELDS regardless of the user role they chose during registration. The reason is that although Gravity Forms allows you to map certain fields on the form to profile fields in Buddypress, you still have to edit Buddypress to HIDE the fields you don’t want those users to see.
That is why I am posting this question … I am trying to get code together to alter the profile section of Buddypress to allow you to associate specific profile fields to a user role, so when the user of a specific role finally goes to their profile to make edits, they do see, and are not allowed to edit fields that are not associated to their specific role.
IMHO this type of control is very useful, as it can help you create some fairly interesting communities.
Thanks for your assistance. I hope I have clarified things further for you. If anyone can help, great … if not, I am still moving forward on this and when I come up with a solution, I will post it here. If anyone can help me get to that solution faster, I’d be very appreciative. If not, I hope I can help those of you who are looking for the same results.
August 18, 2014 at 4:14 pm #187138mrapino
ParticipantI appreciate your response! I will take a look at this plugin. I am always hesitant to use plugins that are so out of date, but perhaps there is some code within the plugin files that will be useful.
Also, is there any resource that details the functions available within Buddypress. I have looked at the Codex, but I can’t seem to find a nice definitive resource. The WP Codex has all of the actions, filters, functions, etc… I was trying to find something similar within the Buddypress website, but can’t seem to find documentation that has everything detailed out. Is there a lot of documentation that hasn’t been written yet, or am I just looking in the wrong place?
Please keep me posted if you have any other suggestions about what functions, or code snippets I might use to gather the correct information to alter the profile section based on user roles.
Basically, I need to know where you might place the custom code (is it within the bp_custom file?) And if I use bp_custom, I am guessing I would have to hook my code into the correct location, so Buddypress knows to enact my code correctly (Is there an action hook that hooks into the Profile section specifically?) I also would need to know where to find the functions I need to edit the profile section (all xprofile functions, any functions that might help me attach user roles to profile fields, any functions that pull data relevant to the connection between profiles and users, etc…)
Regarding the connection between user/user role and profile, would I be calling these functions separately … meaning, would I first use a conditional to see what user role the user is, and then within that conditional be using general xprofile functions to display only the fields I want to display for the user role that the conditional is specifying?
I think if we all start to spitball ideas, this post can be a sounding board for the code that can build this functionality out. In my research over the past week, I have found so many incomplete conversations about how to make this functionality a reality. So, I know there are many people looking to do exactly what I am attempting. And the beauty is that we all have bits and pieces of this idea and how it might fit together. Perhaps we can all start posting our code snippets here to build this out together?
If we can make it work, I bet this post can be the beginning of a core Buddypress code update that can integrate this into the actual Buddypress Core.
What do you all think?
I’ll be continuing my research and posting my findings here. Let’s make this happen!
August 18, 2014 at 10:40 am #1871181a-spielwiese
ParticipantDo you have inserted text (information) into the fields and profiles at issue?
If you have old profiles and create later new fields, this fields are of course empty. So you have to update the profile information at first.
August 18, 2014 at 2:29 am #187103In reply to: Add profile field to 'Order By' drop down menu
danbp
Participantdid you noticed that profile field datas are clickable ?
This default behaviour is intended to be use as a filter.Member A filled the Contractor field
If any visitor goes to member’s A profile and click on the Contractor field value, BP will show a list of all other members who also filled in this field.So what you want to get already exist !
August 16, 2014 at 11:46 pm #187041danbp
ParticipantWould it matter that I have my group_order (i.e., the order in which my field groups are displayed) arranged in a specific order?
No !
Anyway, i was wrong myself. Apologize. My snippet hides groups from viewing, not from editing. But you can get another trick on this post. And this one works realy. 😉August 16, 2014 at 10:29 pm #187039In reply to: [Resolved] No button for finishing registration
1a-spielwiese
Participant“remove all xprofile fields to get only the default name field.”
When I posted the comment:
https://buddypress.org/support/topic/no-button-for-finishing-registration/#post-187032
non xprofile field was created.
“Also download a fresh copy of wordpress and upload the twenty twelve theme folder to your site. Maybe your’s is corrupted somewhere.”
That’s really unlikely, because both copies worked without problems, before I installed the BuddyPress-Plugin. And I tried never to make any major change of twenty twelve theme or WordPress itself.
-
AuthorSearch Results