Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'profile fields'

Viewing 25 results - 3,501 through 3,525 (of 3,892 total)
  • Author
    Search Results
  • #56895
    shane54
    Participant

    I installed WPMU and buddypress and all work great but blogs subdomains dont work – blank page

    My Apache error:

    [Tue Nov 17 21:21:52 2009] [error] [client 83.16.234.122] WordPress database error Table ‘aa11935_pozy.wp_bp_xprofile_data’ doesn’t exist for query SELECT * FROM wp_bp_xprofile_data WHERE field_id = 1 AND user_id = 1 made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, bp_core_setup_globals, bp_core_get_user_displayname, xprofile_get_field_data, BP_XProfile_ProfileData->get_value_byid, referer: http://trzebiatow.eu/wp-admin/plugins.php

    [Tue Nov 17 21:21:52 2009] [error] [client 83.16.234.122] WordPress database error Table ‘aa11935_pozy.wp_bp_xprofile_fields’ doesn’t exist for query SELECT id FROM wp_bp_xprofile_fields WHERE id = 1 made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, bp_core_setup_globals, bp_core_get_user_displayname, xprofile_set_field_data, BP_XProfile_ProfileData->save, BP_XProfile_ProfileData->is_valid_field, referer: http://trzebiatow.eu/wp-admin/plugins.php

    [Tue Nov 17 21:21:52 2009] [error] [client 83.16.234.122] WordPress database error Table ‘aa11935_pozy.wp_bp_groups’ doesn’t exist for query SELECT id FROM wp_bp_groups WHERE slug = ‘plugins.php’ made by require_once, require_once, require_once, require_once, do_action, call_user_func_array, groups_setup_nav, BP_Groups_Group->group_exists, referer: http://trzebiatow.eu/wp-admin/plugins.php

    can you help me? whats wrong… install was OK

    #56867
    Brajesh Singh
    Participant

    hi Phillip

    Yes yo can.

    By default your registration page will show only the fields from first profile field group.

    You can change it.

    You will have to edit registration/register.php

    Look for the code

    bp_has_profile( 'profile_group_id=1' )

    and replace it with

    bp_has_profile( )

    Now your register page will show all the fields.

    But stop,This is not enough,you need to aggregate all the field ids and put it as hidden field.

    So Take a look at the the line

    <input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php bp_the_profile_group_field_ids() ?>" />

    remove it from the profile loop.Now create some code inside the profile loop,aggregate all profile ids and then

    put this code outside the profile group loop,

    where I ssume you have aggregated all profile fields in the variable $all_pf_fields.

    <input type="hidden" name="signup_profile_field_ids" id="signup_profile_field_ids" value="<?php echo $all_pf_fields;?>" />

    Please note,all $all_pf_fields should be the comma separated list of all profile ids(say 1,2,3,)

    This will make it work,and your registration page will show all profile groups fields

    #56866
    Simon Dabkowski
    Participant

    Each field group has an ID value. You can modify the registration.php file to include additional groups by repeating the following and changing “1” to “2”:

    <?php if ( function_exists( ‘bp_has_profile’ ) ) : if ( bp_has_profile( ‘profile_group_id=1’ ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

    to

    <?php if ( function_exists( ‘bp_has_profile’ ) ) : if ( bp_has_profile( ‘profile_group_id=2’ ) ) : while ( bp_profile_groups() ) : bp_the_profile_group(); ?>

    #56859
    Philipp
    Participant

    Hi!

    It’s me again. After many hours thinking how to handle my problem I have an idear which could help.

    But for this I also need your help and your opinion… ;)

    I would like to add two profile fields which the user has to answer at the registration:

    1.) In which Month do you go abroad? “March 2010”, “September 2010”,…

    2.) How long are you going to stay abroad? “6 months” or “12 months”

    After that I would need a Widget or Plugin, that the Visitors can search for people who are abroad at the moment or search for those, who left in “March 2010”,…

    Do you think, that this could be possible?

    Now I added these profile fields into buddypress. But there are more than 200 members at the moment. Do I have to go to every profile to change the answer in “September 2009” or is it possible to do it automaticly? E.g. with phpmyadmin? It is saved in the table “wp_bp_xprofile_data” with the field_ID “266”. And I know, that every user how is registred yet went abroad in September 2009.

    The next point ist the question, weather there is a plugin that searches for deathly users who didn’t login or didn’t write a post e.g. 6 months. So I could delete them.

    So. Thats my long, long plan. But if you have a better Idear – Please let me know. Or if not, PLEASE help me how to realize this!

    Thanks so much and many greatings from Jerusalem!

    Philipp

    #56853

    In reply to: BP Member Filter

    Jean-Pierre Michaud
    Participant

    i installed it… and it is the best example possible for the suggestion i made for a /bp-plugins/ directory… we can not actually install this plugin on the fly with the installer, we need to move files around. we also have to replace two files… that could be a problem if we have another product that need to overwrite these 2 files again. (adding actions into these files is needed though)

    suggestion:

    bp-profile-setup : when we setup some custom field, would be good to have a checkbox “is searchable”… so we can filter or search thru these fields only when possible. this could be good if we want to avoid some details to be trackable…

    #56644

    In reply to: BP Member Filter

    Jean-Pierre Michaud
    Participant

    suggestion: popular keywords. similar to auto-tags based on post content, would be amazing for big sites to have the same for profile fields, so we have a cloud (or a dropdown) of popular profile field answers.

    challenging i suppose.. lol

    #56613

    In reply to: BP Member Filter

    Xevo
    Participant

    I believe the xprofile fields are the fields like “name”, so basically your users their account details.

    I like the fact that you can order your users like this, A to Z is kinda… lame and outdated. I’ll definately try this out later. Thanks JJJ.

    Edit: JJJ was 51 seconds faster then me. :)

    #56612

    In reply to: BP Member Filter

    Extended Profile – Basically the profile fields you setup for your audience

    An example would be here at buddypress.org, if you wanted to search for people who put “puppies” in their interests field. Rather than searching for puppies and possibly getting someone with the name “I Love Puppies” it will isolate your search down to the field you’re searching in.

    Clear as mud? Haha

    #56611

    In reply to: BP Member Filter

    stwc
    Participant

    I want to thank you for this, but I don’t even know what ‘xprofile fields’ refers to! ;-)

    Jeff Sayre
    Participant

    This is a free, open source project primarily powered by volunteers’ efforts. So don’t expect to get instant results.

    As r-a-y has stated, there used to be several pre-built fields and site developers also had the option to create their own pre-built fields by importing their list via a .cvs file. But, as Andy states in this thread, that feature is no longer available:

    https://buddypress.org/forums/topic/making-prebuilt-profile-fields

    So, you either have to code a solution yourself or hire a developer to do it.

    By the way, up until two-weeks ago, there was only one official BuddyPress developer. Now there are two. The rest of us are unpaid volunteers–some of us with coding experience, some of us with design experience, and some of us just interested in running social networking sites.

    You can ask for additonal insights on the #buddypress-dev IRC channel. But even there, it is simply a group of developers with their own projects and responsibilities. Only Andy and jjj are the official voices of BuddyPress development.

    #56118

    In reply to: X-Profile Fields

    r-a-y
    Keymaster

    I don’t see this as well in BP 1.1+.

    This was extremely useful!

    But, I’m guessing if you already have these profile fields setup when you upgrade, these fields should still exist.

    It’s only if you decide to create new x-profile fields that you won’t be able to use the CSV option.

    EDIT: Added an enhancement ticket in Trac:

    https://trac.buddypress.org/ticket/1327

    #56042

    In reply to: html in profile fields

    philbow
    Participant

    DJPaul,

    Yes it was wrapped, and no line breaks/whitespace.

    Thanks,

    Phil

    #56004

    In reply to: html in profile fields

    Paul Wong-Gibbs
    Keymaster

    I assume you’ve wrapped your code in <?php ?> brackets?

    Also, check you haven’t got any linebreaks or white spaces anywhere.

    #55992

    In reply to: html in profile fields

    philbow
    Participant

    I am putting it into bp-custom.php per the thread referenced. The error is that it can’t pass the headers because it already did.

    Thanks,

    Phil

    #55915
    peterverkooijen
    Participant

    Excellent, that works very nicely. Thanks John James Jacoby!

    Could something like this become part of the core? When you have the name of a member, it should be easy to add associated data. This function makes it a lot easier.

    Edit: The function probably needs to be expanded a bit. I get these slashes (escapes?) in the output:

    Pandora's Box

    I’ll look into that when I have time…

    #55905

    Within the members loop, the problem is that you’re not feeding it any user_id to get the data for… Like I said above, without a user_id, it’s just looking for the $bp->displayed_user->id, which doesn’t exist because when you’re on a directory page, there is no displaued_user->id; you’re not looking at a member…

    Within any member related loop, you will need to make a custom function for that loop and use the user_id available to you to spit out what you need…

    Put this in your bp-custom.php… (haven’t tested this, wrote freehand, lookout for bugs)

    function bp_custom_member_list_xprofile_data( $field ) {
    echo bp_custom_get_member_list_xprofile_data( $field );
    }
    function bp_custom_get_member_list_xprofile_data( $field ) {
    global $site_members_template;

    return xprofile_get_field_data( $field, $site_members_template->member->id );
    }

    Then use it like this on fields that need checking…

    <?php if ( $company = bp_custom_get_member_list_xprofile_data('Company') ) : ?>
    <p><?php echo $company ?></p>
    <?php endif; ?>

    …or like this on fields that don’t…

    <p><?php bp_custom_member_list_xprofile_data('Company') ?></p>

    #55904
    peterverkooijen
    Participant

    Thanks for the additional information. I’ve tried this in members-loop:

    <?php if ( $company = xprofile_get_field_data('Company') ) : ?>
    <p><?php echo $company ?></p>
    <?php endif; ?>

    and this

    <p><?php echo xprofile_get_field_data('Company'); ?></p>

    Still get nothing with either version…

    The search actually searches all fields of the user/group/blog, and returns anything that is relevant to that item. So if any of my xprofile_field’s have a “k” in it somewhere, it will return me. So in theory, it doesn’t suck yet, it just hasn’t been narrowed down. It’s a blank slate and a starting point to building a better search. Search functions also greatly depend on the goal of the website and what results you’re trying to pull out.

    WPMU Sitewide Search plugins currently aren’t for the faint of heart. They take all of your posts/tags/categories for all blogs, lump them into new additional full text database tables, and search those instead. It’s the only real way to do it without a million joins that just wouldn’t make any sense… Problem is you’re duplicating your data twice over into 1 mega huge table, and rebuilding the search index for old posts on a larger website would be an astronomical task that would take days of processing.

    @erich73, those are good recommendations for the directories. Put them in a trac ticket as an enhancement for maybe 1.3?

    #55901

    In reply to: html in profile fields

    What error does it generate? The code looks fine. Where are you putting it. The only thing I can think is that it’s running before the filter is added somehow.

    #55897

    I recommend using the field name, just because it’s easier to keep track of…

    Example…

    <?php if ( $firstname = xprofile_get_field_data('First Name') ) : ?>
    <h3><?php _e('First Name', 'your-theme-textdomain') ?></h3>
    <div class="profile-data-field">
    <?php echo $firstname ?>
    </div>
    <?php endif; ?>

    …will get you the data from the field named “First Name” for the currently displayed user. If there is no user displayed (your account or anyone else’s), it will return false.

    #55887
    peterverkooijen
    Participant

    Doesn’t work for me. Field id ‘2’ is supposed to be company name in my installation, but this in the members_loop.php only displays name and last active:

    <h3><a href="<?php bp_the_site_member_link() ?>"><?php bp_the_site_member_name() ?></a></h3>
    <p><?php do_action( 'bp_core_directory_members_content' ) ?></p>
    <p><?php echo xprofile_get_field_data('2'); ?></p>
    <label><?php bp_the_site_member_last_active() ?></label>

    Should I use bp_the_site_member_something(‘2’)?

    #55852
    buzz2050
    Participant

    Hi again,

    Well, now I have a fresh install of both WPMU(2.8.5.2) and BP(1.1.2) on my localhost. I do not have any other plugins apart from BP installed and still the same problem.

    I have added some ‘required’ custom fields to the ‘Base’ Profile Group. Even though the user fills them during the registration, they still appear blank on the ‘Edit Profile’ page (in BP members) and he has to fill them again (editing and saving works).

    I have the same install on my server, but there I upgraded from earlier versions and apparently, this problem does not occur there. Not sure what’s going on??!

    Please HEELLP!!

    -Sib.

    #55665
    peterverkooijen
    Participant

    @Chouf1, the code is not for uppercasing; it’s making sure firstname and lastname are stored consistently in the different places where WP/WPMU/BP stores names.

    Why is it too much to ask for consistently, reliably stored firstname + lastname in the WordPress world? Uppercasing should be part that imho. It’s utterly ridiculous to have to do that in CSS. Is that even official CSS? Do all browsers support it?

    In most software for grownups firstname and lastname fields are at the top of the members/users table, part of the core of the application, the heart of member registration and management. In the WP/WPMU/BP world it’s a messy afterthought, stored halfheartedly in three or four different locations, in different ways, without any synchronization between them. Aaarrrggghhh.

    Before a WordPress user account is activated, it is stored in the wp_signups table; there’s a meta field storing various things. Have you checked if its that one?

    That’s one of the two places where the lowercase version of the name is stored. My code above updates names with uppercase in the usermeta fields.

    My question is which code stores them in xprofile or wp_signups. Where should I apply my nameize() function to get clean names in xprofile?

    Cleaning them up before they’re stored in wp_signups would do the trick as well, because I think the xprofile data is taken from there. I don’t think the wp_signup data is used for anything else later, so it has a lower priority to me.

    Edit: Of course I’m not trying to uppercase all chars of the name, just the first ones, as used to be custom in western culture. FYI, here’s the nameize function I use:

    function nameize($str,$a_char = array("'","-"," ")){
    //$str contains the complete raw name string
    //$a_char is an array containing the characters we use as separators for capitalization. If you don't pass anything, there are three in there as default.
    $string = strtolower($str);
    foreach ($a_char as $temp){
    $pos = strpos($string,$temp);
    if ($pos){
    //we are in the loop because we found one of the special characters in the array, so lets split it up into chunks and capitalize each one.
    $mend = '';
    $a_split = explode($temp,$string);
    foreach ($a_split as $temp2){
    //capitalize each portion of the string which was separated at a special character
    $mend .= ucfirst($temp2).$temp;
    }
    $string = substr($mend,0,-1);
    }
    }
    return ucfirst($string);
    }

    Edit2: The CSS solution only works on the first name. The last name still starts with lowercase. Any easy CSS trick for that? I don’t think so.

    Apparently the same CSS trick is used in this forum, which would explain why my “username” – cough, spit – is displayed as ‘Peterverkooijen’ instead of ‘peterverkooijen’ as I had entered it. Why is that kind of mess considered acceptable?

    #55510
    buzz2050
    Participant

    Thanks for your reply Jeff. I understand that the register.php directly contains all the elements now.

    However, we liked the registration page of the default ‘bphome’ theme (BP 1.0.3) better (earlier) and accordingly we customized our site theme(premium edu-clean home theme for WPMU) to have a register page like that.

    To achieve this, I created a custom page template register.php with code similar to that of bphome’s and plonked it in my theme folder. There if you see, the page template is divided into right-column, center-column, left-column (it hosts the registration section)

    The code for this register.php is something like:

    <?php get_header(); ?>

    <!-- div content starts -->
    <div id="content" class="widecolumn">
    ....
    ....

    <div id="left-column">
    <div class="register bp_core_widget_welcome">
    <h2 class="widgettitle"><?php _e( 'Register for an Account', 'buddypress' ) ?></h2>
    <?php bp_core_signup_do_signup() ?>
    </div>
    </div>

    </div><!-- div content ends -->
    <?php get_footer(); ?>

    It’s the bp_core_signup_do_signup() that is responsible for including the content of the registration page in the left-column.

    Here is how my current registration page looks like:

    http://www.cmswebusa.com/testsib/reg_pg.png

    The registration section on the left is included in that section due to the bp_core_signup_do_signup() call. We still haven’t converted to the new single theme way, but we have already upgraded our BP to 1.1.2 and since then our custom fields just don’t get saved. Not sure what to do here?! I was wondering this could be happening coz of the deprecated function call. Also, how do I still make the registration section appear in the left-column of my page? Is there a function to include the register template or something?

    Thanks,

    Sib

    #55467
    buzz2050
    Participant

    @DJPaul

    Earlier when we were using WPMU 2.8.4a with BP 1.1, our registration form worked fine and all the custom fields got saved just fine. Only after the upgrades, are we experiencing this issue. Did not touch the WPMU install, just upgraded BP, that’s it!

    However, we do have a custom registration page which is different than wp-signup.php. On this page we are calling bp_core_signup_do_signup() which is deprecated in BP1.1.2. Could that possibly be creating the issue? Is there any alternative to this call in the newer version?

    We really need to fix this asap, users are already grumbling. Any troubleshooting advice is greatly appreciated.

    Thanks,

    Sib

Viewing 25 results - 3,501 through 3,525 (of 3,892 total)
Skip to toolbar