Skip to:
Content
Pages
Categories
Search
Top
Bottom

Search Results for 'forum'

Viewing 25 results - 16,301 through 16,325 (of 20,258 total)
  • Author
    Search Results
  • #60038
    Xevo
    Participant

    It’s probably a glitch, and a bad one. Try re-installing and make sure you have sub directories selected when installing. If it goes back to subdomains again, try checking for any errors in logs or on the page itself.

    If all else fails, go to the wpmu forums, and ask your question there.

    #60020
    21cdb
    Participant

    I never use the search function on BP. It’s a pitty, but it doesn’t motivate when you have to specify so many different types of possibilities.

    I also read the comment in function bp_search_form_type_select() and i would love if this could be implemented in BP.

    I’m pretty much in love with buddypress exept how forums work (see here: http://testbp.org/members/toreg/activity/58328/ ) and how activities and so discussions slowly get lost on the screen (see here: http://testbp.org/members/toreg/activity/58411/).

    Hastags would be also a great addition to get people to what is “in” at the moment.


    @username
    is great too … but BP shows the fullname and average user will never be patient enough to look up the username on the profile URL.

    Note this is all constructive criticism – i love what you guys have done so far!! Great work, especially the new theme and the improved activity stream!

    #59991
    peterverkooijen
    Participant

    You can make pages in the regular WordPress part. And maybe this is helpful.

    #59990
    Boone Gorges
    Keymaster

    Andy, I see that you’ve commented in bp_search_form_type_select() (bp-core/bp-core-templatetags.php) that eventually there’ll be a single search page to bring together all content types. Am I right that it doesn’t exist yet? If not, where do you think hashtag search links should link, since all search is specific either to groups or forums or members or blogs?

    #59976
    Paul Wong-Gibbs
    Keymaster
    #59972
    stwc
    Participant

    20,000-foot thought here, but possibly germane.

    I’ve been thinking as I’ve gotten from ankles- to knees- to nipples-deep in Buddypress is that there may be a little fuzziness conceptually (or perhaps it’s just my own lack of understanding and need to hammer things down, mentally) around some stuff at the highest level as BP has evolved.

    What I mean is something like this: forums and groups seem commingled in a way that is pretty darned counterintuitive, I think, for most users accustomed to traditional forums structure or to social networky ways of doing things. This is not entirely to the bad — I’m not suggesting that — but I think it confuses people who are not ‘techy’. This initial confuzzlement means a lot of people give up without trying to figure out the Buddypress Way, which is a Bad Thing. For my part, as someone who’s highly technical and been working on and off in designing user experience stuff for decades, even me, if a site doesn’t present its ‘expected’ interaction mode after a few seconds, I’ll probably give up and go elsewhere. Little things like a lack of an easily found search box will have me closing a site tab, my patience level is so low — I think that ordinary users tend to be a little lost in the groups/forums melange of Buddypress, sensible as it may seem to those of us who are building the sites, and just give up and go back their Facespaces and Mybooks.

    Part of the issue I’m describing badly probably comes from the bolt-on and eventually plugged-in nature of BBpress as part of Buddypress, but I also think it might have been a bit of a result of not starting from top down, boring old use-casey thinking. I could be wrong there, of course, it could just be me, and no offense to Andy or anyone else meant by saying it. It just seems a little… wrong to me, a bit, thinking as a user.

    So, finally, about this latest idea and thread: there seems to me, as part of the shift in 1.3, to be a changing conceptual focus. That is, we are directing the focus of users from other individuals, other users on the site (as ‘objects’), to the activity of those individuals, as the engine of interaction, if you will. ‘Following’ activity and so on. Now there’s nothing wrong with that, and I actually feel it’s a very good idea, because engaging users and keeping them actively using a site and interacting with others is what it’s all about, and Facebook, like it or love it, understands that perfectly.

    But there are downstream consequences of activity (actions) being the focus of site use as opposed to, for lack of a better word, objects (people, groups).

    I’d just like to hold up a hand and say that considering what those consequences might be is a wise thing, I think, if only to avoid a kind of frankenstein’s monster situation, with different conceptual drivers for user engagement ruling over different parts of the app, and further stirring up cognitive dissonance in already-possibly-bewildered users.

    OK, that’s enough words now. ;-)

    #59968

    I deeply apologize if my previous post is a spam.

    I only followed BuddyPress Documentation in Improving Performance, and showed how it works with my websites.

    I found that the article is very-very useful (for server’s performance and users’ access). So, I want to share my experience in this forum to other BuddyPress lovers.

    Please forgive me if my previous post is a spam. Do I have to delete it?

    #59964
    designodyssey
    Participant

    I’m very late to this party, but since I’ll be developing when 1.3 comes out, here’s my two pennies.

    I believe the modularity and CMS capabilities of WP/BP should be expanded. I think we need the ability to create different “content types,” “user types”. Groups could essentially be a user type. Users are a user type. Tournaments, Classrooms, Camping Trips could all be user types. Differentiation is based on functionality and capabilities. I’d like to see a single API work with user types as I hope WP is moving toward for content types.

    Let me decide what a friend can do just as a group. Because “groups” can have multiple distinct members, they require a bit more thought, but other than that it should be the same.

    BTW, I would never want users to have their own individual forum, but someone else might and that’s the point.

    #59949
    Anton
    Participant

    This is quite a big problem. I deleted a user account but it didn’t delete the forum posts the user made. It only deletes his name in the feed but the content of the topic is still on the forum for the specific group. Now if it was a spammer(s) you would have to filter through all the groups/forums that they created and replied on topics and delete them. This will be quite tedious as you can’t search for the user in the database and delete all the topics related to that user because his name is deleted but not the content. You would have to manually filter through everything and I don’t think it will work.

    John James Jacoby – You mentioned

    “Which version of BP? This will be fixed in 1.2 as I think it’s just a missing or incorrectly named action. “

    Where is this action so that I can insert it into my BP 1.1.3 installation? Is it simple?

    Boone Gorges
    Keymaster

    I’m not sure how those plugins in particular work, but here’s a solution that worked for me with the plugin More Privacy Options: https://buddypress.org/forums/topic/more-privacy-options-private-blogs-and-activity-streams

    The same principle can probably be applied to your case. Figure out how your plugins are recording fine-grained privacy options, and then adjust the code at the above link to match.

    #59942
    juandrah
    Participant

    Why not check the WP forum?

    So if I install WPMU, then Buddypress, then the On Demand theme, my site members will each have their own video gallery blog, be able to view other members video blogs, and with a little tweaking the main page can be a video gallery of all videos posted by all members (or rather maybe show the most recent postings)?

    #59931

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    #59928

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    #59927

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    Now is up to 3-times-faster because I have installed this jazz thing modified by Donncha. A salute thanks to this jazz person.

    Please feel the different here

    #59922
    peterverkooijen
    Participant

    This is my pet peeve with Buddypress! Wasted at least two weeks on this issue last Summer.

    I use the same Beau Lebens email as login plugin that David Lewis found. So I wanted to get rid of username entirely and have basically only real name and email address on my registration form.

    To integrate a mailinglist script I needed separate firstname + lastname. Buddypress doesn’t store them out-of-the-box. This is NOT a WPMU issue; WP/WPMU has firstname + lastname in wp_usermeta, but Buddypress simply refuses to synchronize those fields, so you can’t count on the data being there for other scripts (mailinglist, events, etc.).

    Here’s my solution:

    How to synchronize firstname+lastname between xprofile field_1 and wp_usermeta upon registration

    And

    How to autogenerate blogname (url) from Blog Title (or username from fullname!)

    The Javascript I use for fullname->username looks like this

    function copyinputuser()
    {
    var tmp = document.getElementById('field_1').value;
    tmp = tmp.toLowerCase().replace(/^s+|s+$/g, "").replace(/[_|s]+/g, "");
    tmp = tmp.replace(/[^a-z0-9-]+/g, "").replace(/[-]+/g, "").replace(/^-+|-+$/g, "");
    document.getElementById('signup_username').value = tmp;
    }

    Unfortunately a lot of people sign up with only one name in the Fullname (field_1) field. Question:

    Would anyone know how to validate/check the input for a two-part (minimum) name? You’d probably have to check for a space, make a space required. How would that script look?

    No firstname/lastname because this does not work for a lot of international users.

    Which countries are you talking about?! Name them.

    With all due respect, this is such a bizarre argument. Not only the western world, but India, China, etc. all have no problem whatsoever using two or more names. Countries that use only one name or more than four can write their own plugins, along with the language pack etc.

    More than two names is no problem; separating first and last name is primarily about having a first name available. Users can put their other two, three, four names in the second field.

    If Facebook, LinkedIn, etc. have no problem requiring separate firstname and lastname, why is this such a controversial issue for Buddypress? Why make life difficult for 80-90 percent of Buddypress users just to prevent offense to 10 percent with different customs?

    #59919
    Henry
    Participant

    How do you delete a forum topic – any way besides accessing the database?

    edit: (nevermind, found it)

    #59904
    peterverkooijen
    Participant

    I can see how it might be good tokeep friending, but give the option not to use it. I hate it when Ning takes away features …

    Just in general I don’t like the idea of any features being taken away …

    If friending gets taken out in 1.3, then I’ll stay with Buddypress 1.2 …

    We should be thinking about extending the BuddyPress framework and not deprecating major components at this time …

    Not sure why JJJ wants to remove the “friending feature” in favour of the “following-feature”? Can we not have both ? …

    I am worried Buddypress will fall into the trap of trying to be everything to all people and will become a bloated mess. For my projects I need a coherent, reliable core before I need any more features – forums, events, galleries, enterprise features, ecommerce, …

    It’s great the developers are rethinking friending, how it can make more sense in the Buddypress context. If Buddypress can come up with a different approach, logically tied into groups and (micro)blogging, that could really set BP apart from Facebook, Ning, etc. Less is more!

    JJJ’s proposal already is the best of both world imho (yes, we can have both!):

    1. Deprecate “Friends” component code into a separate downloadable plugin that can still be used exactly like it is now, just not part of the core anymore.

    2. Merge friends functionality into private “user” groups so that developers can choose to ditch the “friends” model if they want …

    3. “Friends” would replaced with the core ability to “follow” peoples activity, and for your activity to be followed by others …

    This is also a next step in the evolution in web friending, from classic Friendster/Facebook -> Twitter following -> following/friending with more context in groups and blogging (not just based on 140 chars brain farts).

    Absolutely agree with Windhamdavid btw!

    #59885
    Anonymous User 96400
    Inactive

    @Bowe

    setting up different group types is fairly easy. You just have to attach some groupmeta to the group, that basically let you add as many types as you’d like. Then you just check the metadata to figure out what type of group you’re in. Using the groups API you can then add different functionality for different groups.

    I’ve written a types-plugin for one of my sites. It doesn’t have an interface, though. The 3 types I needed are hardcoded into it, so it’s really not suited for a release at the moment. There’s also a lot of more stuff, like a shopping cart, part of that plugin. So, I’ve stripped the functions needed for group types out (hopefully al of them).

    First we need to add the addtional fields to our registration form:

    function sv_add_registration_group_types()
    {
    ?>
    <div id="account-type" class="register-section">
    <h3 class="transform"><?php _e( 'Choose your account type (required)', 'group-types' ) ?></h3>

    <script type="text/javascript" defer="defer">
    jQuery(document).ready(function(){
    jQuery("#account-type-normal_user").attr("checked", true);
    jQuery("#group-details").hide();
    jQuery("#account-type-type_one,#account-type-type_two,#account-type-type_three").click(function(){
    if (jQuery(this).is(":checked")) {
    jQuery("#group-details").slideDown("slow");
    } else {
    jQuery("#group-details").slideUp("slow");
    }
    });
    jQuery("#account-type-normal_user").click(function(){
    if (jQuery(this).is(":checked")) {
    jQuery("#group-details").slideUp("slow");
    } else {
    jQuery("#group-details").slideDown("slow");
    }
    });
    });
    </script>

    <?php do_action( 'bp_account_type_errors' ) ?>
    <label><input type="radio" name="account_type" id="account-type-normal_user" value="normal_user" checked="checked" /><?php _e( 'User', 'group-types' ) ?></label>
    <label><input type="radio" name="account_type" id="account-type-type_one" value="type_one" /><?php _e( 'Type 1', 'group-types' ) ?></label>
    <label><input type="radio" name="account_type" id="account-type-type_two" value="type_two" /><?php _e( 'Type 2', 'group-types' ) ?></label>
    <label><input type="radio" name="account_type" id="account-type-type_three" value="type_three" /><?php _e( 'Type 3', 'group-types' ) ?></label>

    <div id="group-details">
    <p><?php _e( 'We will automatically create a group for your business or organization. This group will be tailored to your needs! You can change the description and the news later in the admin section of your group.', 'group-types' ); ?></p>

    <?php do_action( 'bp_group_name_errors' ) ?>
    <label for="group_name"><?php _e( 'Group Name', 'scuba' ) ?> <?php _e( '(required)', 'buddypress' ) ?></label>
    <input type="text" name="group_name" id="group_name" value="" />
    <br /><small><?php _e( 'We suggest you use the name of your business or organization', 'group-types' ) ?></small>

    <label for="group_desc"><?php _e( 'Group Description', 'scuba' ) ?></label>
    <textarea rows="5" cols="40" name="group_desc" id="group_desc"></textarea>
    <br /><small><?php _e( 'This description will be visible on your group profile, so it could be used to present your mission statement for example.', 'group-types' ) ?></small>

    <label for="group_news"><?php _e( 'Group News', 'scuba' ) ?></label>
    <textarea rows="5" cols="40" name="group_news" id="group_news"></textarea>
    <br /><small><?php _e( 'Enter any news that you want potential members to see.', 'group-types' ) ?></small>
    </div>
    </div>
    <?php
    }
    add_action( 'bp_before_registration_submit_buttons', 'sv_add_registration_group_types' );

    Then we have to validate things and add some usermeta when a regitration happens:

    /**
    * Add custom userdata from register.php
    * @since 1.0
    */
    function sv_add_to_signup( $usermeta )
    {
    $usermeta['account_type'] = $_POST['account_type'];

    if( isset( $_POST['group_name'] ) )
    $usermeta['group_name'] = $_POST['group_name'];

    if( isset( $_POST['group_desc'] ) )
    $usermeta['group_desc'] = $_POST['group_desc'];

    if( isset( $_POST['group_news'] ) )
    $usermeta['group_news'] = $_POST['group_news'];

    return $usermeta;
    }
    add_filter( 'bp_signup_usermeta', 'sv_add_to_signup' );

    /**
    * Update usermeta with custom registration data
    * @since 1.0
    */
    function sv_user_activate_fields( $user )
    {
    update_usermeta( $user['user_id'], 'account_type', $user['meta']['account_type'] );

    if( isset( $user['meta']['group_name'] ) )
    update_usermeta( $user['user_id'], 'group_name', $user['meta']['group_name'] );

    if( isset( $user['meta']['group_desc'] ) )
    update_usermeta( $user['user_id'], 'group_desc', $user['meta']['group_desc'] );

    if( isset( $user['meta']['group_news'] ) )
    update_usermeta( $user['user_id'], 'group_news', $user['meta']['group_news'] );

    return $user;
    }
    add_filter( 'bp_core_activate_account', 'sv_user_activate_fields' );

    /**
    * Perform checks for custom registration data
    * @since 1.0
    */
    function sv_check_additional_signup()
    {
    global $bp;

    if( empty( $_POST['account_type'] ) )
    $bp->signup->errors['account_type'] = __( 'You need to choose your account type', 'group-types' );

    if( empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )
    $bp->signup->errors['group_name'] = __( 'You need to pick a group name', 'group-types' );

    if( ! empty( $_POST['group_name'] ) && $_POST['account_type'] != 'normal_user' )
    {
    $slug = sanitize_title_with_dashes( $_POST['group_name'] );
    $exist = groups_check_group_exists( $slug );
    if( $exist )
    $bp->signup->errors['group_name'] = __( 'This name is not available. If you feel this is a mistake, please <a href="/contact">contact us</a>.', 'group-types' );
    }
    }
    add_action( 'bp_signup_validate', 'sv_check_additional_signup' );

    And then we set up the group for the user (there are some constants in this function, so you’ll need to change that):

    /**
    * Create custom groups for skools, biz and org accounts
    * @since 1.0
    */
    function sv_init_special_groups( $user )
    {
    global $bp;

    // get account type
    $type = get_usermeta( $user['user_id'], 'account_type' );

    if( $type == 'normal_user' )
    {
    // Do nothing
    }
    elseif( $type == 'type_one' || $type == 'type_two' || $type == 'type_three' )
    {
    // get some more data from sign up
    $group_name = get_usermeta( $user['user_id'], 'group_name' );
    $group_desc = get_usermeta( $user['user_id'], 'group_desc' );
    $group_news = get_usermeta( $user['user_id'], 'group_news' );

    $slug = sanitize_title_with_dashes( $group_name );

    // create dive skool group
    $group_id = groups_create_group( array(
    'creator_id' => $user['user_id'],
    'name' => $group_name,
    'slug' => $slug,
    'description' => $group_desc,
    'news' => $group_news,
    'status' => 'public',
    'enable_wire' => true,
    'enable_forum' => true,
    'date_created' => gmdate('Y-m-d H:i:s')
    )
    );
    // add the type to our group
    groups_update_groupmeta( $group_id, 'group_type', $type );

    // delete now useless data
    delete_usermeta( $user['user_id'], 'group_name' );
    delete_usermeta( $user['user_id'], 'group_desc' );
    delete_usermeta( $user['user_id'], 'group_news' );

    // include PHPMailer
    require_once( SV_MAILER . 'class.phpmailer.php' );

    $mail = new PHPMailer();
    $mail->IsSMTP();
    $mail->Host = SV_SMTP;

    $auth = get_userdata( $user['user_id'] );
    $profile_link = $bp->root_domain . '/' . $bp->groups->slug . '/' . $slug . '/admin';

    $message = sprintf( __( 'Hello %s,

    we have created a group for your business or organization. To get more out of your presence on Yoursitenamehere please take some time to set it up properly.

    Please follow this link to fill in the rest of your profile: %s

    We wish you all the best. Should you have any questions regarding your new group, please contact us at support@yoursitenamehere.com.

    Your Yoursitenamehere Team', 'group-types' ), $auth->display_name, $profile_link );

    $mail->SetFrom("support@yoursitenamehere.com","Yoursitenamehere");
    $mail->AddAddress( $auth->user_email );

    $mail->Subject = __( 'Your new group pages on Yoursitenamehere', 'group-types' );
    $mail->Body = $message;
    $mail->WordWrap = 75;
    $mail->Send();
    }
    }
    add_action( 'bp_core_account_activated', 'sv_init_special_groups' );

    When you write a group extension we’ll have to swap the activation call with a function like the one below to be able to check for group types.

    /**
    * Replacement activation function for group extension classes
    */
    function activate_type_one()
    {
    global $bp;
    $type = groups_get_groupmeta( $bp->groups->current_group->id, 'group_type' );
    if( $type == 'type_one' )
    {
    $extension = new Group_Type_One;
    add_action( "wp", array( &$extension, "_register" ), 2 );
    }
    }
    add_action( 'plugins_loaded', 'activate_type_one' );

    The last thing we need to do is add our group type names to group and directory pages:

    /**
    * Modify the group type status
    */
    function sv_get_group_type( $type, $group = false )
    {
    global $groups_template;

    if( ! $group )
    $group =& $groups_template->group;

    $gtype = groups_get_groupmeta( $group->id, 'group_type' );
    if( $gtype == 'type_one' )
    $name = __( 'Type 1', 'group-types' );

    elseif( $gtype == 'type_two' )
    $name = __( 'Type 2', 'group-types' );

    elseif( $gtype == 'type_three' )
    $name = __( 'Type 3', 'group-types' );

    else
    $name = __( 'User Group', 'group-types' );

    if( 'public' == $group->status )
    {
    $type = sprintf( __( "%s (public)", "group-types" ), $name );
    }
    elseif( 'hidden' == $group->status )
    {
    $type = sprintf( __( "%s (hidden)", "group-types" ), $name );
    }
    elseif( 'private' == $group->status )
    {
    $type = sprintf( __( "%s (private)", "group-types" ), $name );
    }
    else
    {
    $type = ucwords( $group->status ) . ' ' . __( 'Group', 'buddypress' );
    }

    return $type;
    }
    add_filter( 'bp_get_group_type', 'sv_get_group_type' );

    /**
    * Modify the group type status on directory pages
    */
    function sv_get_the_site_group_type()
    {
    global $site_groups_template;

    return sv_get_group_type( '', $site_groups_template->group );
    }
    add_filter( 'bp_get_the_site_group_type', 'sv_get_the_site_group_type' );

    It’s quite a bit of code, but it should get you started. This hasn’t been tested with 1.2 btw.

    #59875
    designodyssey
    Participant

    solved my issue. Hope it helps someone. https://mu.wordpress.org/forums/topic/16051?replies=6

    #59865
    designodyssey
    Participant

    @Symm2112. Just left the GF forums and it does need to be activated on each blog separately. They said they’d look into changing this, but not until after the merge (boy that merge is going to open some doors).

    I’m looking to do a single blog install, so this solution still might work for me. I’ll have many groups, but one blog, therefore only one GF. Each group can still get it’s own category for posts (e.g. $blogcategory = “blog” . $blogid). I can display posts to that category only on that groups page (e.g. is(category)).

    I can afford to be a bit patient and see how this all develops. I’m actually not even in the BP stage of development. Still kicking the tires on my XAMPP WPMU install and making sure my other core functionality (e.g. the mapping I mentioned above) is working before I even install BP (will wait for 1.2 and WPMU 2.9).

    Given the theming issues, I’ll probably install Hybrid as a parent and ensure it’s working before I install BP. I’ll keep folks posted when I get to this. I’m just a planner by nature, so I’m trying to think things through – measure twice, cut once.

    #59811
    georgef101
    Participant

    I have the same problem…

    I have deleted all groups and started a new group but no luck.

    The thread appears in the sitewide activity, the tags get created.

    I just get the error and the thread doesnt show up in my /forums page.

    Any idea how to fix that?

Viewing 25 results - 16,301 through 16,325 (of 20,258 total)
Skip to toolbar